Fix ERROR_INSTALL_NOTUSED (0X00000662) Like a Real IT Pro

1. Stale Registry Leftovers from a Previous Install

This is the #1 reason you're seeing 0X00000662. Windows Installer remembers every component you've ever installed, and when it finds a registry key pointing to something that doesn't exist anymore, it throws this error. I had a client last month whose QuickBooks install kept failing with this — turns out an old trial version had left behind a dozen orphaned entries.

Here's the fix:

1. Press Win + R, type regedit, hit Enter.
2. Back up your registry first — File > Export, save a copy. I'm serious, one wrong delete and you're in for a bad day.
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData.
4. Look for subkeys related to the product you're trying to install. If you don't know the GUID, check HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products — match the product name there, then drill into the GUID.
5. Delete any folders that clearly belong to a previous version or failed install of the same software.
6. Close regedit and try the install again.

This works about 70% of the time. Don't go deleting random GUIDs — stick to the ones tied to the failed app.

2. Corrupted Windows Installer Engine

If the registry cleanup didn't help, the Windows Installer service itself might be hosed. This happens after a bad Windows Update or a crash mid-install. I've seen this on Windows 10 22H2 and Windows 11 23H2 — the MSI engine just stops recognizing valid components.

Here's the fix:

# Run as Administrator
msiexec /unregister
msiexec /regserver

Then restart the Windows Installer service:

1. Press Win + R, type services.msc, hit Enter.
2. Find Windows Installer, right-click, choose Stop.
3. Wait 10 seconds, then right-click again and choose Start.
4. Try your install again.

If that doesn't work, run the System File Checker:

sfc /scannow

Let it finish — it'll replace any corrupted system files. I've had this fix the error on a Dell OptiPlex that was refusing to install Adobe Reader. Weird, but it worked.

3. Conflicting Services or Apps in the Background

Sometimes the error is caused by something running in the background that's interfering with the installer. Antivirus software is the usual suspect — especially McAfee or Norton. But I've also seen it happen with old VPN clients like Cisco AnyConnect.

Here's the fix:

1. Press Win + R, type msconfig, hit Enter.
2. Go to the Services tab, check Hide all Microsoft services.
3. Click Disable all.
4. Go to the Startup tab, click Open Task Manager.
5. Disable every startup item.
6. Reboot. Windows will start with only essential services.
7. Try the install again.

If it works, enable services one at a time until you find the culprit. For me, it was a Lenovo update service that was blocking the MSI from writing its component data. Disabled that and never saw the error again.

Quick-Reference Summary Table

Start with the registry cleanup — it's the fastest and most common fix. If that doesn't work, move to the MSI reset. The clean boot is your last resort, but it's saved my skin more than once. Good luck — you'll beat this one.