Fix ERROR_INSTALL_SUSPEND (0x00000644) on Windows

Quick answer

Stop the Windows Installer service, kill any orphaned msiexec.exe processes, then restart the service and try your install again. If that fails, run msiexec /unregister followed by msiexec /regserver from an admin command prompt.

What's actually happening here

Windows returns ERROR_INSTALL_SUSPEND (0x00000664) when the MSI engine detects that an installation is already in progress but in a suspended state. This isn't a generic 'something went wrong' error — it's the installer saying 'I see a partially completed transaction that never finished, and I refuse to start a new one until that's resolved.'

The typical trigger is a previous installation that got interrupted. Maybe you force-killed the setup midway, the system crashed during an MSI install, or a software update got stuck at 90% and you rebooted. Windows Installer tracks state in a mutex — a kernel-level lock — and until that mutex is released, no new MSI-based installers will run. You'll see this with pretty much any .msi package: Office updates, Visual C++ redistributables, printer drivers, or even Skype.

Fix steps

Kill all msiexec.exe processes. Open Task Manager (Ctrl+Shift+Esc), go to the Details tab, sort by name, find any msiexec.exe entries. Right-click each and choose End task. If you see one you can't kill, skip to step 3 — that process might be stuck in a non-terminable state.
Restart the Windows Installer service. Open services.msc (Win+R, type it in). Find Windows Installer in the list. Right-click it and choose Restart. If it's not running, start it. Then try your installation again.
Clear the MSI mutex manually. If step 2 didn't work, the orphaned mutex is still held. Open Command Prompt as Administrator. Run:
```
msiexec /unregister
```
Then:
```
msiexec /regserver
```
This unregisters and re-registers the Windows Installer COM components and clears any stale mutex. You'll see no confirmation message — that's normal. After this, try your install.
Clean up pending file rename operations. Sometimes the installer leaves a pending rename in the registry. Open Regedit (admin) and go to:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
```
Look for a value called PendingFileRenameOperations. If it exists and contains entries, delete the contents (not the key itself) — clear the multi-string value. Reboot, then try installing again.

Alternative fixes if the main steps don't work

Run the Microsoft Program Install and Uninstall Troubleshooter. Download it from Microsoft's site (search for 'program install uninstall troubleshooter'). It automates the registry and service checks above. I've seen it fix edge cases where manual steps failed, especially on Windows 10 20H2 and later.
Boot into Safe Mode with Networking. Reboot, hold Shift while clicking Restart, go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 5 for Safe Mode with Networking. In Safe Mode, the Windows Installer service starts clean with no leftover mutexes. Run your installation there. This works when the mutex is held by a third-party service that doesn't start in Safe Mode.
Use Process Explorer to find the culprit. Run procexp.exe from Sysinternals. Press Ctrl+F, search for 'msiexec' or 'Install'. Look for any handle or DLL held by a non-Microsoft process. If you find one (common culprits: antivirus real-time scanners, backup software, or Dell/HP update utilities), terminate that process and retry.

Preventing this from happening again

The root cause is almost always a killed installer or a crash during setup. To minimize recurrence:

Never force-close an MSI-based installer. If it seems stuck, wait at least five minutes before taking action. Many MSI packages look frozen while they do COM registration in the background.
When you need to cancel an install, use the installer's own Cancel button, not Task Manager's End task. This lets Windows clean up the mutex properly.
Keep your system stable during large updates. Don't install Windows updates while running heavy games or VMs. A BSOD during a cumulative update is a classic cause of this error.
If you regularly hit this, check your event logs under Applications and Services Logs > Microsoft > Windows > MsiInstaller for Event ID 11728 — it'll tell you which product left the session hanging. Then you can specifically reinstall or uninstall that product to clear the state.

One last thing: 0x00000644 is specific to MSI transactions. If your installer isn't an .msi (like an .exe bootstrapper that downloads files), you might be dealing with a different error — look at the exact code in the log, not just the message text. But 9 times out of 10, the service restart and mutex clear gets you back in business.