Administrators can restore Remote Desktop functionality by removing the update, but doing so also removes the security patches.
Key Takeaways:
Organizations that applied Microsoft’s September 2026 security updates are encountering a new problem in which Remote Desktop Services (RDS) can become unstable or stop working entirely on affected Windows Server systems. This issue can disrupt user access and force emergency troubleshooting for businesses that rely on remote administration, virtual desktops, and terminal services.
According to the reports, Windows Server machines initially appear healthy after installing the updates, but problems often emerge hours later. Microsoft has warned that existing Remote Desktop sessions may hang, users can become unable to disconnect properly, and new connection attempts frequently fail. Some environments have required hard resets to restore access, which creates operational risks for IT teams managing critical workloads remotely.
Microsoft has now acknowledged the issue and confirmed that it affects various supported platforms, including Windows Server 2012 through Windows Server 2025, along with select Windows client versions. The company says affected systems may experience failed RDP connections, sign-in problems, unresponsive management tools, and servers becoming stuck during Remote Desktop configuration processes.
“In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at “Please wait for the Remote Desktop Configuration”. Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator,” Microsoft explained.
As a workaround, Microsoft recommends uninstalling the September 2026 updates on their Windows Server machines. However, it also removes the security fixes delivered in the latest Patch Tuesday release, which could expose the system to vulnerabilities.
Microsoft is investigating the root cause and has published Known Issue Rollback policies to help enterprise customers mitigate the problem until a permanent fix is available. For virtual machines that become inaccessible, Microsoft says stopping and restarting the affected VM may temporarily restore connectivity.