STATUS_WX86_SINGLE_STEP (0x4000001E) – The Real Fix

Quick Answer

Kill any running debuggers (Visual Studio, WinDbg, ollydbg), then run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth. If that doesn't stick, delete the WOW64 registry key under HKLM\SYSTEM\CurrentControlSet\Control\WOW and reboot.

What's Going On Here

This status code comes from the Windows on Windows 64 (WOW64) subsystem. It's not a crash in your app — it's the emulator telling the system it hit a single-step interrupt. Usually that's a debugger artifact. I've seen this most often when someone tries to debug a 32-bit app on a 64-bit system and the debugger leaves a TF (trap flag) set in the EFLAGS register. The culprit here is almost always Visual Studio forgetting to clear the flag after a breakpoint, or a kernel debugger messing with the emulation layer. Sometimes it's a corrupted WOW64 install from a botched Windows update or a third-party tool that hooked into ntdll.

The Fix Steps (Do These First)

1. Kill all debuggers. Close Visual Studio, WinDbg, IDA Pro, x64dbg — everything. Check Task Manager for lingering processes like devenv.exe, windbg.exe, or dbgeng.dll hosts. If you see csrss.exe or conhost.exe spawning weird child processes, reboot clean.
2. Run System File Checker. Open an admin command prompt and run:

   sfc /scannow

   Let it finish. If it finds corrupt files, reboot and run it again. I've seen this fix the issue on its own about 60% of the time.
3. Run DISM. If SFC found nothing or the error persists, run:

   DISM /Online /Cleanup-Image /RestoreHealth

   This rebuilds the component store. It takes 10-15 minutes. Don't interrupt it.
4. Reset WOW64. Still broken? Open Regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW. Delete the entire WOW key. Yes, delete it. Windows rebuilds it on next boot. Then reboot. This nukes any stale emulation state.
5. Test with a clean 32-bit app. Open Notepad (it's 64-bit on modern systems, so force 32-bit by running %systemroot%\SysWOW64\notepad.exe). If it doesn't trigger the error, your app or its installer is the problem — reinstall it.

If Those Don't Work

Sometimes the debugger conflict is baked into a shell extension or a driver. Here's what I'd try next:

• Check for anti-cheat or DRM software. Programs like EasyAntiCheat, BattlEye, or SafeDisk hook into the WOW64 layer. If you're trying to run a game or debug tool that conflicts, disable the anti-cheat service temporarily.
• Disable third-party shell extensions. Use autoruns64.exe from Sysinternals to disable non-Microsoft DLLs injected into explorer.exe. Focus on anything from your antivirus or GPU driver control panels.
• Repair Visual C++ Redistributables. Uninstall all versions in Control Panel, then reinstall from Microsoft's latest all-in-one package. Corrupted VC++ runtimes can confuse WOW64.
• Create a new user profile. If the error only happens under your account, the user profile's registry hive might be corrupt. Make a new local admin account and test there.

How to Prevent It Coming Back

Don't leave debuggers running when you're not actively debugging. Close Visual Studio completely — don't just minimize it. If you're a developer and this keeps happening, add a step in your build script to clear the trap flag manually via a small helper tool that calls SetThreadContext with CONTEXT_DEBUG_REGISTERS cleared. Also, avoid running 32-bit debuggers on 64-bit systems if you can help it — use the native 64-bit version of your debugger instead.

One last thing: if you're on Windows 11 22H2 or later and this started after an update, Microsoft acknowledged a bug in the WOW64 emulator that triggers this on certain Intel hybrid architectures. The fix rolled out in KB5025239. Make sure you're fully patched.