Listen to this Post
In January 2025, Microsoft released a series of updates that have unintentionally caused issues for users relying on Remote Desktop Protocol (RDP) and Remote Desktop Services (RDS). These connection problems were especially noticeable after the March 2025 security update. Affected customers found themselves facing unexpected disconnections, often after just 65 seconds of connecting. Microsoft has acknowledged the problem and is addressing it through a rollback process. Here’s what you need to know about the issue and how Microsoft is fixing it.
the Issue
Microsoft has identified a growing number of reports from customers experiencing connection issues with Remote Desktop Protocol (RDP) and Remote Desktop Services (RDS) following the installation of updates from January 2025 onward. According to the company, the issue seems to have been exacerbated after the March 2025 Windows security update (KB5053598). The problem primarily affects users who are connecting from Windows 11 24H2 PCs to RDS hosts running on older systems like Windows Server 2016.
The disconnection occurs unexpectedly, typically after about 65 seconds, when establishing a UDP connection. Interestingly, Windows Server 2025 systems, though not directly impacted as RDS hosts, can still encounter disconnections if they are acting as RDP clients trying to connect to older server versions.
To resolve this issue, Microsoft has deployed a Known Issue Rollback (KIR), a feature designed to undo problematic updates that are not related to security fixes. Administrators managing affected devices will need to install the latest update and configure a group policy to mitigate the problem. This group policy must be applied to both Windows 11 24H2 and Windows Server 2025 systems.
Once the Known Issue Rollback (KIR) is installed and configured, the problem should be resolved. However, Microsoft has promised a permanent fix will be rolled out with a future Windows update, which will make the group policy unnecessary for IT admins.
What Undercode Says:
The issue with Remote Desktop disconnections highlights the complexities of managing updates across various Windows platforms, especially for businesses and enterprises that rely heavily on remote access. Although Microsoft has responded quickly by introducing the Known Issue Rollback, the need for IT administrators to manually deploy and configure this solution adds an extra layer of complexity to what should be a simple update process.
This issue underscores the challenges that many organizations face in ensuring compatibility across multiple versions of Windows. With servers running on older versions like Windows Server 2016, even new systems like Windows 11 24H2 can experience significant disruptions.
The use of Known Issue Rollback (KIR) is a practical solution for addressing such problems in the short term. However, it highlights an ongoing issue in software management—when updates break things unexpectedly, it can lead to significant downtime or disruptions. In large organizations, this may require intensive monitoring and quick responses from IT teams to ensure everything remains functional.
Looking ahead, Microsoft’s plan to roll out a permanent fix with a future update should alleviate the burden on IT admins. However, it’s important to note that updates—particularly those not related to security—can create significant challenges for organizations trying to maintain operational stability. The need for proactive patch management and testing is now more critical than ever.
Fact Checker Results:
- Microsoft has acknowledged an uptick in reports of RDP disconnections since the January 2025 updates.
- Known Issue Rollback (KIR) provides a temporary fix, but a permanent solution will come with future updates.
- IT admins must manually configure the KIR to resolve the issue until the permanent fix is available.
References:
Reported By: https://www.bleepingcomputer.com/news/microsoft/microsoft-recent-windows-updates-cause-remote-desktop-issues/
Extra Source Hub:
https://www.linkedin.com
Wikipedia
Undercode AI
Image Source:
Pexels
Undercode AI DI v2
