After a Windows 11 update, Remote Desktop connections suddenly stop working — the machine is unreachable or throws a "Can't connect to the remote PC" error. This is one of the most common side effects of major Windows updates and can be resolved without reinstalling the system.

Why this happens

Cumulative patches and Feature Updates can modify registry keys, reset Windows Defender Firewall rules, or stop Remote Desktop services. The root cause is almost always one of three things: RDP is disabled in system settings, port 3389 is blocked by the firewall, or the TermService service is not set to start automatically.

How to fix it yourself

Step 1. Enable Remote Desktop in Settings

Open: Settings → System → Remote Desktop. Make sure the Remote Desktop toggle is turned on. If it's already on but RDP isn't working — turn it off and back on to restart dependent services.

Step 2. Check Firewall rules

Open: Settings → Privacy & Security → Windows Security → Firewall & network protection → Advanced settings. In the inbound rules list, find "Remote Desktop - User Mode (TCP-In)" and "Remote Desktop - User Mode (UDP-In)". Both rules should be enabled (green). If not — right-click → Enable Rule.

Quick fix via PowerShell (run as Administrator):

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Step 3. Restart RDP services

Search for services.msc and open Services. Find "Remote Desktop Services" (TermService) and "Remote Desktop Services UserMode Port Redirector". Make sure both are running with Automatic startup. To restart via PowerShell:

Restart-Service -Name TermService -Force

After running the command, try connecting again.

Step 4. Check the registry

Updates sometimes reset a critical registry value. Open regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Find the fDenyTSConnections value. It should be 0 (RDP allowed). If it's set to 1 — double-click and change it to 0. Via PowerShell:

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0

⚠️ Edit the registry carefully — mistakes can cause system instability.

Step 5. Verify port 3389

Confirm that port 3389 is listening:

netstat -ano | findstr :3389

No output means the RDP service isn't running or the port has changed. If a line appears but connections still fail — check your external firewall or router (NAT / port forwarding).

If none of the above worked

  • Disable Network Level Authentication: Settings → System → Remote Desktop → Advanced settings → turn off "Require computers to use NLA"

  • Check whether the computer name changed after the update: System → About → Device name

  • Uninstall the latest update: Settings → Windows Update → Update history → Uninstall updates

  • Check Group Policy: gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections → "Allow users to connect remotely" — must be Not Configured or Enabled

Need professional help?

If none of the steps resolved the issue, the cause may be deeper: antivirus conflict, corrupted system files, or a corporate policy lock. English-speaking technician available. IT-Master arrives in Odesa within 1 hour. Free diagnostics with any service order.

24/7 Technical Support