Listen to this Post
Microsoft has recently acknowledged a significant issue impacting Remote Desktop (RDP) sessions on Windows Server 2025 systems following the installation of security updates released since February 2025. This problem, which causes RDP sessions to freeze and input devices like the mouse and keyboard to become unresponsive, has led to a series of disruptions for users attempting to connect to their remote systems.
The company also highlighted that this issue affected Windows 11 24H2 systems initially, but a resolution was implemented quickly via an optional update (KB5052093) issued on February 25, 2025. A similar solution for Windows Server 2025 devices is expected in a future update.
Here’s a breakdown of the situation and the steps Microsoft is taking to address it.
Summary
In a release update, Microsoft confirmed that after the installation of the February 2025 Security Update (KB5051987) and subsequent patches, Remote Desktop (RDP) sessions on Windows Server 2025 may freeze within moments of establishing a connection. Once the freeze occurs, users are unable to interact with the session through keyboard or mouse, forcing them to disconnect and reconnect in order to resume use.
While this issue also impacted Windows 11 24H2 devices, it was resolved with the optional KB5052093 update, rolled out on February 25, 2025. However, the solution for Windows Server 2025 systems is still in development and will be included in an upcoming update.
Additionally, Microsoft has been using the Known Issue Rollback (KIR) tool to address similar problems involving RDP disconnections on Windows 11 24H2. The issue, which emerged after updates since January 2025, causes delays in establishing UDP connections between Windows 11 24H2 PCs and Remote Desktop Services (RDS) hosts running on Windows Server 2016. While Windows Server 2025 systems are not directly affected as RDS hosts, disconnections could still occur when using Windows Server 2025 as an RDP client connecting to older servers. A permanent solution for these disconnections is expected in the March 2025 cumulative updates.
Alongside these fixes, Microsoft also resolved issues where certain USB printers began printing random characters after updates from January 2025 onwards. They are continuing their investigation into other known issues, including one affecting Windows 11 24H2 systems when restoring data from SMB network shares or Backup & Replication servers.
What Undercode Says:
The ongoing issues with Remote Desktop on both Windows Server 2025 and Windows 11 24H2 systems, though not immediately catastrophic, highlight important flaws in the update deployment process. Microsoft’s approach of releasing partial fixes through Known Issue Rollback (KIR) suggests a proactive, though piecemeal, method of addressing the impact on users while preparing comprehensive patches for future updates.
These problems have raised a broader question about the timing and coordination of critical security updates. Security patches, particularly those rolled out in response to vulnerabilities, are crucial for maintaining system integrity. However, when such patches inadvertently disrupt core functionalities like RDP, they can leave users and IT departments in a difficult position—balancing between the need for security and the functionality of essential services.
Moreover, the initial patch addressing the issue on Windows 11 24H2 systems highlights Microsoft’s ability to quickly roll out fixes when the problem is widespread, but the delay in addressing the same issue for Windows Server 2025 demonstrates a challenge in patching enterprise-level systems that may have more complex configurations and requirements.
The use of KIR for reversing non-security updates that lead to RDP disconnections shows that Microsoft is committed to mitigating user disruption while waiting for more complete solutions. It’s clear that they understand the inconvenience caused by these disruptions, but it also signals a need for more robust testing before updates are pushed out to ensure that essential features, like Remote Desktop, continue to function smoothly.
Microsoft’s decision to bundle fixes for multiple related issues (including USB printer bugs and data restoration failures) into broader update cycles also speaks to their strategy of addressing problems holistically. While it can be frustrating for users to wait for a permanent fix, the company’s strategy of bundled updates likely helps in managing resources effectively.
One significant takeaway from this incident is the ongoing importance of user communication. In today’s tech environment, transparency with customers is vital, especially when dealing with enterprise solutions like Windows Server 2025. Microsoft’s release health dashboard updates provide a critical avenue for keeping users informed, but ongoing clarity regarding timelines and fixes would likely boost user confidence during these challenging periods.
Lastly, the acknowledgment of issues such as those seen with SMB network shares, and the broader effort to resolve them, reflects Microsoft’s commitment to not only patching security vulnerabilities but also ensuring that business-critical functions are not disrupted in the process.
Fact Checker Results:
- The freeze issue for Remote Desktop sessions, acknowledged by Microsoft, affects both Windows Server 2025 and Windows 11 24H2 systems after the February 2025 updates.
- A fix for Windows 11 24H2 was implemented shortly after the issue was discovered, while the solution for Windows Server 2025 is still in progress.
- Microsoft’s Known Issue Rollback (KIR) tool has been used to reverse problematic non-security updates affecting RDP connections on Windows 11 24H2 systems.
References:
Reported By: https://www.bleepingcomputer.com/news/microsoft/recent-windows-server-2025-updates-cause-remote-desktop-freezes/
Extra Source Hub:
https://www.pinterest.com
Wikipedia
Undercode AI
Image Source:
Pexels
Undercode AI DI v2
