Fix Windows Installer Error 0X0000065F (ERROR_CREATE_FAILED)

You see error ERROR_CREATE_FAILED (0X0000065F) when starting the Windows Installer service? It usually hits right after a botched MSI install — think a .NET framework update that crashed halfway, or an Office install that left junk behind. I've also seen it on Windows Server 2019 machines after a third-party security tool decided to "lock down" the service. The core issue? The service can't initialize because either the registry key for the service is missing or the msiexec.exe binary itself is hosed.

What actually causes this

The Windows Installer service relies on a specific set of registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver. If one of those keys gets deleted (malware, bad uninstaller, or a corrupt patch) the service fails to load. Another common culprit: a damaged msiexec.exe in C:\Windows\System32 — usually from a .NET framework repair that went sideways. Don't bother checking event logs first; they'll just say "service failed to start" without the real detail. The fix is straightforward.

The fix: 4 steps that actually work

I've done this across hundreds of machines. Stick to these steps in order. Don't skip around.

Check the registry key exists
Open regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver. If the entire key is missing — that's your problem. If it's there but has strange values (e.g., ImagePath pointing to a non-existent file), note the current values. You'll rebuild this key if needed.
Rebuild the service registry key (only if missing)
Export the same key from a healthy machine of the same OS version (Windows 10 22H2, Server 2022, etc.). Copy the .reg file over, double-click to merge. If you don't have a spare machine, use this as a template — but replace the OS-specific GUID paths. For Windows 10/11, the default ImagePath is:
```
%systemroot%\system32\msiexec.exe /V
```
Run System File Checker on msiexec
Open an admin command prompt and run:
```
sfc /scanfile=C:\Windows\System32\msiexec.exe
```
This checks only that binary. If it reports corruption, run a full SFC next:
```
sfc /scannow
```
Wait for it to finish. If SFC finds issues but can't fix them, move to step 4.
Run DISM to restore system health
DISM can fix the underlying component store that SFC relies on. Run:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
This takes 10-20 minutes. After it completes, re-run sfc /scannow. Then try restarting the Windows Installer service.

Still failing? Check these gotchas

Third-party security software — Some AV suites (looking at you, McAfee and Symantec) hook into MSI and block the service. Temporarily disable the AV, then try starting the service. If it works, add an exclusion for %windir%\system32\msiexec.exe.
Corrupt Windows Installer cache folder — The C:\Windows\Installer folder stores cached MSI files. If that folder is full or has locked files, the service can't create new install sessions. Clear it? No — that breaks existing installed apps. Instead, run msiexec /unregister then msiexec /regserver from an admin prompt.
DCOM permissions — Rare, but I've seen it. Check DCOM permissions for the Windows Installer service. Open dcomcnfg → Component Services → Computers → My Computer → DCOM Config → Windows Installer. Right-click, Properties, Security tab. Ensure Launch and Activation Permissions include LOCAL SERVICE with Allow. If not, add it.
Last resort: restore from backup — If you have a system state backup from before the issue started, restore the registry hive for SYSTEM. This is faster than rebuilding from scratch.

If none of that works, you're looking at a corrupt OS installation. At that point, an in-place upgrade (Windows 10/11 repair install) or a server rebuild is the only reliable fix. Don't waste hours chasing obscure DLL registrations — the service won't start without a clean binary and a valid registry key.