You're staring at the 0x00000654 error when trying to install software. It's frustrating, but I've fixed this dozens of times — here's the solution.
The Fix (Works 95% of the time)
Skip all the registry cleaning nonsense. The culprit here is almost always a corrupted download or a file that Windows blocked for safety reasons. Here's what you do:
- Re-download the installer from the official source. Use a different browser if possible. I've seen Chrome cache a bad version while Edge works fine.
- Right-click the installer file and select
Properties. If you see an "Unblock" checkbox at the bottom, check it and hit Apply. - Run the installer as Administrator — right-click it and choose
Run as administrator.
That's it. Nine out of ten times that unblock checkbox is the culprit. Windows Defender sometimes flags legitimate MSI files as unsafe just because they came from the internet.
Why This Works
Error 0x00000654 is Windows telling you the MSI file isn't valid. The most common reason: the file header got corrupted during download. A partial download, a network hiccup, or your antivirus stripping out chunks of the installer can leave the file malformed.
The unblock checkbox removes the "Mark of the Web" flag that Windows adds to downloaded files. When that flag is present, the Windows Installer service treats the file with suspicion and won't open it properly. It's a security feature that backfires more often than it helps.
Running as admin bypasses any permission restrictions that might prevent the installer from accessing temp directories or writing to protected areas of the registry.
When the Simple Fix Doesn't Work
If you still get the error after re-downloading and unblocking, try these in order:
1. Restart the Windows Installer service
net stop msiserver
net start msiserverRun that from an elevated command prompt. I've seen the service hang after a failed install attempt, and it won't pick up new MSI files until you bounce it.
2. Clean your Temp folders
%temp%Type that into the Run box (Win+R). Delete everything in there. Old cached installers from failed attempts can interfere with new ones.
3. Check for disk corruption
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthRun SFC first, then DISM if SFC reports issues. System file corruption can break the Windows Installer engine itself.
Less Common Variations
Sometimes you'll see this error with a specific line like "This installation package could not be opened. Verify that it exists and that you can access it." That usually means the file path is too long. Move the installer to C:\Temp or the desktop — short path, no spaces.
On Windows 11 22H2 and later, I've seen this error pop up when the installer was downloaded through a corporate VPN. The VPN's traffic inspection often corrupts the file. Download it without the VPN active.
Another variation: the error appears only for 64-bit installers on 32-bit systems. Check your Windows architecture in System Information. You can't install 64-bit software on a 32-bit OS.
Prevention
Always verify the checksum of the installer against the publisher's website when available. A simple SHA-256 check can save you 20 minutes of troubleshooting. Tools like CertUtil -hashfile installer.msi SHA256 work from the command line.
Also, don't interrupt downloads. Close other bandwidth-heavy apps when grabbing MSI files. A 30-second dropout can ruin an installer.
Finally, if you're deploying software across multiple machines, use a tool like PDQ Deploy or a group policy object. Pushing an already-verified MSI from a network share avoids the download corruption problem entirely.