Fix ERROR_SXS_DUPLICATE_PROGID (0X000036CA) Fast

You're trying to install or uninstall something, and Windows throws ERROR_SXS_DUPLICATE_PROGID (0X000036CA). Annoying as hell. The culprit here is almost always a corrupted or duplicate COM ProgID entry in the registry — usually from a failed uninstall or a botched update.

The Quick Fix: Regedit Cleanup

1. Press Win + R, type regedit, hit Enter.
2. Back up the registry first. File > Export > save a backup. Do this. Trust me.
3. Navigate to:
   

   HKEY_CLASSES_ROOT\CLSID
   HKEY_CLASSES_ROOT\Wow6432Node\CLSID (on 64-bit systems)

4. Press Ctrl + F, search for the ProgID from the error. The error doesn't always name it, so look for anything recent — app name, partial name, or GUIDs from software you just installed or uninstalled.
5. Delete the entire key that has the duplicate ProgID. Usually you'll see two keys with the same ProgID value. Keep the one from the OS or the legit app; delete the stray one.
6. Reboot. Retry the install.

Why This Works

Every COM object needs a unique ProgID. When two entries in the registry claim the same one, Windows Side-by-Side (SxS) activation chokes. This is common after an app update that leaves old registry entries behind, or when two apps register the same COM class (think: old and new versions of the same toolkit). The registry is a flat namespace there — duplicates aren't allowed. Deleting the orphan restores order.

Less Common Variations

Variation 1: The Error Points to a Side-by-Side Assembly Manifest

Sometimes the error shows up in Event Viewer as sxstrace.exe output. If so, run this command as admin to get a detailed log:

sxstrace.exe trace -logfile:sxs.etl
sxstrace.exe parse -logfile:sxs.etl -outfile:sxs.txt

Open sxs.txt — look for the exact DLL or OCX that failed. Re-register it with regsvr32:

regsvr32 /u C:\Path\To\File.dll
regsvr32 C:\Path\To\File.dll

Variation 2: The Error Happens During .NET Framework Install

If you're installing .NET Framework 3.5 or 4.x and hit this, the issue is usually a corrupted .NET installation or leftover from a previous version. Run the .NET Framework Repair Tool from Microsoft. If that fails, uninstall all .NET versions via Programs and Features (or DISM), then reinstall the one you need.

Variation 3: The Error Appears Randomly at Boot

This is rarer. It means a startup program or service can't register its COM object. Check Startup tab in Task Manager, disable recent entries. Also check Services.msc for any service that failed to start. Look for one with a dependency on a COM class — disable or reinstall that service's host app.

Prevention

Don't skip the uninstaller. Use the official uninstall tool for the app. If an app has its own cleanup utility (like CCleaner for some), run it after uninstalling. Keep your system clean — I've seen this error from antivirus software that orphaned ProgIDs after removal. Also, make sure you're using the right installer for your OS architecture (32-bit vs 64-bit). A 32-bit installer on a 64-bit OS can sometimes write to both CLSID hives and cause a duplicate if the app is dumb about it.

Finally, if you see this error more than once on the same machine, run a registry cleaner like Autoruns from Sysinternals or RegScanner to scan for leftover CLSID entries after uninstalling software. Manually deleting them is safer than automated cleaners, but use what you're comfortable with.