Microsoft 365 Error Codes

How to Fix Office Deployment Tool Error 17006 During Silent Uninstallation

Amos Gikunda Oct 21, 2026 868 views

Question details

Users need to resolve error code 17006 when attempting to silently uninstall Microsoft 365 using the Office Deployment Tool (ODT).

Fix Office Deployment Tool Error 17006 During Silent Uninstallation

Product: Microsoft 365
Device & OS: not provided
Scenario: Silently uninstalling or removing Microsoft 365 from a PC via the command line and an XML configuration file.
Observed behavior: The uninstallation fails and returns error 17006, often due to an invalid XML configuration, an incorrect product ID, or a mismatched 32-bit/64-bit architecture.

Before you start

Ensure you are logged into your computer with administrative privileges and have access to the original Office Deployment Tool configuration XML file used for the installation.

Solution 1Recommended

Verify XML Configuration Architecture and Run as Administrator

Error 17006 frequently occurs if the architecture (32-bit vs. 64-bit) in the removal XML does not match the currently installed version of Office.

The Office Deployment Tool is highly sensitive to mismatched configuration parameters. If the XML file specifies a 32-bit removal but a 64-bit version is installed, the process will fail with error 17006. Modifying the XML and ensuring the command is run with elevated privileges is the primary fix.

Edit the XML File

Open your removal XML file in a text editor like Notepad. Check the 'OfficeClientEdition' attribute.

Match Architecture

Ensure the 'OfficeClientEdition' value exactly matches your installed version (e.g., change it to '64' for 64-bit installations or '32' for 32-bit installations).

Launch Command Prompt

Press the Windows key, type 'cmd', right-click on 'Command Prompt' in the search results, and select 'Run as administrator'.

Execute ODT Command

Navigate to the ODT folder and run the command again using: setup.exe /configure remove.xml (replace remove.xml with your actual file name).

Verify XML Configuration Architecture and Run as Administrator

Double-Check Product IDs: While checking the architecture, also ensure that the Product ID in the XML exactly matches the installed product (e.g., O365ProPlusRetail or O365BusinessRetail).

Solution 2

Use the Microsoft Support and Recovery Assistant (SaRA)

If command-line uninstallation continues to fail, use Microsoft's automated uninstall tool to force remove the Office components.

Free Microsoft Office alternative

Try WPS Office for a Lightweight, Error-Free Experience

Tired of dealing with complex deployment tools and cryptic uninstallation errors? WPS Office offers a free, lightweight, and incredibly easy-to-manage alternative to Microsoft Office. Skip the complicated XML scripts and enjoy seamless document creation right out of the box.

1. Download: Get the latest version of WPS Office from the official website.
2. Install: Run the simple, one-click installer without worrying about deployment configurations.
3. Start Creating: Open WPS Office and seamlessly load your existing Word, Excel, or PowerPoint documents.

Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight installation package that requires no complex deployment scripts or XML files.Free to use with a familiar, easy-to-navigate user interface.All-in-one suite combining Writer, Spreadsheet, and Presentation in a single window.

microsoft office alternative - wps office

Frequently Asked Questions

What exactly does Office Deployment Tool error 17006 mean?

Error 17006 generally indicates a syntax error, an unrecognized product ID, or a configuration mismatch in your XML file during silent uninstallation. The most common cause is specifying the wrong architecture (32-bit instead of 64-bit) in the removal script.

Where can I find the ODT log files to troubleshoot this error?

ODT log files are automatically generated in your Windows Temp directory during installation or removal attempts. You can access them by pressing Win + R, typing '%temp%', and looking for log files that start with your machine name.

Do I always need to run the ODT command as an administrator?

Yes, adding, modifying, or removing Office installations requires elevated system privileges. Always ensure you open the Command Prompt with the 'Run as administrator' option to avoid permission-based failures.

Microsoft Office Error Codes