Microsoft Acknowledges Windows 11 24H2 Issues with Remote Desktop and Releases Fix

Microsoft has officially acknowledged that the rollout of Windows 11 version 24H2 is plagued by persistent issues with the Remote Desktop Platform (RDP).To mitigate this, the tech giant is implementing an emergency server-side update aimed at resolving these connectivity challenges. However, users should anticipate a waiting period of about 24 to 48 hours before their remote sessions return to normal functionality.

Back in February 2025, Windows Latest highlighted ongoing issues with RDP in Windows 11 version 24H2, despite Microsoft’s silence on the matter at that time. Personal testing revealed that after applying the January optional updates, the RDP issues not only continued but became more prevalent. The challenges with RDP were apparent from the initial release, but the January update exacerbated the situation.

On February 25, Microsoft released an update confirming that it was investigating user reports regarding RDP failures. Although Microsoft claimed to have rectified these issues with the February optional patch marked as KB5052093, users clearly reported that problems persisted even after the March update.

In fact, community feedback indicated that the number of users experiencing Remote Desktop connectivity issues spiked following the March 2025 update. I documented these findings in an article titled “Windows 11 KB5053598 issues, install fails, RDP disconnects, ” solidifying our report’s accuracy.

Microsoft later recognized in an update to its support page that the March update worsened the RDP issues. The statement read, “We’ve observed a significant increase in reports of this issue following the release of the March 2025 Windows security update.”

Understanding Remote Desktop Issues on Windows 11 24H2

Windows 11 24H2 Remote Desktop Platform RDP issues

Observations made by Windows Latest indicate that these RDP issues typically manifest when a session is disrupted—such as during disconnections due to network issues or when the RDP client is closed. In such cases, while users can establish a connection upon reconnection, they often encounter a frozen login screen presented as spinning dots during the session initiation.

Some users have reported that when they access the server via SSH, the remote session remains active with processes functioning normally in the background. One long-time RDP user noted, “I have been using RDP to connect to my various Win 11 Pro VMs for years. Since 24H2, it frequently hangs after connecting. To the point of connectivity and authentication, the animated circle is supposed to signify the setup of the session environment. Sometimes it starts, but it never reaches completion.”

For those facing challenges with Remote Desktop on Windows 11 24H2, sessions may unexpectedly disconnect after approximately 65 seconds of a successful initial connection. Fortunately, Microsoft has now introduced a rollback fix, utilizing a Known Issue Rollback (KIR) approach. This fix is being deployed gradually, and users may need to wait up to 48 hours for it to fully take effect. A quick device reboot can potentially expedite the implementation of this update.

Frequently Asked Questions

1. What specific RDP issues have been reported with Windows 11 version 24H2?

The RDP issues mainly include automatic disconnections during remote sessions, freezing login screens, and challenges with reconnecting after a disruption in the session. Users have reported both client disconnections and freezes that prevent the establishment of a stable remote desktop environment.

2. How long will it take for the emergency patch to resolve the RDP issues?

The emergency server-side update is being rolled out in stages, so users may experience a temporary wait of 24 to 48 hours before their Remote Desktop sessions function properly again. Restarting your device can help speed up the update process.

3. What can I do if I continue to experience RDP issues after the update?

If you still encounter RDP connection problems post-update, consider checking for additional updates to Windows. Also, review support documentation from Microsoft or connect with their support team for further assistance. Community forums may provide additional troubleshooting tips from users with similar issues.

Source & Images