Fix ERROR_CTX_CDM_DISCONNECT (0X00001B9B) on RDP

Quick answer

Check Group Policy at Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection. Set "Do not allow drive redirection" to Disabled or Not Configured, then run gpupdate /force and reconnect.

Why this happens

ERROR_CTX_CDM_DISCONNECT (0X00001B9B) means the Client Drive Mapping (CDM) service — which lets you see your local drives inside a remote desktop session — has been cut off. The real trigger is almost always a GPO or registry setting that blocks drive redirection on the remote machine. I've seen this on Windows Server 2016 and 2019 deployments where admins locked down drive mapping for security, but forgot to allow it for users who actually need file transfers. Another common scenario: someone manually changed the fDisableCdm registry value under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services to 1, thinking they were disabling CDM globally. That kills it for everyone, including admins.

The reason you get a specific disconnect error instead of just losing drive access is that the RDP stack tracks CDM state as part of session initialization. If the service detects a policy conflict at connection time — like the client asking for drives but the server refusing — it terminates the mapping cleanly. That 0X00001B9B code is the server saying, "I can't do what you're asking, so I'm not starting this part of the session."

Fix steps

1. Check Group Policy
   On the remote machine, open gpedit.msc and drill to:
   

   Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection

   
   Look for "Do not allow drive redirection". If it's Enabled, set it to Disabled or Not Configured.
2. Apply the change
   Open Command Prompt as admin and run:
   

   gpupdate /force

   
   A reboot isn't strictly required, but I'd restart the Remote Desktop Services service (net stop TermService && net start TermService) to be safe.
3. Check registry directly
   If GPEdit isn't available (e.g., Windows 10 Home), open Registry Editor and navigate to:
   

   HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

   
   Find fDisableCdm. A DWORD value of 1 blocks drive mapping. Delete it or set it to 0. Also check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp for a fDisableCdm — some older configurations hide it there.
4. Verify RDP client settings
   On the client side, open Remote Desktop Connection > Show Options > Local Resources tab > More... under Drives. Make sure the drives you want are checked. If none are checked, the server won't even try to map them, but that usually gives a different error. Still, it's worth a look.
5. Test with a fresh RDP file
   Sometimes corrupted RDP settings on the client cause this. Delete the saved connection from the RDP client dropdown, or create a new .rdp file from scratch using the Save As option.

Alternative fixes if the main one fails

• Check for third-party RDP wrappers: Tools like RDP Wrapper Library or Myrtille can override Windows policies. If you're running one, disable it temporarily and test with native RDP.
• Firewall or VPN blocking CDM ports: Drive mapping uses RDP dynamic virtual channels (port 3389, but channel 0x1B9B is a sub-channel). If a VPN or firewall is stripping certain packets, the CDM handshake fails. Try connecting from the same subnet to bypass network inspection.
• Corrupted user profile: Rare, but if the remote user profile is damaged, the CDM service can't hook in. Create a new local user on the remote machine and test with that account. If it works, migrate the data and delete the old profile via System Properties > Advanced > User Profiles.
• Missing registry key entirely: If neither fDisableCdm nor the GPO exists, the default Windows behavior should allow drive mapping. But I've seen cases where a security baseline script deleted the entire Terminal Services key. Recreate it manually — create HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services and set fDisableCdm to 0.

Prevention tip

Don't rely on GPO or registry edits alone to manage drive mapping. If you're enforcing a security policy that blocks drive redirection, document it explicitly and communicate with users before they hit this error. I recommend deploying a baseline script that logs the fDisableCdm value on startup, so you can audit who changed it. You can also use PowerShell to enforce the setting:

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name 'fDisableCdm' -Value 0 -Type DWord -Force