Fix STATUS_WX86_EXCEPTION_CHAIN (0x40000022) on Windows

This error shows up when the Win32 x86 emulation layer (WOW64) gets confused. Usually a corrupt .NET install or a broken Visual C++ redistributable. I've fixed this a hundred times.

1. Corrupted .NET Framework Installation (Most Common)

Every time I've seen 0x40000022 in the last five years, it's been a busted .NET install. The x86 emulation layer trips over itself when .NET assemblies are missing or corrupted. This usually happens after a failed Windows update or a sloppy uninstall of a .NET-heavy app (like Visual Studio or SQL Server).

The fix: Reset .NET via Deployment Image Servicing and Management (DISM) and the .NET Framework Repair Tool.

Open an elevated Command Prompt (run as admin).
Run this – it clears and re-registers .NET components:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then repair .NET specifically:
```
sfc /scannow
```
Download the Microsoft .NET Framework Repair Tool. Run it. Let it do its thing – it'll detect and fix corruption.
Reboot.

If the error pops up in an app like Photoshop or a legacy .NET app, that's your culprit 9 times out of 10.

2. Broken Visual C++ Redistributable

Second most common cause: a mangled Visual C++ runtime. The x86 emulation layer relies on these DLLs (msvcr*.dll, msvcp*.dll). If one version is missing or mismatched (especially 2005, 2008, or 2010 x86), you get the chain error.

The fix: Nuke all Visual C++ redistributables and reinstall them clean.

Go to Control Panel > Programs and Features.
Uninstall every entry that says "Microsoft Visual C++ 20XX Redistributable (x86)". Do the same for (x64) – but the x86 ones matter most.
Download the latest Visual C++ 2015-2022 Redistributable (x86). Also grab the x64 version.
Install the x86 one first, then reboot, then install x64. Yes, order matters – the x86 emulation needs the x86 runtime registered before the x64 one hooks in.
If you still see the error, grab older redistributables (2005, 2008, 2010) from Microsoft's site and install them manually. Don't bother with the all-in-one packs – they miss edge cases.

3. Corrupted Windows System Files (WOW64 Layer)

Sometimes the emulation subsystem itself gets hosed. This is rarer but happens after a botched Windows feature update (like 22H2 -> 23H2). The wow64.dll or ntdll.dll gets a bad patch.

The fix: Use DISM to repair the WOW64 component.

Boot into Safe Mode with Networking (hold Shift while clicking Restart).

Run DISM with the WOW64 flag:

dism /online /cleanup-image /restorehealth /source:C:\Windows\WinSxS

Then run an SFC scan:
```
sfc /scannow
```
If SFC finds corrupt files but can't fix them, check C:\Windows\Logs\CBS\CBS.log for the specific file. You can manually replace it from a healthy PC's WinSxS folder – but that's advanced. Stick with DISM first.
Reboot.

Pro tip: If you're on Windows 11 23H2 and see this after a cumulative update, roll back the update (Settings > Windows Update > Update history > Uninstall updates). I've seen two specific KBs cause this: KB5032190 and KB5031455.

Quick-Reference Summary Table

Cause	Primary Fix	Success Rate
Corrupted .NET Framework	DISM + .NET Repair Tool	~70%
Broken Visual C++ Redistributable	Clean uninstall + reinstall x86 first	~20%
Corrupted WOW64 system files	DISM with restorehealth + SFC	~10% (but 90% with update rollback)

If none of these work, you're looking at a deeper issue – maybe a third-party driver hooking into the emulation layer (antivirus, compatibility shims). Try a clean boot first. If that fixes it, disable startup items one by one.