STATUS_SXS_SETTING_NOT_REGISTERED (0XC0150023) Fix

Cause 1: Corrupted or Missing Visual C++ Redistributables

This is the one I see most often. The error 0XC0150023 pops up right when you launch an app — usually an older game, a CAD tool, or something from 2010-2015. The app expects a specific version of the Visual C++ runtime (2005, 2008, 2010, etc.) and the side-by-side assembly manifest can't find it. The culprit here is almost always a partial uninstall or a bad update that left the registry entry but trashed the DLL.

Fix: Reinstall All Visual C++ Redistributables

1. Open Control Panel > Programs and Features
2. Uninstall every Microsoft Visual C++ Redistributable you see. Don't skip any.
3. Restart your machine.
4. Download the all-in-one package from the official Microsoft site. I use the direct links from Microsoft's VC++ page. Get both x86 and x64 versions.
5. Install them in this order: x86 first, then x64. Reboot after each.

Don't bother with third-party "all-in-one" packs. I've seen those cause more problems than they solve. Stick to Microsoft's official installers.

Cause 2: Corrupt Side-by-Side (SxS) Cache

If reinstalling VC++ doesn't do it, the Windows side-by-side cache itself is probably hosed. This cache lives under C:\Windows\WinSxS and contains all the manifest files and assemblies. A botched Windows update or a disk error can corrupt it. The error will show when you run sxstrace.exe — it'll say something like "Setting not registered" for a specific manifest.

Fix: Use the System File Checker and DISM

1. Open Command Prompt as Administrator.
2. Run sfc /scannow. Let it finish. That takes 15-20 minutes.
3. If it finds corrupt files but can't fix them (common with SxS corruption), run DISM /Online /Cleanup-Image /RestoreHealth. This downloads fresh copies from Windows Update.
4. After DISM finishes, run sfc /scannow again.

This fixes about 60% of SxS corruption cases. If it doesn't, you're looking at an in-place upgrade repair install — that's the nuclear option. It keeps your files and apps but replaces all system files. Boot from a Windows install ISO, choose "Upgrade", and select "Keep personal files and apps".

Cause 3: Missing or Mismatched Application Manifest

Sometimes the app itself has a bad embedded manifest. This is rarer, but I've seen it with poorly ported games and custom business software. The manifest references a specific version of a runtime that doesn't exist on your system — even after you've installed all VC++ versions.

Fix: Check the Event Log and Extract the Manifest

1. Open Event Viewer > Windows Logs > Application
2. Look for an error from SideBySide source. The details will show the exact assembly name and version it's looking for.
3. If the missing assembly is an older VC++ runtime (like 8.0 or 9.0), you can manually download that specific redistributable from Microsoft's Download Center.
4. Alternatively, use sxstrace.exe to get a verbose log:

   sxstrace.exe Trace -logfile:sxs.etl
   sxstrace.exe Parse -logfile:sxs.etl -outfile:sxs.txt

   Then open sxs.txt — it shows exactly which setting is missing.

In one case, the manifest demanded a 32-bit runtime on a 64-bit app. That was a developer screw-up. The fix involved contacting the vendor for a corrected install.

Quick Reference Summary

Start with Cause 1. It's quick, safe, and fixes most cases. If that doesn't work, move to Cause 2. Skip straight to Cause 3 only if you see the error on a specific app that worked elsewhere.