September 2026 Windows Server updates are breaking Remote Desktop Services on 2019, 2022, and 2025. Users can't connect, and some servers need a hard reset. Here's what admins can do.
If you manage Windows Servers, you've probably had a rough week. The September 2026 security updates are causing Remote Desktop Services (RDS) to fail on Windows Server 2019, 2022, and 2025. Users can't connect, and in some cases, a hard reset is the only way to bring things back.
### What's Actually Happening
Microsoft's latest patch was supposed to harden RDP security. Instead, it broke the handshake process. When a client tries to connect, the server hangs or drops the session. Event logs show errors like "The remote procedure call failed" or "An internal error occurred." It's not every server, but enough that forums are lighting up.
> "We patched 40 servers over the weekend. By Monday, 12 were unreachable via RDP. We had to drive to the data center." — a sysadmin on Spiceworks
That's the reality for a lot of teams right now.
### Which Servers Are Affected?
- Windows Server 2019 (all builds)
- Windows Server 2022 (after installing KB5031234 or later)
- Windows Server 2025 (initial release and post-update)
If you're running any of these in production, assume you're at risk until you test.
### The Quick Fix (If You Can't Wait)
Microsoft hasn't released an official patch yet, but there are workarounds. The most effective one so far is to uninstall the problematic update. Yes, it's a pain, but it beats a hard reset every few hours.
Here's what admins are doing:
- Boot into Safe Mode or use out-of-band management (iDRAC, iLO).
- Run `wusa /uninstall /kb:5031234` (replace with your KB number).
- Reboot and verify RDP works.
- Block the update from reinstalling via WSUS or Intune.
If you can't uninstall, try disabling the new RDP security layer via Group Policy. It's a temporary band-aid, but it keeps the lights on.
### Why This Keeps Happening
Microsoft's patch testing clearly missed something. But this isn't new. Every few months, an update breaks something critical. The lesson? Never patch production without a test ring. And always have an out-of-band access method.
### What About Antidetect Browsers?
If you're using antidetect browsers for managing multiple remote sessions, you might be affected too. Some antidetect tools rely on RDP for remote team access. If your RDP is down, your team can't reach those browser profiles. That's a productivity killer.
For now, the best defense is a good backup plan. Keep local access ready. Document your rollback steps. And don't assume the next patch will fix it.
### When Will Microsoft Fix This?
No official timeline yet. Microsoft has acknowledged the issue on its support page, but a fix could take days or weeks. In the meantime, admins are on their own.
So, what's your move? Patch and pray, or hold off until the dust settles? Either way, have a plan B. Because when RDP goes down, everything else stops.