Silent uninstall Office 365

I had to bulk repair a few Office 365 Fat Client Installations. With the Office 365 Click-to-Run deployment EXE and two XML files this is a quick task.

First download the Office 2016 Deployment Tool:

Second create the XML files:

    <Remove All="TRUE"/>
    <Display Level="None" AcceptEULA="TRUE"/>
    <Property Name="AUTOACTIVATE" Value="0"/>
    <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
    <Property Name="SharedComputerLicensing" Value="0"/>
    <Property Name="PinIconsToTaskbar" Value="FALSE"/>
    <Add OfficeClientEdition="32" Channel="Deferred" SourcePath="\\FS01\Office365\2016\32\">
        <Product ID="O365ProPlusRetail">
            <Language ID="de-de"/>
            <ExcludeApp ID="Groove"/>
            <ExcludeApp ID="Publisher"/>
    <Updates Enabled="TRUE" Channel="Deferred" UpdatePath="\\FS01\Office365\2016\32\"/>
    <Display Level="None" AcceptEULA="TRUE"/>
    <Logging Level="Standard" Path="\\FS01\Office365\2016\32\Log\"/>
    <Property Name="AUTOACTIVATE" Value="0"/>
    <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
    <Property Name="SharedComputerLicensing" Value="0"/>
    <Property Name="PinIconsToTaskbar" Value="FALSE"/>

And then deploy the tasks to the affected machines:

"\\FS01\Office365\2016\32\setup.exe" /configure "\\FS01\Office365\2016\32\remove.xml
"\\FS01\Office365\2016\32\setup.exe" /configure "\\FS01\Office365\2016\32\configuration_FAT.xml

Hope that helps you!

Author: Marco

Marco is an IT-System administrator and IT-Consultant with 10+ years experience. He is specialized in the delivery of virtual Apps and Desktops with Citrix solutions. In 2017 he has been awarded Citrix Technology Advocate by Citrix for his community work (#CTA). His second core area is availability & performance monitoring with Zabbix, a leading open-source solution. His employer is the German IT-Company ANAXCO, which is developing a Transport Management Software (TMS) based on Microsoft Dynamics AX. More about Marco

8 thoughts on “Silent uninstall Office 365”

  1. Hi, a little confused, about your process. I assume for the removal, you ONLY used the remov.xml. Just trying to understand your two xml files, deploy, and remove. Thanks

    1. Yes, it were two deployments. First I did a complete removal with the first XML, then I did a fresh install with the second XML.

        1. As far as I know, you have to uninstall the whole Office 365 package and reinstall it with a new config.xml file, that doesn’t include Outlook.

  2. Hey Marco!

    Thanks for saving me some time! It works great!

    I have a question though. Is there a reason you decided to install the 32bit version over the 64bit version?

    1. The only reason I have to rely on the 32bit version of Office 365 is, that most of my customers still rely on legacy Office AddIns, where the vendor wouldn’t support 64bit.
      If that wouldn’t be the case, I would deploy 64bit.
      Ps.: That post is from 2017 (but still valid!), 32bit Office was still the de-facto standard a few years ago 😉

  3. Do you know if there are any limitations using the tag and the tag in the same configuration file?

    I determinined, that removing e.g. Office 2019 using

    in a seperate xml-file works fine, but if I add this snippet to the xml which installs office 2021 it seems to be ignored. Office 2021 is installed properly, but Office 2019 is still available after the installation finished.

  4. Great Work!!
    As many new notebooks come with a bunch of Office365 languages pre-installed it was a pain clicking and waiting in the program manager.
    Thanks Marco!!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.