Recent Windows updates cause Remote Desktop issues

Microsoft says that some customers might experience Remote Desktop and RDS connection issues after installing recent Windows updates released since January 2025.
“After installing the January 2025 Windows preview update (KB5050094) and later updates, users might experience unexpected disconnections with Remote Desktop Protocol (RDP) sessions, including Remote Desktop Services (RDS),” the company said in a new entry on the Windows release health dashboard.
“We’ve observed a significant increase in reports of this issue following the release of the March 2025 Windows security update (KB5053598).”
Affected users may experience unexpected RDP disconnections after 65 seconds when establishing UDP connections from Windows 11 24H2 PCs to RDS hosts on systems running Windows Server 2016 earlier.
While Windows Server 2025 systems are not directly affected as RDS hosts, users may still experience disconnects when acting as RDP clients connecting to older servers.
Fixed via Known Issue Rollback
Microsoft has resolved these Remote Desktop issues via Known Issue Rollback (KIR), a Windows feature designed to reverse buggy non-security updates delivered via Windows Update.
To resolve the known issue on impacted Windows enterprise-managed devices, admins must install and set up the Windows 11 24H2 and Windows Server 2025 KB5053598 250314_20401 Known Issue Rollback group policy.
After installation, the Group Policy can be found under Computer Configuration > Administrative Templates.
To deploy the Known Issue Rollback on affected endpoints, you must go to the Local Computer Policy or the Domain policy on the domain controller using the Group Policy Editor to choose the Windows version that needs to be targeted. Next, restart impacted devices to apply the group policy setting.
IT admins can find additional guidance on deploying and configuring KIR Group Policies on the Microsoft support website.
Redmond says a permanent fix will roll out automatically with a future Windows update, and organizations will no longer need to install and configure the Group Policy to address this known issue once the update is released.
Source link