EuroVDC operations note: after the 8 September 2026 Patch Tuesday security updates, Remote Desktop Services (RDS) failures appeared on Windows Server 2019, 2022 and 2025. We reproduced the issue on our Windows Server 2022 hosts, restored RDP with DISM, and documented the steps below for the same scenario.
Microsoft added the known issue “Remote Desktop Services might stop responding after September 2026 security update” to KB5122882 (Windows Server 2022) (and matching September packages) on 12 September 2026. Track status on the Windows release health dashboard.
What happens?
Right after installation, RDS often looks healthy. The failure typically shows up after a few hours of use—especially after users log off. New RDP attempts can hang on “Connecting…”; existing sessions may not disconnect cleanly. In some environments a soft reboot is not enough and a hard reset is required.
Microsoft’s known-issue text also lists RDP dropping after several minutes, sign-in problems, hangs on “Please wait for the Remote Desktop Configuration”, and unresponsive MMC, RDS Licensing Diagnoser, File Explorer or Windows Update UI.
Affected updates
- Windows Server 2019 — KB5122876 (Windows Server 2019)
- Windows Server 2022 — KB5122882 (Windows Server 2022) (OS Build
20348.5622) - Windows Server 2025 — KB5122871 (Windows Server 2025) (OS Build
26100.33438)
Seeing the same pattern across three supported Server releases suggests this is not limited to one servicing branch. Independent reports also appear on BleepingComputer and, for enterprise VDA estates, Citrix CTX697101.
Symptoms we saw at EuroVDC
- For the first hours after the update, RDP logon/logoff still works.
- After users start logging off, new RDP connections can no longer be established.
- A reboot helps only temporarily; it is not a root fix.
- Some reports show TermService stuck in
StopPending; Event Viewer may log TerminalServices-RemoteConnectionManager / Winlogon delays.
Community debugging notes describe a deadlock between RDP and Local Session Manager (LSM), hanging in RDPSERVERBASE!WDLIB_Close. Microsoft has not confirmed that root cause; we treat it as operational context only, not an official diagnosis.
Diagnostics checklist
- Confirm the installed KB:
wmic qfe get HotFixID,InstalledOnor Settings → Windows Update history. - Test logon → use → logoff → new RDP attempt (a single post-reboot login is not enough).
- Verify console / iLO / iDRAC access before you lose RDP.
- Keep TermService, RemoteConnectionManager and Winlogon events for Microsoft Support or a later patch.
The fix we applied on Windows Server 2022
On Windows Server 2022 / KB5122882, EuroVDC restored RDP by removing the September rollup package with DISM. A KB number alone is not enough; you need the full packagename. Names differ on 2019/2025—confirm with dism /online /get-packages on your host.
How to remove the update on Windows Server 2022
- Open the Start menu and type cmd.
- Right-click Command Prompt and choose Run as administrator.
In the black window, paste the following command exactly and press Enter:
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.5622.1.23- Wait until the progress bar goes from
0%to100%. - When asked to restart, type Y and press Enter. (On Turkish UI type E.)
- After the server is back, reconnect with RDP. Then log off and reconnect once more to confirm the failure does not return.
These steps are for Windows Server 2022 / KB5122882. After restart the build typically returns to 20348.5499 and RDP works again.
Security warning: Removing the package also removes September 2026 security fixes. Risk is high on internet-facing hosts or when RDP is the only management path. Do not proceed without console / iLO / iDRAC / out-of-band access. Balance availability against your security policy.
Alternative: Known Issue Rollback (KIR)
Microsoft published Known Issue Rollback (KIR) Group Policy packages for the affected OS lines. KIR aims to roll back the bad behaviour without fully uninstalling the security update. Deployment model: Microsoft Learn — Known Issue Rollback. A practical VDA/RDS-farm walkthrough is in Citrix CTX697101 (WS2022 policy example: 260911_18471).
EuroVDC note: the operational path we validated is DISM remove-package. If you prefer KIR, test first—template install plus reboot is required.
FAQ
Is a restart enough?
No. A reboot only helps temporarily; the failure can return after sessions are closed.
Does this command also apply to 2019 or 2025?
No. The packagename above is only for WS2022 / KB5122882. On 2019 and 2025, pick the correct RollupFix name from dism /online /get-packages.
What does Microsoft say officially?
KB5122882 (Windows Server 2022) lists the known issue “RDS might stop responding”. A permanent fix is expected in a future Windows update; for an immediate workaround Microsoft points IT admins to Support for Business. Follow Windows release health.
How do I remove the update on Windows Server 2022?
- Type cmd in the Start menu.
- Right-click Command Prompt → Run as administrator.
- Paste the DISM command above and press Enter.
- Wait for
0%→100%. - Confirm restart with Y (or E on Turkish UI).
- After reboot, test RDP—including a logoff/reconnect cycle.
References
- KB5122882 (Windows Server 2022) — Microsoft known issue (12 September 2026 changelog)
- KB5122876 (Windows Server 2019) / KB5122871 (Windows Server 2025) — related September LCUs
- Windows release health — Windows release health
- BleepingComputer — field reports and Microsoft “aware / investigating” statement
- Citrix CTX697101 — KIR packages and VDA/RDS farm notes
- Microsoft Learn — Known Issue Rollback — deploying KIR with Group Policy
