Fix 0xC0150011 STATUS_SXS_MULTIPLE_DEACTIVATION on Windows

This error pops up when a program tries to close an activation context that's already closed. Usually triggered by broken Visual C++ redistributables or corrupt Winsxs store.

When This Error Hits

You're running an application — maybe an old game, a CAD tool, or some enterprise software — and then it crashes. Or you try to install a Visual C++ redistributable and the installer throws 0xC0150011. The event log shows STATUS_SXS_MULTIPLE_DEACTIVATION. I've seen this most often after a failed Windows update or after uninstalling a Visual C++ runtime manually.

What's Actually Happening

Windows uses activation contexts to manage which DLLs a program sees. Think of it as a sandbox that tells the app "these are your side-by-side assemblies." When the app shuts down, it tells Windows "I'm done with this context." The error means the program tried to deactivate a context that was already released — a double free for the OS loader. The culprit here is almost always a corrupted side-by-side (SxS) store or a busted Visual C++ redistributable.

Don't bother reinstalling the affected app first — that rarely helps. The problem sits at the system level: missing or broken manifests or manifest entries that point to a context that's already gone.

The Fix: Step by Step

Step 1: Repair Visual C++ Redistributables

This fixes 90% of cases. Download the Visual C++ 2015-2022 Redistributable (x86) and x64. Run each installer and choose Repair. If that fails, uninstall all Visual C++ redistributables via Programs and Features, then reinstall from scratch — install the oldest first (2005, 2008, 2010, 2012, 2013, then 2015-2022).

Step 2: Run DISM and SFC

Open an elevated Command Prompt (right-click Start > Terminal Admin). Run these commands in order:

DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

DISM fixes the component store. SFC checks system files. Reboot after both complete.

Step 3: Reset Windows Update Components

Corrupt update metadata can mess with the SxS store. Run the Windows Update Troubleshooter from Settings > System > Troubleshoot > Other troubleshooters. If that doesn't cut it, use the Microsoft Update Reset script or manually reset the update cache:

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

Step 4 (Advanced): Rebuild the Winsxs Store

This is the nuclear option. Only do this if the error persists and you're on Windows 10/11 Pro or Enterprise. Mount the Windows ISO, then from an elevated command prompt:

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

Replace E: with your ISO drive letter. This trims the store and replaces bad files from the install image.

What to Check If It Still Fails

Event Viewer: Look under Windows Logs > Application for events with source "SideBySide" or "Microsoft-Windows-SideBySide". The details often name the exact assembly — like Microsoft.VC80.CRT or Microsoft.VC90.CRT. That tells you which runtime is broken.
Third-party software: Some apps install their own WinSxs manifests. Antivirus suites and VPN clients are notorious for this. Try uninstalling any recently added security software.
Check for pending reboots: A pending file rename operation can corrupt activation contexts. Run reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations — if it returns data, reboot.

If nothing above works, you're looking at a repair install of Windows. Use the "Keep my files" option in Settings > Recovery > Reset this PC. That preserves apps and data but rebuilds the entire component store. It's drastic, but I've never seen 0xC0150011 survive it.