How to fix RDP for Windows Server 2025 taking long

For Windows Server 2025, slow or problematic RDP behavior can currently be caused by known issues in recent updates, as well as general Remote Desktop performance or connectivity problems. Use the following steps to diagnose and improve RDP performance.

1. Check for known Windows Server 2025 RDP issues and install fixes

• If the server has the February 11, 2025 security update KB5051987 (OS Build 26100.3194) or later installed, Remote Desktop sessions might freeze shortly after connection, with mouse and keyboard becoming unresponsive and requiring reconnects.
• This specific freeze issue is resolved in KB5055523 (OS Build 26100.3775). Install the latest cumulative update for Windows Server 2025 that includes KB5055523 or newer.
• Keeping the server fully updated is the primary fix for this class of RDP freezes and related delays.

2. Distinguish between “slow to connect” vs “slow after login”

• If the delay is at the “Securing remote connection…” or initial connection stage:
  • This can be caused by certificate checks and high security negotiation.
  • Ensure the server is using a valid certificate from a trusted CA where possible, rather than relying only on self-signed certificates.
  • If using self-signed certificates and clients are waiting on Internet-based revocation/CA checks, consider importing the server’s certificate into the client’s Trusted Root Certification Authorities store to reduce delays, or centrally manage certificates via enterprise PKI.
• If the delay is after login (desktop slow to appear, sessions hanging, or “busy” behavior):
  • Investigate server resource usage and potential leaks as described below.

3. Check for RDP server memory, session, or token leaks

If RDP logons become slower over time, or connections intermittently fail with messages like “Remote Desktop Service is currently busy,” or performance degrades until a reboot:

• Restart the server once and observe whether RDP performance temporarily improves. If it does, this suggests a leak (memory, session, or token) or a misbehaving service.
• As a less disruptive workaround than rebooting, restart the Remote Desktop Services (RDS) service on the server. Note:
  • Restarting RDS disconnects all current RDP users, but their sessions remain and can be reconnected.
• Monitor Task Manager, Resource Monitor, or other tools for:
  • Unusual or steadily increasing memory usage by services or processes.
  • High handle counts or CPU usage associated with third-party software.
• If the problem only occurs when users connect via RDP (and not on console), focus on non-Microsoft software that hooks into RDP sessions, such as:
  • Antivirus/endpoint protection
  • Session recording/monitoring tools
  • Other RDP-related agents
• As a test, gradually uninstall (not just stop) non-Microsoft software that interacts with RDP and monitor whether RDP performance improves.

4. Validate network and RDP path (especially for Azure or remote-hosted VMs)

If the server is an Azure VM or otherwise remote-hosted and RDP is slow or intermittently unavailable:

• Confirm the VM is running and healthy in the hosting portal.
• Check Network Security Group (NSG) or firewall rules to ensure TCP 3389 is allowed and not being throttled or inspected in a way that adds latency.
• If RDP becomes slow or unresponsive after some time but recovers after a VM restart or RDS restart, this again points to resource or service issues on the server (see step 3).

5. Address client-side issues that can appear as “slow RDP”

If RDP to the same server is fast from some clients but slow or failing from others:

• Ensure the Windows client is fully updated.
• Clear cached credentials and re-enter them.
• Confirm the client’s time and date are correct (time skew can cause authentication delays or failures).
• If using the Microsoft Store Remote Desktop client, ensure it is up to date; if using the built-in client, test with the Store version.

6. Monitor for profile or logon-related delays

If the delay occurs specifically at or after “Please wait for the User Profile Service” or similar messages, and logon takes a long time:

• Check that the server has sufficient disk space and resources.
• Test logging in with a new user profile. If the new profile logs in quickly, the original profile may be corrupted and should be repaired or recreated.

7. General recommendations

• Keep Windows Server 2025 updated, especially with KB5055523 or later, to pick up RDP-related fixes.
• Minimize unnecessary software on RDS hosts, particularly anything that injects into user sessions.
• Regularly monitor memory, CPU, and session counts on RDS servers and investigate any steady growth patterns.
• For persistent or complex leaks, collect diagnostics and open a support case with Microsoft, especially if non-Microsoft software has been ruled out.

References:

• Resolved issues in Windows Server 2025
• February 11, 2025—KB5051987 (OS Build 26100.3194)
• April 8, 2025—KB5055523 (OS Build 26100.3775)
• "Remote Desktop Service is currently busy" message during RDP connections
• Remote desktop connection is sometimes stuck on the Securing remote connection screen
• Unable to Access or Connect to VM - Microsoft Q&A
• Azure VM takes over an hour to login - stuck on "Please wait for the User Profile Service" - Microsoft Q&A