Remote Desktop Services may become unresponsive
Some environments experienced failed RDP connections or unresponsive management tools after the September 2026 security update.
Does this match your environment?
- Windows scope
- 24H2 / 25H2
- Architecture
- Unknown — not universal
- App / driver
- Remote Desktop Services
- Conditions
- Windows devices with Remote Desktop enabled. Exact hardware and architecture are unspecified by Microsoft.
A matching version is only a starting point. This page does not diagnose an individual device.
Evidence & current resolution
Microsoft lists this scope as resolved on 2026-09-14. Resolving update: KB5129195.
- Evidence ID
- official-rds-connections
- Source groups
- 1 · official publication
- Evidence basis
- Manually reviewed public source; no independent device test
Suggest a correction
Recorded timeline
Originating update released
KB5124008Official resolution recorded
KB5129195
Snapshot reviewed
Added to this curated collection. Earlier acknowledgement time was not independently captured.
Could this be what you are seeing?
Checked 2026-10-25The official symptom list for this issue, so you can compare it with what your Remote Desktop environment reports before reading further.
In affected environments, Remote Desktop Services (RDS) might become unstable, causing RDP connection and sign-in failures.
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".
Servers might become unresponsive during Remote Desktop configuration.
Related tools — 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.
The captured official texts tie the issue to installing the September 2026 Windows security update; the two official originating-update wordings are listed below.
This list mirrors the official symptoms only. It cannot diagnose an individual device, and an absent symptom does not rule the issue out.
Evidence: tracked:lib/catalog.ts#issues.rds-connections · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#src-ms-release-health · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#kb5124008 · tracked:docs/qa/evidence/review-2026-10-25.md#rds-connections
Which environments the official scope covers
Checked 2026-10-25What the captured official sources state about who is affected. The two "introduced by" entries differ because the official sources themselves differ — see the note.
- Windows versions
- Windows 11 24H2 and 25H2
- Device condition
- Windows devices with Remote Desktop enabled
- Introduced by — KB5129195 article wording
- The KB5129195 fix article says it addresses an issue affecting RDS "after installing the September 2026 Windows security update (KB5122880)".
- Introduced by — release-health table wording
- The Windows 11 24H2 and 25H2 release-health tables record the originating update as KB5124008 (2026-09-08).
- Official exclusion
- Microsoft notes this issue does not affect Windows 365 or Azure Virtual Desktop.
- Official platform list (wider than this page)
- This page curates Windows 11 24H2/25H2 client devices. Microsoft's entry lists a wider affected set — Windows 11 23H2 and 26H1, Windows 10 22H2/21H2 and LTSC 2019/2016, and Windows Server 2012 through 2025; see the linked source for the full official list.
The two official wordings name different KB numbers for the September 2026 security update, and no captured official source reconciles the difference. The same KB5129195 article also carries a build-history table that lists KB5122880 as the Windows 11 23H2 security update of September 8, 2026 (OS Build 22631.7582); this page records that observation without drawing a conclusion from it. Both originating-update wordings are presented side by side, and this page does not choose between them.
Evidence: tracked:lib/catalog.ts#issues.rds-connections · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#src-ms-release-health · tracked:docs/qa/evidence/review-2026-10-25.md#rds-connections · tracked:docs/qa/evidence/candidates-20261024172211.json
Official status and fix
Checked 2026-10-25The resolution path Microsoft published for this issue, and how this record was revised.
- Status
- Resolved. Microsoft recorded resolution on 2026-09-14.
- Official fix
- KB5129195 (out-of-band update released 2026-09-14), and updates released after that date.
- Official workaround
- UNAVAILABLE
- If you deployed a temporary mitigation through Group Policy
- Microsoft states such IT administrators "do not need to take any action before installing this OOB update".
- Nature of the OOB update
- Cumulative — it "includes all improvements and security protections contained in previous Windows updates"; Microsoft recommends installing the latest update available for your devices as a best practice.
- How this record was revised
- A snapshot of this site from 2026-09-15 still carried the issue as acknowledged; the 2026-10-25 re-check of the official tables recorded resolution (2026-09-14, KB5129195) and this page was revised to match. Official statuses move over time, and the revision is shown rather than hidden.
Microsoft's resolution notes that IT administrators who deployed a temporary mitigation through Group Policy need not remove it before installing the out-of-band update, but the captured sources publish no step-by-step mitigation procedure, so none is offered here. When acting, tie the KB number to your device's Windows version and its official evidence: for Windows 11 24H2/25H2 the release-health tables name KB5124008 as the originating update and KB5129195 as the fix.
Evidence: tracked:lib/catalog.ts#issues.rds-connections · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#src-ms-release-health · tracked:docs/qa/evidence/review-2026-10-25.md#rds-connections · tracked:docs/qa/evidence/candidates-20261024172211.json
What is not yet known
Checked 2026-10-25Questions the captured official sources do not answer. Each stays open until an official source addresses it.
Which KB number introduced the issue for Windows 11 24H2/25H2 — KB5122880 as the KB5129195 article words it, or KB5124008 as the release-health tables record — is not reconciled by any official source captured here.
The official scope is devices with Remote Desktop enabled; which Remote Desktop configurations or roles are affected is not further broken down by the captured sources.
Evidence: tracked:lib/catalog.ts#issues.rds-connections · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#src-ms-release-health · tracked:docs/qa/evidence/review-2026-10-25.md#rds-connections
What to do next
Checked 2026-10-25The actions this evidence supports. Nothing here goes beyond the official fix.
Install KB5129195 (out-of-band, released 2026-09-14) or any update released after that date; Microsoft lists the issue as resolved there.
Match the KB number to the device's Windows version and the official evidence for it: the release-health tables for 24H2/25H2 name KB5124008 as the September 2026 security update, while the KB5129195 article's text names KB5122880, which that article's build table lists for Windows 11 23H2 (OS Build 22631.7582). This page does not adjudicate between the two.
This page offers no steps beyond the official fix, because the captured official sources publish no workaround for this issue. Follow official guidance for your environment.
Evidence: tracked:lib/catalog.ts#issues.rds-connections · tracked:docs/qa/evidence/ingest-state-2026-10-24.json#src-ms-release-health · tracked:docs/qa/evidence/review-2026-10-25.md#rds-connections