Fix 0xC0150003 SXS Invalid Activation Context Data

What is 0xC0150003?

Short version: Windows can't read the activation context for an app — that's a fancy way of saying the app's side-by-side assembly data is garbage. You'll see this when launching software after a botched update, a partial uninstall, or disk corruption. The most common trigger I've seen: someone installed a Visual C++ Redistributable, it got half-broken by a Windows update, and now every app that depends on it throws this exact code.

Good news: you don't need to reinstall Windows. Bad news: you might need to dig into the Component Store. Let's go from fastest to most thorough.

Fix 1 (30 seconds): Reboot into Safe Mode and retry

I know it sounds stupid, but I've seen this error pop up when third-party DLL injection (antivirus overlays, launcher hooks) corrupts the activation context at runtime. A clean boot or Safe Mode can confirm that.

1. Press Win + R, type msconfig, go to the Boot tab, check Safe boot (Minimal), and restart.
2. Launch the app that was failing. If it works, the problem is a background service or startup program. Run msconfig again, uncheck Safe boot, and disable suspicious startup items via Task Manager.
3. If it still fails in Safe Mode, move to Fix 2.

Don't bother with updating drivers or running CCleaner here. That won't touch the SXS store.

Fix 2 (5 minutes): Repair the Visual C++ Redistributables

This is the culprit 80% of the time. The app you're running likely depends on msvcr*.dll or msvcp*.dll. If the merge module registry entries are hosed, you get exactly this error.

1. Open Settings → Apps → Installed apps (or Control Panel → Programs and Features).
2. Search for Microsoft Visual C++ 2015-2022 Redistributable (both x86 and x64). Also look for older ones like 2008, 2010, 2013 — any of them could be involved.
3. Right-click each and choose Change, then Repair. Do it for both the x86 and x64 versions, even if your app is 64-bit. Many installers pull in both.
4. Reboot and test the app.

If Repair isn't available or doesn't work, uninstall all VC++ redistributables, then reinstall the latest from Microsoft's official download page: https://aka.ms/vs/17/release/vc_redist.x64.exe (and the x86 version as well). Install x86 first, then x64.

Also consider .NET Framework. Some apps need a specific version. Run the .NET Framework Repair Tool from Microsoft — it's a one-click fixer that handles registry corruption and missing servicing entries.

Fix 3 (15+ minutes): System File Checker and DISM

If the above didn't fix it, the Windows Side-by-Side store itself is corrupted. Don't skip this — it's the actual system component that validates those activation contexts.

First, run DISM to repair the component store. SFC alone won't cut it because it reads from that same store.

DISM /Online /Cleanup-Image /RestoreHealth

Let it finish — might take 10-20 minutes. Then run SFC:

sfc /scannow

Restart. If the error persists, you're looking at a deeper issue.

Fix 4 (advanced, 30 min): Nuke and re-register the SXS store

This is the nuclear option, but it's less painful than a full reinstall. You're going to force Windows to rebuild the Component Store from scratch. Backup first. Seriously. Or at least have a recent restore point.

1. Boot into Windows Recovery Environment. You can do this by holding Shift while clicking Restart, or use a Windows installation USB.
2. Open Command Prompt from Troubleshoot → Advanced Options.
3. Plan: delete the existing store and let Windows recreate it. But you can't delete it while the OS is running.

Here's the trick — run the following in the recovery command prompt. Replace C: with your actual Windows drive letter (often it's D: in recovery).

cd /d C:\Windows\WinSxS

No, I'm not going to tell you to delete WinSxS — that's a myth and it'll brick your system. Instead, use the built-in cleanup:

DISM /Image:C:\ /Cleanup-Image /StartComponentCleanup /ResetBase

This resets the base of the component store, stripping out superseded versions. It's safe and takes about 15 minutes. Then restart and see if the error's gone.

If that still fails, you can try a repair install (in-place upgrade) using the Windows Media Creation Tool. It reinstalls the OS while keeping your files and apps. That's the last resort before a clean install — and in 14 years, I've only had to do that twice for this specific error.

Why you shouldn't bother with registry tweaks

Some forums will tell you to hunt down HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide and change flags. Skip that. The SXS subsystem doesn't read a simple flag that will fix this. You'll just make things worse. Stick to the proper repair paths above.

If you still get the error after Fix 4, the app itself is probably compiled against a runtime that's genuinely incompatible with your Windows build. Check the app's support page for a Windows 10/11 specific version. Most likely though, Fix 2 does the job. Go do that first.