SXS Process Default Already Set (0x000036BB) Fix

Quick answer

Run sfc /scannow from an admin command prompt, then reboot. If that fails, check for corrupt side-by-side assemblies by running DISM /Online /Cleanup-Image /RestoreHealth. The error means a process tried to set a default activation context when one already existed—usually from a bad manifest or COM registration.

What's actually happening here

Windows side-by-side assemblies (SxS) manage DLL versions using activation contexts. Each process can have one default activation context—think of it as the master manifest that tells Windows which versions of common controls, CRT, or COM objects to load. When you see 0x000036BB, some code called ActivateActCtx with the ACTCTX_FLAG_PROCESS_DEFAULT flag, but a default context was already set. This typically happens when:

• A COM object or application loads a manifest that conflicts with an already-active default context.
• Third-party software (like antivirus or shell extensions) injects its own manifest into a process.
• Windows itself gets confused after a botched update or system file corruption.

I've seen this error most often with older apps (pre-2015) that try to set their own default manifest but run inside a host process that already has one—like when you launch an old game from Steam's browser overlay, or a custom shell extension crashes Explorer. The error code 0x000036BB (decimal 14011) translates to ERROR_SXS_PROCESS_DEFAULT_ALREADY_SET in winerror.h.

Fix steps (order matters)

1. Run System File Checker — Open an admin command prompt (right-click Start > Windows Terminal (Admin) or Command Prompt (Admin)). Type sfc /scannow and let it finish. This checks core system files, including SxS manifest files in C:\Windows\WinSxS. If it finds corruption, reboot and retest the app.
2. Run DISM to repair component store — SFC can only fix files it knows about. If the component store itself is broken, SFC won't help. Run DISM /Online /Cleanup-Image /RestoreHealth. This downloads fresh system files from Windows Update. Takes 5-15 minutes. Reboot after.
3. Reset Windows Update components — Sometimes the SxS pileup happens after a failed update. Stop the update services, clear the cache, restart them. Run these as admin:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Reboot and try the failing app again.

4. Check for corrupt COM registration — Some COM objects (especially those using manifest-based registration) can leave orphaned activation contexts. Use OleView.exe (part of Windows SDK) or regedit to inspect HKEY_CLASSES_ROOT\CLSID and HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID for entries referencing missing DLLs. This is advanced—only do this if you know what you're looking for.

Alternative fixes if the main ones fail

• Reinstall the application — Uninstall the specific app that triggers the error, reboot, then reinstall as admin (right-click installer > Run as administrator). This forces a fresh manifest registration.
• Disable third-party shell extensions — Use ShellExView from Nirsoft to disable non-Microsoft shell extensions. Reboot and test. The error often comes from context menu handlers or property sheet handlers that try to set their own default context.
• System Restore — If the error started after a driver install or update, roll back to a point before it happened. rstrui.exe from an admin prompt.
• Repair install Windows — In-place upgrade using the Windows 10/11 Media Creation Tool. Keeps your files and apps but replaces all system files. This is your nuclear option—fixes SxS corruption 99% of the time.

Prevention tip

Keep Windows Update running. Most SxS corruption comes from interrupted updates or manual registry edits. Don't use registry cleaners—they're garbage and routinely break SxS manifests. If you develop software, never call ActivateActCtx with ACTCTX_FLAG_PROCESS_DEFAULT from inside a COM DLL or a thread that inherited a default context. Check GetLastError after activation and handle ERROR_SXS_PROCESS_DEFAULT_ALREADY_SET gracefully.