Fix STATUS_SXS_CANT_GEN_ACTCTX (0xC0150002) fast

You're staring at the 0xC0150002 error — let's kill it

I know the feeling. You double-click an app and get that ugly popup: "The application was unable to start correctly (0xc0150002)." Or worse, a generic side-by-side configuration error. I've seen this on everything from old accounting software to modern CAD tools. The fix is usually simple.

The real fix: Reinstall Visual C++ Redistributables

This error means Windows can't generate an activation context for a side-by-side assembly. In plain English: a required VC++ runtime DLL is missing or busted. 90% of the time, reinstalling the Visual C++ Redistributables does the trick.

1. Open Control Panel > Programs > Uninstall a program.
2. Uninstall every Microsoft Visual C++ Redistributable you see, from 2005 through 2015-2022. Don't skip any — they stack.
3. Download the latest all-in-one package from Microsoft: vc_redist.x64.exe (or x86 if your app is 32-bit).
4. Run the installer. Reboot.
5. Try your app again.

Had a client last month whose entire print queue died because of this — their label printer software couldn't load after a Windows update. Reinstalling the VC++ runtimes fixed it in under 5 minutes.

Why this works

Windows uses a side-by-side assembly system to avoid DLL hell. Each app requests a specific version of a VC++ runtime through a .manifest file. When that runtime is missing or corrupted, the activation context fails. The error code 0xC0150002 is the system's way of saying "I can't find what this app needs."

Reinstalling the runtimes resets the assembly cache and puts the correct DLLs back. Skip the "repair" option in Programs — a full reinstall is cleaner.

Less common variations of the same issue

1. Corrupted system files

If reinstalling VC++ doesn't work, the Windows component store might be borked. Run these commands in an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

This fixes the system file integrity. I've seen a single corrupt advapi32.dll cause this error on a Windows 10 22H2 machine.

2. A specific app's manifest is bad

Some poorly written apps embed their own manifest inside the EXE. If that manifest has a typo or references a nonexistent assembly version, you'll get this error. Extract the manifest with Resource Hacker or mt.exe and look for version mismatches. Rare, but happens with old custom line-of-business apps.

3. Windows update broke something

KB5030211 (October 2023) caused this on some systems for apps using older CRT (2005-2008). Roll back the update or reinstall the specific VC++ 2005 runtime from Microsoft's download center. Don't use the all-in-one packager for that — it's outdated.

Prevention tips

• Keep VC++ runtimes updated. Install every new version when they drop — Microsoft puts out updates for security and compatibility.
• Don't clean out runtimes. Apps often rely on multiple versions. The 2005 runtime isn't dead yet — I've seen it in hospital software from 2019.
• Run sfc /scannow monthly. Catches corruption before it bites you.

That's it. If you followed the steps above, the error should be gone. If not, you're likely dealing with a broken app install — reinstall the offending program itself.