Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
As far as I can tell, the issue likely persists because the standard installer performs a global check for any 32-bit registry keys or leftover components from integrated apps like Visio or Project. Even if the main applications are gone, shared architectural files in the Program Files (x86) directory or specific keys in the WOW6432Node registry hive can trigger the blockade. To bypass this check, try using the Office Deployment Tool (ODT). This method allows you to force a 64-bit architecture regardless of what the standard setup executable detects on the system.
First, download the Office Deployment Tool from the official Microsoft Download Center and extract its contents to a folder on your desktop named ODT. Inside that folder, create a new text file and rename it to install.xml. Open this file with Notepad and paste the following configuration code into it, then save the file.
<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2019">
<Product ID="ProPlus2019Volume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="Full" AcceptEULA="TRUE" />
</Configuration>
Next, execute the installation through an elevated command prompt to ensure it has the permissions required to write to the registry and system folders. Click your Start menu, type cmd, right-click the Command Prompt result, and select Run as Administrator. Navigate to your ODT folder using the change directory command. If your folder is on the desktop, the command will look like the following example.
cd %USERPROFILE%\Desktop\ODT
Once you are inside the correct directory, run the following command to initiate the 64-bit installation process. This command tells the deployment tool to ignore the standard setup logic and follow the specific instructions in your XML file.
setup.exe /configure install.xml
If you receive an error regarding the Product ID, it may be because you have a Retail version rather than a Volume License version. In that specific case, you would need to change the Product ID in the XML file from ProPlus2019Volume to ProPlus2019Retail.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin