How to Completely Uninstall Office 2013 64-bit Before Installing 32-bit
Question details
The user needs to completely remove Microsoft Office 2013 Enterprise 64-bit to install the 32-bit version, but faces errors stating the 64-bit version is still installed despite removal via Control Panel.
- Product
- Microsoft Office 2013 for Enterprise
- Device & OS
- Windows
- Scenario
- Attempting to switch from a 64-bit to a 32-bit Office 2013 installation in an enterprise environment without local administrator rights.
- Observed behavior
- The 32-bit setup is blocked because it detects residual 64-bit files. Furthermore, the official Office uninstall utility fails with a download error due to a lack of local administrator rights.
Ensure you have local administrator credentials, as modifying system registries and removing enterprise software components requires elevated permissions.
Use the Official Office Uninstall Support Tool as an Administrator
This is the most reliable way to strip hidden registry keys and residual files that the standard Control Panel uninstallation leaves behind.
The standard Windows uninstallation process often leaves residual Office registry entries that trigger architecture conflicts. The official Microsoft Support and Recovery Assistant is designed to aggressively clear these remnants.
Download the official Microsoft Office uninstall support tool (SetupProd_OffScrub.exe) from the official Microsoft support website.
Right-click the downloaded tool and select 'Run as administrator'. This is crucial because standard user profiles will trigger application download errors or fail to delete protected keys.
Follow the on-screen prompts and select 'Office 2013' as the version you want to remove.
Once the tool finishes, restart your Windows computer to complete the registry cleanup before attempting the 32-bit installation.
Manually Remove Office 2013 Registry Entries and Folders
Use this method if the automated uninstall tool continues to fail due to network download errors.
Request Enterprise IT Administrator Assistance
The safest approach for users running Office 2013 for Enterprise on a domain-joined machine lacking proper local credentials.
Avoid Architecture Conflicts with WPS Office
Microsoft Office uninstallation issues often stem from complex registry leftovers and strict 32-bit versus 64-bit architecture conflicts. You can bypass these enterprise deployment headaches entirely by switching to WPS Office. It is a lightweight, highly compatible alternative that installs seamlessly without complex administrative roadblocks.
- 1. Download the Installer: Visit the official WPS website and download the free installation package.
- 2. Run the Setup: Double-click the downloaded file and click 'Install' to begin the rapid setup process.
- 3. Start Creating: Open WPS Office and instantly view, edit, or create files compatible with Microsoft Office formats.
Frequently Asked Questions
Why does the 32-bit installer say the 64-bit version is still installed?
Even after uninstalling via Control Panel, hidden registry keys and residual installation files often remain on your system. The 32-bit installer detects these fragments and halts the process to prevent software conflicts.
How can I fix the application download error in the Microsoft uninstall utility?
This error usually occurs due to network firewalls or a lack of local administrator rights. Try right-clicking the tool and selecting 'Run as administrator'. If you are on an enterprise network, you may need your IT administrator to temporarily disable network blocks or run the tool for you.
Can I install both 32-bit and 64-bit Office versions on the same computer?
No. Microsoft does not allow the simultaneous installation of 32-bit and 64-bit Office products on the same operating system. You must completely wipe one architecture type before installing the other.
Why do I need administrator rights to uninstall Office 2013?
Office 2013 integrates deeply into the Windows operating system and modifies protected registry keys and system folders. Standard user accounts are restricted from altering these critical areas to ensure system security.
