'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Office Installing 64-Bit Instead of 32-Bit on Windows ARM64
Question details
The user needs to force the installation of a 32-bit version of Microsoft Office on a Windows ARM64 virtual machine to support legacy components.
- Product
- Microsoft 365
- Device & OS
- Windows ARM64
- Scenario
- Attempting to install the 32-bit version of Office to use legacy Access builds on a Windows ARM64 virtual machine, such as Parallels on Apple Silicon.
- Observed behavior
- The installer automatically prioritizes and silently installs the 64-bit version despite the 32-bit version being selected. Standard uninstallation methods leave residual files behind, causing the issue to persist upon reinstallation.
Ensure you have administrative privileges on your virtual machine and back up any existing legacy databases before proceeding with a complete software uninstallation.
Use Microsoft Support and Recovery Assistant for a Clean Install
Completely remove the stubborn 64-bit Office installation remnants using Microsoft's official cleanup tool before deploying the 32-bit version.
The standard Windows uninstaller often leaves behind registry keys and cached installation files that force subsequent installations back into the 64-bit architecture. Utilizing the Support and Recovery Assistant (SaRA) ensures a completely clean slate.
Navigate to the official Microsoft download page and acquire the Microsoft Support and Recovery Assistant.
Run the application, select 'Office & Office Apps', choose the option to uninstall Office, and follow the on-screen prompts to remove all components.
Once the tool finishes, reboot your Windows ARM64 virtual machine to clear all memory and cached files.
Instead of the standard web installer, use the Office Deployment Tool with a configuration XML file specifically targeting the 32-bit architecture to prevent automatic 64-bit overrides.
Looking for a hassle-free alternative on ARM-based devices?
If you are struggling with complex Microsoft Office architecture installations on your ARM virtual machine, try WPS Office. It provides a lightweight, highly compatible, and easy-to-install alternative for your everyday document, spreadsheet, and presentation needs without strict architecture limitations.
- 1. Download WPS Office: Visit the official WPS website and click the free download button.
- 2. Run Installer: Execute the downloaded installation file on your virtual machine.
- 3. Start Creating: Open WPS Office and enjoy seamless document editing.
Frequently Asked Questions
Why does Microsoft 365 force a 64-bit installation on my Windows ARM64 VM?
Microsoft 365 web installers are designed to detect the host architecture and optimize performance automatically. Since Windows on ARM handles 64-bit instructions natively or via optimized emulation, the installer defaults to 64-bit to provide the best performance, often ignoring manual selections.
Can I run 32-bit legacy Access databases on an Apple Silicon Mac using Parallels?
Yes, but you must completely scrub any existing 64-bit Office installations first. You will then need to explicitly use an offline 32-bit deployment method to prevent the auto-updater from installing the 64-bit version.
Why doesn't the standard Windows Apps & Features uninstallation work?
The standard Windows uninstaller frequently leaves behind registry keys and cached installation configuration files. When you attempt to reinstall, the Office installer reads these remnants and reverts to the previously installed architecture.
