STATUS_CTX_INVALID_WD (0XC00A002E) Fix Guide

Why This Error Shows Up

The error STATUS_CTX_INVALID_WD (0XC00A002E) means Windows can't load the terminal connection driver. The driver here isn't a hardware thing — it's a software module that handles RDP sessions. When it's missing, corrupt, or its registry entry points to the wrong spot, you get this error.

I've seen this most often on Windows Server 2016 and 2019 after a failed update or a manual registry cleanup gone wrong. It also shows on Windows 10/11 if someone uninstalled Remote Desktop Services improperly.

Cause #1: Corrupt or Missing Registry Key for Ctx_WdWorkstation

This is the number one cause. The registry key that loads the terminal driver got hosed. The fix is straightforward.

Check the Registry Key

Open Regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters

Look for a value named DriverName. It should be set to Ctx_WdWorkstation. If it's missing or set to something else, that's your problem.

Fix It

1. If the DriverName value doesn't exist, create it as a REG_SZ type.
2. Set the data to Ctx_WdWorkstation.
3. Also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\WdWorkstation. If that key is missing entirely, your terminal driver registration is gone.

If the WdWorkstation key is missing, you'll need to re-register the driver. Run this from an elevated command prompt:

regsvr32 /s termdrv.dll

Then reboot. I've fixed 9 out of 10 cases with this single step.

Cause #2: Corrupt System Files (Especially termdrv.dll and terminal.dll)

If the registry looks fine, the actual driver files might be corrupt. The two files you care about are termdrv.dll in C:\Windows\System32 and terminal.dll in the same folder. Windows File Protection usually catches this, but not always — especially after a botched update.

Run System File Checker

Open an admin command prompt and run:

sfc /scannow

Wait for it to finish. If SFC finds corrupt files but can't fix them, run DISM first:

DISM /Online /Cleanup-Image /RestoreHealth

Then run SFC again. This combo fixes most file-level corruption.

Cause #3: Third-Party RDP Wrappers or Custom Drivers

If you're running RDP Wrapper Library (the popular open-source tool that lets multiple RDP sessions on Windows 10), it sometimes overwrites the default driver. The error appears when that wrapper driver goes missing or conflicts with Windows updates.

Check for RDP Wrapper

Look in C:\Program Files\RDP Wrapper or check the Services panel for TermService — if it's still running but fails with this error, the wrapper's driver file rdpwrap.dll might be corrupt or blocked by antivirus.

The fix: uninstall RDP Wrapper completely. Run its uninstall.bat as admin, then reboot. After that, reinstall the latest version from the official GitHub repo. Don't bother with old versions — they break after updates.

Quick-Reference Summary Table

If none of these work, check the Windows Event Log under System for the source TermService. The event ID is usually 56 or 58. That'll tell you exactly which driver it's failing on. Sometimes the driver name in the event log reveals a typo in the registry or a file that's been deleted.