| Code | Name | Meaning |
|------|------|---------|
| 0x3 | ERROR_PATH_NOT_FOUND | The system cannot find the path specified. Often indicates profile path issues (roaming profiles, home drives, or user profile disk). |
| 0x11 | ERROR_BAD_NET_NAME | The network name cannot be found. Points to a missing or inaccessible network share/resource. |
Can you connect to port 3389?
(Test-NetConnection remotePC -Port 3389)
| Step | Action |
|------|--------|
| 1 | Verify the computer name/IP. Double-check for typos. Try pinging the remote host: ping <hostname> or ping <IP address>. |
| 2 | Use the IP address directly in the RDP client instead of the hostname. If that works, the issue is DNS. |
| 3 | Check network connectivity. Ensure both devices are on the same VPN or network segment. Disable the local firewall temporarily for testing. |
| 4 | Verify the remote PC is on. Wake-on-LAN may be needed if it’s sleeping. |
| 5 | Flush DNS cache on your local machine: ipconfig /flushdns (Windows). |
Start with ping and Test-NetConnection. These two commands alone will tell you whether you’re dealing with 0x3 or 0x11. From there, the fix is usually a simple toggle of a firewall rule or network profile.
⚠️ Security note: Never open port 3389 directly to the internet unless you have additional protection like RDP Gateway or a VPN. Brute-force attacks on raw RDP are extremely common.
In the context of the Remote Desktop Protocol (RDP), the error code 0x3 with extended error code 0x11 typically indicates a session termination shortly after authentication. This error is frequently associated with Windows Server 2022 and is often tied to driver conflicts or network transport issues. Summary of Causes
Driver & Display Conflicts: The error often stems from the Microsoft Remote Display Adapter failing to initialize or conflicting with physical GPU drivers. rdp 0x3 0x11
UDP Transport Timeouts: A known protocol bug can cause UDP heartbeats to fail through firewalls or NAT, leading to a dropped connection, often on a predictable timer (e.g., every 30 minutes).
Windows Updates: Specific updates, such as KB5055528, have been identified as primary triggers for this error in some environments.
File System Permissions: Removing "Read" access for the Users group on the system drive (C:\) can unexpectedly break RDP sessions with this code. Recommended Solutions
Force TCP Transport (Disable UDP)Disabling UDP bypasses transport bugs and aggressive firewall timeouts. On the client machine, open the Registry Editor.
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
Create a DWORD (32-bit) named fClientDisableUDP and set its value to 1. | Code | Name | Meaning | |------|------|---------|
Reset Display DriversConflicts with the virtual display driver are a primary culprit. Open Device Manager on the remote server. Go to View > Show hidden devices.
Under Display adapters, right-click Microsoft Remote Display Adapter and select Uninstall.
Restart the RDP session; the driver will reinstall automatically.
Rollback Recent UpdatesIf the error began after a Windows Update, consider rolling back KB5055528 via Settings > Update & Security > View Update History > Uninstall Updates.
Verify Drive PermissionsEnsure the local "Users" group has read access to the root of the system drive (C:\). Right-click C:\, go to Properties > Security. Verify that Users have at least Read & execute permissions.
Configure Keep-Alive IntervalsTo prevent network hardware from dropping the connection, enable keep-alives in the registry of the session host server: Can you connect to port 3389
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters Set KeepAliveEnable to 1. Set KeepAliveInterval to 10000.
In RDS or VDI deployments (e.g., Azure Virtual Desktop), if the User Profile Disk (UPD) path points to a missing network share, the session fails with ERROR_PATH_NOT_FOUND (0x3).
Note: This is a temporary fix for testing or lab environments. You should install proper RDS CALs for production.
If the 120-day grace period is corrupt or reporting false errors, you can reset the Grace Period timer.
If the internal database is corrupted, the server cannot find the licensing group.