Fix Duplicate Office Apps After Microsoft 365 Upgrade
Question details
Users are experiencing duplicate Office application shortcuts, broken file associations, and outdated application registrations after upgrading their Office installation.
- Product
- Microsoft 365
- Device & OS
- Windows
- Scenario
- Upgrading from the Microsoft Store version of Office to the Microsoft 365 Click-to-Run desktop version.
- Observed behavior
- Outdated application shortcuts and registry cache data persist in the original Windows profile. PowerShell commands fail unless the full path to the executable is provided, and file associations may not work properly.
Ensure you have Windows administrator privileges and have saved all your active documents before starting the uninstallation process.
Use the Microsoft Office Uninstall Support Tool
This is the most reliable method to completely wipe outdated application registrations, residual shortcuts, and cache data from previous Office versions.
Installing the Click-to-Run version over the Microsoft Store version often leaves behind registry keys that conflict with the new installation. The official support tool cleans these hidden remnants automatically.
Navigate to the Microsoft Support website and download the official Office Uninstall Support Tool (SetupProd_OffScrub.exe).
Double-click the downloaded file, follow the installation prompts, and select the version of Office you want to uninstall from the provided list.
Once the tool finishes processing and removing the leftover Microsoft Store components, restart your Windows PC to clear the system cache.
Log in to the Microsoft 365 portal in your web browser, download the latest Click-to-Run installer, and reinstall the Office applications.
Create a New Windows User Profile
If completely reinstalling Office does not resolve the cache issue in your current user account, migrating to a new profile will bypass the corrupted registry entries.
Update PowerShell Paths Manually
Use this temporary workaround if you need to launch Office applications via scripts or command line before performing a full reinstallation.
Switch to WPS Office for a Hassle-Free Experience
Tired of dealing with complex Microsoft 365 installations, corrupted registry keys, and broken file associations? Switch to WPS Office. It is a lightweight, all-in-one free alternative that installs cleanly and handles your documents without system conflicts.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for Windows.
- 2. Install WPS Office: Run the setup file. The single-client architecture installs Word, Excel, and PowerPoint alternatives in just one click.
- 3. Set Default File Associations: During setup, check the option to make WPS Office your default program to instantly fix any broken file associations.
Frequently Asked Questions
Why do I have duplicate Office apps after upgrading to Microsoft 365?
This happens when upgrading from the Microsoft Store version of Office to the desktop Click-to-Run version. They install into different directories, and the Windows registry may fail to automatically delete the shortcuts and app registrations from the older Store version.
Will using the uninstall tool delete my personal Word or Excel documents?
No. The Microsoft Office Uninstall Support Tool only removes program files, registry keys, and application cache. Your personal documents, spreadsheets, and files saved on your hard drive or OneDrive will not be affected.
Why does PowerShell fail to open Word after the upgrade?
The system PATH or application alias may still be pointing to the uninstalled Microsoft Store version of the app. Until the old cache is cleared, you must use the complete file path (e.g., C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE) in your commands.
Can I manually fix the broken file associations without reinstalling?
Yes. You can right-click any Office document, select 'Open with', choose 'Choose another app', select the correct Microsoft 365 app (like Word), and check 'Always use this app to open files'. However, a clean reinstallation is recommended to fix all underlying registry conflicts.
