How To Uninstall Microsoft Office Windows 10

[Elsa Hoelscher]

Checking at -US/b8e4cda5-2806-484f-80cf-f8e0f2a98f2f/command-to-uninstall-office-2016-and-contentlocation-of-uninstallxml-file?forum=configmanagerapps , it looks like you have to create an XML answer file for the Office uninstall, and then feed that on the command line.

I was under the impression that if you could get it to run on the local machines command line that you could get it to work through Bigfix. Do you mean use this uninstall string but instead of calling the osetup.dll create that config file and call it instead?

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.

I have a new Asus tablet running windows 10 and I want to uninstall parts of it like Access, OneNote, Publisher, that I will NEVER use on this device.I have only 32GB of harddrive and with windows updates getting more and more I will have to trash my little computer within a month :(

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.

These steps will get you in the Control Panel, ready to disable Microsoft Office Click-to-Run and make changes. In addition to making essential system modifications, the Control Panel also provides customization options. You can personalize your desktop, manage user accounts, uninstall programs, adjust power settings, and much more.

My colleague was facing performance issues with Microsoft Office Click-to-Run on his laptop. He followed these steps and disabled it without causing any problems for his other office applications. It improved his working experience significantly.

Moreover, taking control of the Click-to-Run feature allows one to customize their Office package exactly to their needs and preferences. Plus, turning it off eliminates any security issues linked to automatic updates. This gives them the opportunity to monitor and apply updates as per their comfort, so they can always stay up to date with the latest security patches and improvements.

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.

We have recently solved the issue of MAPI errors coming up for Acro Docs/WM users when attempting to send a file via email from within Acrosoft products. After much troubleshooting, the problem seems to come from 64-bit Office installations conflicting with Acrosoft's 32-Bit MAPI interface. Hyland will also utilize 32-Bit Office protocols as well, so this fix will be pervasive over the upcoming migration from Acro to Hyland.

MS Office is now a package install, where it used to have multiple installs for Outlook, Excel, Etc; the entire MS Office package must be completely uninstalled to replace it, which requires a proprietary Microsoft Application called Microsoft Support And Recovery Assistant, commonly referred to as SARA.

This process requires Admin-level credentials, and should be attempted only when the end-user is physically in the office, as it's a 2-step process (Uninstall, and then a restart before reinstallation), and if SCCM connection is lost before the 32-bit install is complete, the end user will be without any Office products, which will end their business productivity until the application is reinstalled. We have had success with the Admin user being remote and connecting to the EU Computer inside the office, as SCCM seems to be more stable this way, but when both users are at home, SCCM connection can be inconsistent after a restart. The safe step of having the EU at the office for either a Helpdesk employee to physically install on the laptop, or to deploy remotely on their end after a test connection to SCCM first ensures no downtime outside the standard installation process, which is around 20 minutes.

The easiest way to do this is to open MECM with your Admin creds, then select 'Devices' and then search for either the computer name, or the EU's name under "Currently Logged On User" field. Right click and select 'Start', then select 'Remote Control.'

This should not be performed via a Teams screenshare; Office will be completely uninstalled after the SARA tool has run. You will not be able to see anything or provide Admin creds once Office is uninstalled. Proceed ONLY if SCCM connection is successful and stable.

You'll want to select the 'Office - Install, Activate, or Remove Office' option here. Once you do this, it will run the full uninstall tool (approx 10 min), then the Application will inform you the process was successful, and then you'll have to Restart the computer (it will remind you of this).

c80f0f1006