You hit 0xC000026F. Let's cut through the noise.
This status code — STATUS_WX86_INTERNAL_ERROR — means the Windows-on-Windows 64-bit (WOW64) layer that runs 32-bit programs on 64-bit Windows crashed internally. I've seen it most often on Windows 10 version 21H2 and Windows 11 after a botched update, or when trying to launch an old game like Fallout 3 or SimCity 4 that depends on the x86 emulation.
The real fix: clean the system files first
Run these two commands in an elevated Command Prompt (right-click Command Prompt, "Run as administrator"). Do them in order:
DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOWWhy this order? DISM fixes the system image itself — the source files that SFC uses to replace corrupted files. If you run SFC first, it might try to fix things using a corrupted image and fail silently. DISM first ensures the repair source is clean.
After both complete, restart your PC. If the error came from a specific program, try launching it again.
Why this works
WOW64 is implemented in ntdll.dll, wow64.dll, wow64win.dll, and wow64cpu.dll. When these files get corrupted — usually from a partial Windows update, a disk error, or a bad third-party installer — the emulation layer trips over itself. The 0xC000026F code is essentially WOW64 saying "I can't make sense of my own internals." SFC repairs these specific DLLs from the component store, which DISM just verified.
When SFC and DISM don't cut it
Sometimes the system files are fine, and the problem is in the application itself. This happens with older software that bundles its own 32-bit runtime, like an ancient msvcrt.dll or mfc42.dll that conflicts with WOW64. Try these in order:
- Reinstall the problematic program. Uninstall it completely, restart, then download a fresh copy from the developer's site. Don't use a cached installer — it might be corrupted too.
- Run the program in Windows 7 compatibility mode. Right-click the executable > Properties > Compatibility tab > check "Run this program in compatibility mode for" and pick Windows 7. This forces WOW64 to use a slightly different emulation path that bypasses some internal checks.
- Disable the NTVDM subsystem if you're running 16-bit installers. Some old game installers are 16-bit, and Windows 64-bit can't run those at all. You'll get a different error though — usually
0xC0000135or0xC0000142. If you're here, you need a virtual machine.
A less common cause: registry corruption in the WOW64 keys
The WOW64 layer reads from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node for 32-bit applications. If a program's uninstaller or an installer left garbage here, it can confuse the emulation. Open Regedit and navigate there. Look for orphaned entries — keys with no corresponding program files. Delete them only if you're certain they're dead. A safer route: use a tool like CCleaner's registry cleaner, but I don't trust automated cleaners blindly. Manual inspection is better.
Prevention going forward
- Never kill Windows Update mid-install. Let it finish even if it's slow. Partial updates are the #1 cause of WOW64 corruption.
- Run SFC and DISM monthly. I do it on the first of every month. It catches file rot before it bites you.
- Stick to 64-bit apps where possible. They don't touch WOW64 at all. If you must run 32-bit software, keep it updated — the developer may have fixed a WOW64 compatibility issue.
- Check your disk health. Use
chkdsk /fto find and fix bad sectors. File corruption starts at the hardware level.
One last thing: If you see this error during Windows Setup itself, your installer media is corrupted. Redownload the ISO and recreate the bootable USB. Don't try to repair it — start fresh.