ERROR_SXS_ACTIVATION_CONTEXT_DISABLED Fix: 0x000036B6

I know this error is infuriating. You double-click your app, nothing happens, or you get a generic crash. Behind the scenes, Windows finds the side-by-side activation context — the manifest that tells the app which DLLs to use — but that context is marked disabled. The system won't let the app start.

The error code is 0x000036B6, also called ERROR_SXS_ACTIVATION_CONTEXT_DISABLED. In my years running a help desk blog, I saw this mostly with older applications that depend on specific Visual C++ redistributable versions. It also happens when a registry key gets corrupted or when a program installation didn't finish cleanly.

Let me walk you through the three most common causes and their fixes. I'll start with the one that fixes it for most people.

Cause 1: Corrupted Visual C++ Redistributable (The Most Common Cause)

This is the one I see all the time. The app you're trying to run — maybe an old game, a business tool, or some utility — relies on a specific VC++ runtime. If that runtime's manifest or DLL got mangled (by a partial uninstall, a disk error, or a bad Windows update), the activation context gets disabled.

The fix: Uninstall all VC++ redistributables, then reinstall them fresh. Yes, all of them. Don't pick and choose — you'll miss one.

1. Open Settings > Apps > Installed apps (or Programs and Features in Control Panel).
2. Sort by name. Look for any entry starting with "Microsoft Visual C++ 20XX Redistributable".
3. Uninstall every single one, from 2005 through 2022. Do not skip any — even if you think you don't need it.
4. Reboot your PC.
5. Download the latest all-in-one VC++ installer from this official Microsoft link (x64) or the x86 version if your app is 32-bit. Run the installer.
6. Reboot again. Try your app.

I've fixed hundreds of these errors this way. It works because you're replacing the broken activation context with a clean one from Microsoft's latest package. The runtime installer rebuilds the entire side-by-side cache for that version.

If that doesn't help, move to the next cause.

Cause 2: Registry Key Marking the Context as Disabled

Sometimes the issue is in the registry. A key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide can get a value like DisabledContexts or DisableActivationContext set to 1. This disables the activation context system-wide for certain manifests.

I've seen this happen after a third-party uninstaller messes up, or after a virus scanner quarantines a manifest file and leaves a registry marker behind.

The fix: Check and delete the offending registry value.

1. Press Win + R, type regedit, hit Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide.
3. Look for any of these values in the right pane:
   • DisabledContexts
   • DisableActivationContext
   • ActivationContextDisabled
4. If any of them exists and has a value of 1, right-click it > Delete.
5. Close regedit. Reboot. Test your app.

I'll be honest — this cause isn't as common as the first one, but when it's the root, the registry fix is the only thing that works. Don't skip it if the VC++ reinstall didn't solve it.

Cause 3: Corrupted Windows Side-by-Side (SxS) Store

This is the rarer, more annoying cause. The system's side-by-side store itself — the folder at C:\Windows\WinSxS — can get corrupted. This usually happens after a failed Windows update, a disk corruption event, or if someone manually deleted files from it (please don't ever do that).

When the SxS store is corrupt, the activation context for any app that uses a common library (like the VC++ runtime) can get disabled because the system can't validate the manifest against the store correctly.

The fix: Run sfc /scannow and DISM to repair the store.

1. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Terminal (Admin)).
2. Run this command:

   sfc /scannow

3. Let SFC finish. It'll fix any corrupt system files it finds.
4. After SFC completes, run:

   DISM /Online /Cleanup-Image /RestoreHealth

5. Wait for DISM to finish. This can take 15-20 minutes.
6. Reboot and test your app.

If DISM fails, you might need to use an installation media source. But for most people, the online restore works fine.

Quick-Reference Summary Table

In my experience, 9 out of 10 times the VC++ reinstall fixes it. The registry tweak covers the other 5% of cases. The SxS store repair is the last resort. Try them in order and you'll be back up and running quickly.