Every laptop I purchase arrives with Microsoft Office installed in several languages, along with OneDrive and other bundled software. Microsoft used to offer a utility that removed all Office installations in one pass, but I can no longer find it. Is there an official script or reliable deployment method to remove every Office language, OneDrive, and related components without manually uninstalling each item?
5 Answers
If these are business laptops, ask the vendor for a clean Windows image with only the operating system and required drivers. Otherwise, reimage the devices yourself and deploy only the applications you actually need. That avoids vendor bloat and makes future machines consistent.
Third-party tools such as Office Scrubber can handle stubborn Office remnants, and general Windows debloat utilities can remove OneDrive and bundled apps. Be careful with broad debloat scripts, though—some modify services, scheduled tasks, registry settings, or system components and can create hard-to-diagnose problems. Use a tested, narrowly scoped script and keep a recovery plan.
A full Windows reinstall will remove the factory image, but it is usually more work than necessary for this specific problem. Make sure you have backups, drivers, activation details, and deployment information before wiping anything, especially if the device has a vendor recovery partition or is intended for automated device enrollment.
The Microsoft-supported approach is to use the Office Deployment Tool with a removal configuration. A configuration containing can remove Click-to-Run Office installations, including extra language versions. Test it on a representative laptop first, since the result depends on how the vendor installed Office.
Microsoft’s Office uninstall troubleshooter is another good option if you want an official tool. For larger deployments, though, I’d build a clean Windows image or use the ODT configuration during provisioning rather than uninstalling everything interactively.
This is what we use in an automated setup script: run the ODT with the appropriate configuration and then continue with the rest of the build. It has been reliable and is less invasive than a general debloat script.