Uninstall & Reinstall Issues

Remove Microsoft Office Click-to-Run with the Command Line

Camila MilosovichCamila Milosovich Nov 20, 2026 869 views

Question details

Remove Office Click-to-Run installations through an automated command rather than Windows Settings.

Remove Microsoft Office Click-to-Run with the Command Line
Product
Microsoft Office Click-to-Run and Office Deployment Tool
Device & OS
Windows
Scenario
An administrator needs to remove Office from a large number of systems using a deployment tool.
Observed behavior
A configuration targeting a specific Click-to-Run product may return error 0-1008 (0), while manual removal is impractical at scale.
Before you start

Download the latest Office Deployment Tool from Microsoft and extract setup.exe to a deployment folder. Confirm that removing all Click-to-Run Office products is appropriate, and test the configuration on a representative device before deploying it broadly.

Solution 1Recommended

Remove all Click-to-Run Office products with the Office Deployment Tool

Use this approach when all Click-to-Run Office products should be removed, avoiding a product-specific ID that may not match the installation.

Remove All targets all installed Click-to-Run Office products, potentially including Click-to-Run versions of Project and Visio. It does not by itself remove Office products installed using Windows Installer (MSI).

1
Create the configuration file

In the folder containing setup.exe, create configuration.xml with this content: <Configuration><Display Level="None" AcceptEULA="TRUE" /><Remove All="TRUE" /></Configuration>.

2
Close Office applications

Ask users to save their work and close Office applications before the removal runs. Schedule the deployment for a time when Office is not in use.

3
Run the removal command

Open Command Prompt as administrator, change to the Office Deployment Tool folder, and run: setup.exe /configure configuration.xml. For remote deployment, use a management tool that runs the command with administrative permissions.

4
Verify and deploy

On the test device, check Windows Settings > Apps to confirm the targeted Click-to-Run products were removed. If successful, deploy the same files and command to the remaining devices.

Remove all Click-to-Run Office products with the Office Deployment Tool
MSI installations need separate handling: The Office Deployment Tool's RemoveMSI element is used when installing Click-to-Run Office to remove supported MSI versions. Do not rely on a standalone Remove All command to remove MSI installations; plan and test a supported MSI removal method separately.
Free Microsoft Office alternative

Choose WPS Office as an Alternative After Removing Microsoft Office

WPS Office is a free, lightweight alternative with a familiar interface for working on documents, spreadsheets, and presentations. Its support for Microsoft Office formats helps users move their files without starting over.

A lightweight office suite for users transitioning from Microsoft OfficeCompatible with Microsoft Office formats including DOCX, XLSX, and PPTXFamiliar tools for editing documents, spreadsheets, and presentationsA free option for everyday office work
microsoft office alternative - wps office

Frequently Asked Questions

What does Remove All remove?

In an Office Deployment Tool configuration, <Remove All="TRUE" /> targets all installed Click-to-Run Office products. Review the device's Office, Project, and Visio installations before using it.

Why might a product-specific removal return error 0-1008 (0)?

The product ID in configuration.xml may not match the installed Click-to-Run product. Check the ID and XML syntax, or use Remove All if removing every Click-to-Run Office product is acceptable.

Does Remove All uninstall MSI versions of Office?

No. Remove All targets Click-to-Run products. The RemoveMSI element is intended for removing supported MSI Office versions during a Click-to-Run installation, so a standalone removal deployment needs a separate MSI removal plan.

How can I run the removal silently across many computers?

Add <Display Level="None" AcceptEULA="TRUE" /> to the configuration and deploy setup.exe /configure configuration.xml through your management tool with administrative permissions. Test on a representative device first.

Where can I check why the Office Deployment Tool failed?

Inspect the Office setup logs in the Windows temporary folder. Enter %temp% in File Explorer, then review the relevant logs along with the XML file and the command's execution permissions.