Terminal Connection Driver Not Found (0x00001B5C) Fix

When This Error Shows Up

You're trying to connect to a remote PC using Remote Desktop (RDP) — maybe a server at a client's office or your home machine — and bam, you get this error. The connection fails before the login screen even loads. I saw this last month at a small accounting firm after they pushed a Windows 10 22H2 update to their workstations. Every single remote desktop connection from the updated machines died. The error text says the terminal connection driver wasn't found in the system path, and the code is 0x00001B5C.

Root Cause

The core of this problem is that Windows can't load the RDP driver — specifically rdpdr.sys or its supporting files — from where it expects to find them. This usually happens because a Windows update replaces or corrupts the driver files, or a registry entry pointing to the driver path gets mangled. On one client's machine, an antivirus tool quarantined the driver after a false positive. On another, a third-party remote desktop tool (like TeamViewer) overwrote the default driver path in the registry. The real fix is making sure the driver is present and the registry points to it correctly.

The Fix

Skip the guesswork. Here's the step-by-step that works 9 out of 10 times.

Step 1: Verify the Driver File Exists

First, check if rdpdr.sys is actually on your system. Open File Explorer and go to:

C:\Windows\System32\drivers\rdpdr.sys

If it's missing, you'll need to restore it. Had a case where the file was there but zero bytes — corrupted from a partial update.

Step 2: Reinstall RDP Drivers

If the file is missing or corrupt, the quickest way to get it back is to reinstall the RDP driver stack. Open an elevated Command Prompt (right-click Start, select Command Prompt (Admin) or Terminal (Admin)). Run:

dism /online /cleanup-image /restorehealth
sfc /scannow

Let both complete. SFC will replace missing or corrupt system files, including rdpdr.sys. Reboot after this.

Step 3: Fix the Registry Path

If the file is there but the error persists, the registry entry is busted. Open Regedit (Win+R, type regedit). Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermDD

In the right pane, look for a value named ImagePath. It should be:

\SystemRoot\System32\drivers\termdd.sys

If it's missing or pointing somewhere else (like to a third-party driver path), right-click, choose Modify, and set it to the correct path above. Also check the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RdpDr

Same thing — ImagePath should be \SystemRoot\System32\drivers\rdpdr.sys. Had a client where TeamViewer changed this to its own driver. Reverting this fixed it instantly.

Step 4: Restart the Remote Desktop Service

After both registry checks, restart the service. Open Services (Win+R, type services.msc), find Remote Desktop Services, right-click, select Restart. If it doesn't start, check the event log (Event Viewer > Windows Logs > System) for more details.

Step 5: Run a Custom Fix Script (Advanced)

If you're dealing with multiple machines, automate it. Save this as a .bat file and run as admin:

@echo off
sc config TermDD start= demand
sc config RdpDr start= system
reg add "HKLM\SYSTEM\CurrentControlSet\Services\TermDD" /v ImagePath /t REG_EXPAND_SZ /d "\SystemRoot\System32\drivers\termdd.sys" /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\RdpDr" /v ImagePath /t REG_EXPAND_SZ /d "\SystemRoot\System32\drivers\rdpdr.sys" /f
net stop TermService
net start TermService
echo Done. Reboot recommended.

I used this at a dental clinic with 12 broken workstations — saved hours of manual work.

What to Check If It Still Fails

If you've done all the above and it still won't work, check these three things:

• Third-party remote tools: Uninstall any remote desktop software like LogMeIn, TeamViewer, or AnyDesk temporarily. They sometimes hook into the RDP driver stack and break things.
• Antivirus quarantine: Check your AV's quarantine list for rdpdr.sys or termdd.sys. Restore them if found.
• Group Policy: If you're on a domain, your IT admin might have pushed a policy that restricts RDP driver loading. Run gpresult /h gp.html and look for any RDP-related policy settings.

Worst case, a system restore to before the update or an in-place upgrade (using Windows Media Creation Tool) will reset the driver stack completely. Never had to go that far myself, but it's the nuclear option.