Fix Windows Installer Error 0X0000064D – Version Conflict

This error means the installer sees a newer version already installed. The fix is to replace or remove that version. Works for MSI and EXE installers.

When You'll See This Error

You're trying to install an older version of a program — maybe a driver, a security tool, or a line-of-business app. Windows Installer stops dead with 0X0000064D. The exact message says: "This installation package cannot be installed by the Windows Installer service". It usually pops up during an MSI-based install on Windows 10, 11, or Server 2019/2022.

Root Cause – Simple and Stupid

The installer detects a newer version of the same product already installed. Windows Installer won't let you downgrade by default. This is by design — Microsoft doesn't want you accidentally breaking things. But sometimes you legitimately need the older version, maybe because the newer one has a bug or your license doesn't match.

The registry holds the version info. The installer reads it and says "nope."

The Fix – Step by Step

Don't waste time with compatibility mode or running as admin — that only helps with privilege issues, not version conflicts.

Step 1: Check What's Installed

Open Settings > Apps > Installed apps (or Control Panel > Programs and Features if you're on Server 2019). Find the program you're trying to install. Note the exact version number.

Step 2: Uninstall the Newer Version

If the newer version is safe to remove (check with your team first), uninstall it:

Select the app and click Uninstall.
Reboot the machine.
Try the older installer again.

This works about 70% of the time. If you can't uninstall because the app is critical or the uninstall fails, move to Step 3.

Step 3: Edit the Registry (Advanced)

Only do this if you're comfortable with regedit. Wrong changes can break your system.

Back up the registry first: File > Export > save a .reg file.
Press Win + R, type regedit, hit Enter.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
Look for the product's GUID (it's in the error details if you see a log). If not, look through the list — most apps show their name under DisplayName.
Find the DisplayVersion value. Change it to a lower number than the one you're installing. For example, if the installer wants version 1.0.0.0, change the installed version to 0.9.9.9.
Close regedit. Try the installation again.

Note: Some apps also keep version info in HKEY_CURRENT_USER\Software\Microsoft\Installer\Products. Check there if the first path doesn't work.

Step 4: Use the MSI Command-Line Override

If editing the registry feels risky, you can force the installer to ignore version checks. Open a command prompt as admin and run:

msiexec /i "path\to\installer.msi" REINSTALL=ALL REINSTALLMODE=vomus

Replace path\to\installer.msi with the actual path. This tells the installer to reinstall all components and override the version check. I've used this on dozens of Server 2019 boxes — it works but you might lose some config settings from the newer version.

Still Failing? Check These

If the error keeps showing after trying the above, look at these:

Leftover entries: Sometimes the app is uninstalled but the registry key stays. Run regedit and delete any orphaned GUIDs under Uninstall that match the app.
Corrupted Windows Installer: Run msiexec /unregister then msiexec /regserver as admin. This re-registers the service.
Third-party cleanup tools: Use Microsoft Program Install and Uninstall Troubleshooter from the official site. It's old but still good for stuck installs.
Log the install: Create a verbose log: msiexec /i "installer.msi" /l*vx install.log. Look for lines with "Error 0x64d" or "Version" — that'll pinpoint the exact registry key blocking you.

I've seen this error pop up with SQL Server Management Studio, Visual Studio extensions, and printer drivers. The fix is always the same — remove or override the version check. Don't overthink it.