Why Windows 11 Remote Desktop Stops Working
Windows 11 Remote Desktop Protocol (RDP) failures became significantly more common after the April 2026 cumulative update (KB5055628) introduced a regression where RDP connections drop immediately after authentication. Other causes include: Remote Desktop is disabled in settings, the Windows Firewall is blocking port 3389, the network profile is set to Public (which blocks RDP by default), or NLA (Network Level Authentication) conflicts with your client version. Here are 9 fixes.
Fix 1: Enable Remote Desktop in Windows 11 Settings
This is the most common cause — RDP is disabled by default in Windows 11.
1. Press Windows + I → System → Remote Desktop.
2. Toggle Remote Desktop to On.
3. Click Confirm.
4. Note the PC name shown at the top — this is what you'll type in the Remote Desktop client.
Alternatively via Command Prompt (Admin): reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
Fix 2: Set Network Profile to Private
Windows Firewall automatically blocks RDP (port 3389) on Public networks. If your PC is connected to a network classified as Public, Remote Desktop won't work.
1. Press Windows + I → Network & internet → click your connection (Wi-Fi or Ethernet).
2. Under Network profile type, select Private network.
3. Re-test your RDP connection immediately.
Fix 3: Allow RDP Through Windows Firewall
Even on a Private network, a corrupted firewall rule can block RDP.
1. Search for Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall.
2. Click Change settings → scroll to Remote Desktop → check both Private and Public boxes.
3. Click OK.
Alternatively, add the firewall rule via PowerShell (Admin):
Enable-NetFirewallRule -DisplayGroup "Remote Desktop"
Fix 4: Disable Network Level Authentication (NLA)
NLA requires the client to authenticate before a full desktop session is created. If there's a certificate mismatch, expired domain credentials, or a version incompatibility, NLA blocks the connection entirely.
1. Press Windows + R → type sysdm.cpl → Enter.
2. Click the Remote tab.
3. Uncheck Allow connections only from computers running Remote Desktop with Network Level Authentication.
4. Click OK and test.
Fix 5: Fix the KB5055628 April 2026 RDP Regression
Microsoft confirmed a bug in KB5055628 (April 2026) where RDP sessions authenticate successfully but disconnect within seconds. The fix is to install the Out-of-Band patch KB5056579 or later.
1. Press Windows + I → Windows Update → Check for updates.
2. Install all pending updates including optional ones.
3. Reboot and test RDP.
If your organisation delays updates, an alternative workaround is to disable UDP for RDP on the client: open Remote Desktop Connection → Show Options → Experience → uncheck Use UDP (or edit the .rdp file and add enablerdsaadauth:i:0).
Fix 6: Ensure Remote Desktop Services Are Running
Windows Updates sometimes disable RDP-related services.
1. Press Windows + R → type services.msc → Enter.
2. Find Remote Desktop Services — set Startup type to Automatic and click Start.
3. Find Remote Desktop Services UserMode Port Redirector — also set to Automatic and Start.
4. Find Remote Desktop Configuration — set to Automatic and Start.
Fix 7: Disable Windows Hello PIN-Only Sign-In
Windows 11 22H2 and later default to Windows Hello for sign-in. When "For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device" is enabled, RDP with username/password is blocked.
1. Press Windows + I → Accounts → Sign-in options.
2. Scroll to Additional settings.
3. Toggle OFF: For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device.
Fix 8: Check Port 3389 Is Listening
Confirm RDP is actually listening on port 3389 from within Windows.
1. Open PowerShell as Administrator.
2. Run: netstat -ano | findstr :3389
3. You should see a line with 0.0.0.0:3389 in LISTENING state.
4. If not: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v PortNumber /t REG_DWORD /d 3389 /f
5. Then restart Remote Desktop Services: net stop termservice && net start termservice
Fix 9: Check Router and VPN Configuration
If connecting from outside your local network, your router must have port forwarding configured for TCP 3389. If using a VPN: ensure split tunnelling isn't blocking the connection, and that your VPN client isn't classified as a Public network in Windows.
For corporate environments: check Group Policy for Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services and ensure Allow users to connect remotely is Enabled, not set to Not Configured.
Frequently Asked Questions
Why does Remote Desktop say "the remote computer could not be found" on Windows 11?
This means Windows can't resolve the PC name. Either use the IP address instead of the PC name (find it with ipconfig on the target PC), or ensure both machines are on the same network and the same workgroup or domain. DNS resolution must work for name-based RDP connections.
RDP connects but the screen is black — how do I fix it?
A black screen after connecting is usually caused by a display driver conflict or a previous session that didn't terminate cleanly. Fix: on the target PC, right-click the desktop → Display settings → change resolution to something other than current and back. Also try signing out all active sessions via Task Manager → Users tab → right-click → Sign off.
Can I use Remote Desktop on Windows 11 Home?
Windows 11 Home can RECEIVE RDP connections (connect to it) with a third-party enabler, but it cannot HOST them natively. To host Remote Desktop on Windows 11 Home, you need to upgrade to Windows 11 Pro, or use an alternative tool like Chrome Remote Desktop, AnyDesk, or TeamViewer which work on all editions.
Remote Desktop was working yesterday and stopped today — what changed?
Most likely cause: Windows Update ran overnight and either installed KB5055628 (April 2026 RDP regression) or reset firewall rules. Check Windows Update history (Settings → Windows Update → Update history) for updates installed in the last 24 hours and follow Fix 5 above.
How do I allow multiple users to connect via RDP simultaneously on Windows 11?
Windows 11 Pro limits RDP to 1 concurrent session. For multiple simultaneous sessions, you need Windows Server with Remote Desktop Session Host (RDSH) role enabled. On Windows 11 Pro, you can manually edit the termsrv.dll file to bypass this limit (not officially supported and may break after updates). The supported approach is to use Windows Server or a virtual desktop infrastructure (VDI) solution.
Still unable to connect? CloudHouse Technologies' Windows remote support can diagnose and fix RDP configuration issues, firewall rules, Group Policy conflicts, and update regressions in a single session.