bimmira xilone bryannah

0 views

Skip to first unread message

Lorin Searing

unread,

Aug 2, 2024, 11:39:05 PM8/2/24

to grunfarcgaxis

My team and I have an issue that we cannot find a fix for. For what appears to be a random occurrence, we see a number of machines in our network where Office 365 will uninstall itself. We have scoured the internet trying to find a solution and although we see lots of people mentioning that this happens, the answers do not seem to fix the issue. A bit about our setup:

We have one Microsoft 365 for Windows 10 setup to push O365 but only two machines are in that group and although those 2 machines are getting Office removed, there a plenty of other people getting Office removed that are not in that group.

We are facing same issue with o365 apps getting uninstalled leaving Outlook and Teams intact. We are pushing Teams through Intune to all group members but in addition to it end users are downloading the o365 apps from office portal too.

There are several different reasons why you would want to uninstall Office 365 from your computer. You could be having issues with the program and must reinstall the program, you could be changing to another program or model of office such as Office 365 or OpenOffice, your subscription period could be up and you do not want to renew or it could be you want to use this program on a newer computer.

i want install microsoft office 2016 64 bit. i had unistalled microsoft office 32 bit for the same from programs and features in control panel. but after opening the setup of office 16 64 bit it says it has located a file named office 16 click to run extensibility component and unsintall 32 bit Microsoft office. how do i solve this?

You may have to re-install office. I suspect that since it is the free version you cannot scan for leftovers directly. Re-run the installation for office (if necessary) then run REVO and have it uninstall. Be sure to select the advanced scan option and put a check [x] in the box to delete the leftovers.

So you want to know how to uninstall MS Office on your Mac? If you're low on disk space, sick of glitchy MS Office apps, or found a better productivity solution, we've got all the tips you need to completely remove Microsoft Office, now known as Microsoft 365, reset it, or simply delete one of its troublesome apps.

With over 345 million users worldwide, including businesses, schools, and private accounts, it's undoubtedly a popular solution, but it's not the only option out there. Today we see fierce competition from Google Workplace, LibreOffice, and WPS Office, to name a few. Not to mention Apple's built-in tools that come with macOS, such as Pages, Numbers, and Keynote.

Lots of people are looking to make a switch. Whether it's price, performance, or productivity-related, regardless of your reason for opting out, we've got the steps you need to remove it safely from your MacBook. Let's get started.

If you want to quickly uninstall Office on your Mac or perhaps just one of its apps that you never use, the easiest and most efficient way is by using the powerful Uninstaller module that comes with CleanMyMac X.

This is a dedicated removal tool, so you know all traces and hidden application leftovers will be eradicated in just one click, saving you space on your Mac and precious time.
If you aren't already familiar with this popular third-party Mac tool, get the free version here. Then install the app and proceed with the steps below:

Manually removing applications is a two-part process that lots of people don't realize. You can't just simply drag an app to your Trash; you also need to locate and remove leftover files, which take up space on your hard drive if left intact. I'll guide you through the process below.

OK, so the application icons have been deleted. This is the part where things get a little more complex. But it is still not impossible, and what you have to do is hunt down leftover files. Here's how:

Next, locate the Containers folder and remove the following folders and files:
com.microsoft.errorreporting
com.microsoft.netlib.shipassertprocess
com.microsoft.Excelcom.microsoft.Office365ServiceV2
com.microsoft.Powerpointcom.microsoft.Outlook
com.microsoft.RMS-XPCService
com.microsoft.onenote.mac
com.microsoft.Word

Using the tool I mentioned earlier, CleanMyMac X, you can save time by resetting apps back to their original state instead of removing them entirely. Resetting applications gives them the equivalent of a reboot. It's really easy to do; here's how:

If your Mac isn't operating the latest software, you'll undoubtedly begin to encounter some issues, and strange application behavior is one of them. Here's a reminder on how to quickly check for updates:

Well, here we are at the end. We've covered everything on the topic of how to uninstall MS Office on Mac. These tips are transferable; they'll work for help when removing any unwanted apps on your Mac, so why not bookmark this page for future reference?

Microsoft Scripting Guy, Ed Wilson, is here. The Scripting Wife and I were in Texas for the Corpus Christi Windows PowerShell User Group meeting when Marc Carter told me about the problem with the MSI installer reconfiguring applications when the Win32_Product WMI class is queried. I immediately encouraged him to write a guest blog about this issue.

BT, there is a way to use the Win32_Product WMI class in a more efficient manner. It relies on using the [WMI] type accelerator, instead of doing a generic WMI query. The problem is that the [WMI] type accelerator returns a specific instance of a WMI class. To connect to a specific instance, I must use the Key property of a WMI class.

I can use the Get-WMIKey function from my HSGWMImoduleV6 module. In the following code, I first import my HSGWMImoduleV6 module, and then I use the Get-WMIKey function to return the key to the Win32_Product WMI class. The commands and the output from the commands are shown here.

The query to return the three parts of the composite key only needs to run once; the values do not change. It is also possible to use the Get-WmiObject cmdlet and a filter to improve the performance of the command a little bit. The nice thing about this command is that it returns the information that is required by the [WMI] type accelerator. The command and associated output are shown here.

When I have the three pieces of information (the IdentifyingNumber, the Name, and the Version), it is time to create the key. This is where quite a bit of experimentation could be required. I have to use the back tick (grave) character to escape inside quotation marks. I have to escape the quotation mark and the opening curly bracket for the IdentifyingNumber property. I also have to escape the closing curly bracket and the closing quotation mark. I then have to escape the quotation marks that surround Microsoft Silverlight, in addition to the quotation marks for the Version property. There are also two quotation marks at the end of the ClassKey.

The reason for all the escaping in the ClassKey, is that WMI expects the quotation marks and the curly brackets in the key itself. To see what WMI expects to receive via the command, I use the Windows Management Instrumentation Tester (WbemTest) command, and I view the instances of the class. The following image illustrates the instances of Win32_Product on my computer.

When I have the ClassKey, I can use the [WMI] type accelerator to connect to the specific software package (Microsoft Silverlight in this example). In fact, using the [WMI] type accelerator is very easy. Here is the command. (The command is [WMI], the class name, and the key).

I can also include the WMI namespace (really important if the class resides in a namespace other than the default root\cimv2). In the command that follows, notice that there is a backslash that precedes the word root. One other thing to notice is that a colon separates the WMI namespace and the WMI class name.

If I need to connect to a WMI class on a remote computer, I use a double backslash and the name of the computer, then the WMI namespace, the WMI class, and the WMI ClassKey. The command that follows illustrates this.

In the image that follows, I illustrate the different ways of querying WMI for Microsoft Silverlight software. I then compare the speed of using the Get-WmiObject cmdlet against the speed of using the [WMI] type accelerator. As shown in the following image, the Get-WmiObject cmdlet, using the filter to find Microsoft Silverlight, takes over five seconds on my laptop. Using the [WMI] type accelerator takes less than one-half of a second. This is more than 10 times faster.

When using the [WMI] type accelerator, a complete instance of the WMI class instance returns. The properties and their associated values are shown in the following image. Notice two properties: the __Path (that is, double underscore Path) property is the key to the WMI class instance. The InstallLocation property points to the location where the software installs.

BT, that is all there is to using the Win32_Product WMI class to detect or to uninstall software. Join me tomorrow when I will have a guest blog written by Raymond Mitchel as he talks about Windows PowerShell and SharePoint.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scri...@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.