Check What Is Causing the Problem
Before making changes, identify the exact symptom. Common issues after a Windows 11 update include:
- Connection attempt fails with an error about credentials or authentication.
- Remote Desktop cannot connect to the target PC at all (timeout or “connection refused”).
- The remote session starts but displays a black screen or disconnects shortly after login.
- You are prompted repeatedly for a password that is correct.
Open Event Viewer on both the client and the host machine (look under Windows Logs > System and Applications and Services Logs > Microsoft > Windows > TerminalServices). Error codes and descriptions point directly to the blocked component. Also note whether the problem affects all remote connections or only one specific computer.
Fixes to Try in Order
Work through the following steps from simplest to more involved. After each step, test the connection before moving to the next.
1. Verify Remote Desktop Is Still Enabled
A system update can revert the setting that allows remote connections. On the host PC, go to Settings > System > Remote Desktop. Make sure the toggle for “Remote Desktop” is turned on. Also confirm that “Keep my PC awake for connections when it is plugged in” and “Make my PC discoverable on private networks to enable automatic connection from a remote device” are checked if you use those features.
2. Check Windows Firewall Rules
Updates sometimes reset or disable the built-in firewall rule for Remote Desktop. Open Windows Security > Firewall & network protection > Allow an app through firewall. Scroll down and ensure “Remote Desktop” is checked for both Private and Public networks. If it is missing, click “Allow another app” and add C:\Windows\System32\mstsc.exe. Also confirm that the inbound rule for “Remote Desktop (TCP-In)” is enabled in Windows Defender Firewall with Advanced Security.
3. Update Network Adapter Drivers
An outdated or incompatible network driver can cause connection failures after an update. Open Device Manager, expand Network adapters, right-click your active adapter, and select “Update driver”. Choose “Search automatically for drivers”. Restart the computer after the update. For best results, also download the latest driver directly from your PC or motherboard manufacturer’s support site.
4. Clear Cached RDP Credentials
Stored credentials may be incompatible with new security policies introduced by the update. On the client computer, open Credential Manager (Control Panel > User Accounts > Credential Manager). Under Windows Credentials, look for any entries that contain “Remote Desktop” or “TERMSRV”. Remove them. Try connecting again and re-enter your password manually.
5. Adjust Network Level Authentication (NLA) Settings
Updates can change how NLA is handled. On the host PC, go to Settings > System > Remote Desktop. Uncheck “Require devices to use Network Level Authentication to connect” and try the connection. If that works, the update may have changed certificate or authentication requirements. You can leave NLA disabled if security risk is acceptable, but a better solution is to re-enable it after verifying the correct certificate is in place (see step 8).
6. Temporarily Disable Third-Party Security Software
Antivirus, firewall, or VPN software sometimes blocks RDP traffic after an update. Temporarily disable any non‑Microsoft security software on both the client and host and test the connection. If the problem disappears, adjust the software’s settings to allow Remote Desktop on private networks or add an exception for port 3389 (TCP and UDP).
7. Use Group Policy Editor to Enforce Encryption and Authentication
If the update tightened security policies, the default settings may conflict. On the host PC (Windows 11 Pro, Enterprise, or Education), open Local Group Policy Editor (gpedit.msc). Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security. Set “Require use of specific security layer for remote (RDP) connections” to “Enabled” and choose “RDP” if SSL/TLS is causing issues. For authentication, open “Set client connection encryption level” and set it to “High” (128‑bit). Then run gpupdate /force in an elevated Command Prompt and reboot.
8. Reset the RDP Self‑Signed Certificate
An update may have damaged or replaced the certificate used for Remote Desktop. On the host PC, open an elevated Command Prompt (Run as administrator). Type certlm.msc and press Enter. Navigate to Remote Desktop under Certificates – Local Computer > Personal > Certificates. You should see a certificate with the friendly name “Remote Desktop”. If it is expired or missing, delete the existing one (if any), then restart the Remote Desktop Services service with the following commands:
net stop TermService
net start TermService
Windows will recreate a self‑signed certificate automatically. Alternatively, you can use PowerShell: Remove-Item -Path "Cert:\LocalMachine\Remote Desktop\*" -Force followed by Restart-Service TermService.
9. Uninstall the September Update (Last Resort)
If none of the above helps and the problem started immediately after the update, you can remove it temporarily. Go to Settings > Windows Update > Update history > Uninstall updates. Look for the update dated in September (the KB number will vary by month and build). Select it and click Uninstall. Restart the machine. After testing, you can block the update from being reinstalled using the “Pause updates” feature or by hiding it via the Microsoft Show or Hide Updates troubleshooter tool.
If the Problem Continues
If Remote Desktop still does not work after trying these fixes, the issue may be caused by a network configuration beyond the update – for example, a router blocking port 3389, an incorrect VPN route, or a domain policy that cannot be overridden locally. In that case:
- Test the connection from a different client on the same local network to isolate network-level problems.
- Check whether the host PC’s IP address changed (use a static IP or update the client’s target address).
- Review recent Group Policy changes if the PC is domain‑joined.
- Contact Microsoft Support via the Get Help app or the Windows 11 community forums, providing the Event Viewer error codes you recorded earlier.
If an immediate remote connection is needed while troubleshooting, you can temporarily enable a third‑party remote access tool such as Microsoft Quick Assist (built into Windows 11) or a similar utility, but remember to disable or remove it once you resolve the actual RDP problem.
The steps above address the most common disruptions caused by Windows 11 updates to Remote Desktop functionality. Working through them in order usually restores the connection without needing to roll back the entire update.
- Migliori adattatori USB-C per cuffie cablate: guida 2026 - 12 Ottobre 2026
- Best Galaxy Z Fold 8 Deals: October 2026 Buying Guide - 12 Ottobre 2026
- Motorola Razr Ultra 2026: guida alle nuove funzioni AI - 12 Ottobre 2026