← Back to Blog

Remote Desktop Not Working After a Windows Update: Which Update Broke It and Which Fixes It

Published · by Leo Gashi, RS Computers

Remote Desktop Windows Update Windows Server

If Remote Desktop stopped working right after a Windows update in September, October or November 2026, Microsoft has confirmed four update bugs that can cause it, and every one of them is fixed by a later update. Install the newest cumulative update on the machine the table below names (sometimes the server, sometimes your own PC) before you think about uninstalling anything, because rolling back a security update reopens the holes it closed.

Running Windows on a Windows VPS from RS Computers? Every server has a console in the client area that shows its screen without RDP, so you can install the fix even while Remote Desktop refuses to connect.

Quick fix

  1. Find out what is installed: press Win+R, run winver and note the OS build, or run Get-HotFix | Sort-Object -Property InstalledOn in PowerShell.
  2. Match your symptom and Windows version in the update table.
  3. Run Windows Update on the machine in the "Install the fix on" column. The November 10, 2026 cumulative updates contain every fix listed here.
  4. Restart, then connect again. If the server is unreachable over RDP, do all of this from the console.
  5. Still broken? It is probably not an update bug. Work through our Remote Desktop can't connect checklist.

Key facts, all checked on Microsoft's own pages on 19 November 2026:

Which update broke Remote Desktop, and which update fixes it

Only rows Microsoft confirms on its release health pages or KB articles are listed. "Install the fix on" matters: the certificate bug lives on the connecting PC, the others on the machine you connect to.

Windows versionWhat you seeBroken byFixed byInstall the fix on
Windows Server 2025RDS unstable: RDP drops after minutes, sign-in fails, hang at "Please wait for the Remote Desktop Configuration"KB5122871, 8 Sep 2026 (build 26100.33438)KB5129235, 14 Sep 2026, or any later update such as KB5131080The server
Windows Server 2022Same RDS instabilityKB5122882, 8 Sep 2026 (build 20348.5622)KB5129237, 14 Sep 2026, or later (source)The server
Windows Server 2019Same RDS instabilityKB5122876, 8 Sep 2026KB5129238, 14 Sep 2026 (build 17763.9247), or laterThe server
Windows Server 2016Same RDS instabilityKB5123099, September 2026KB5129239, 14 Sep 2026 (build 14393.9514), or laterThe server
Windows 11 24H2 and 25H2Same RDS instability on a PC that accepts Remote DesktopKB5124008, 8 Sep 2026KB5129195, 14 Sep 2026, or laterThat PC
Windows 11 24H2, 25H2, 26H2 (26H1 is affected too: check its release notes)Non-admin users get 0xC000000D, "The token that was passed to the function is invalid"Preview KB5124010, 22 Sep 2026, or later updatesKB5132061, 10 Nov 2026, or laterThe remote PC (the host)
Windows 11 25H2 and 26H2RDP fails on the client because of a certificate mismatchPreview KB5127936, 28 Oct 2026KB5132061, 10 Nov 2026Your own PC (the client)
Windows Server 2016RD shadow connections fail with "Unspecified error"Update of October 14, 2026 (Microsoft's date)KB5131291, 10 Nov 2026 (build 14393.9688)The server

Microsoft says the September bug "does not affect Windows 365 or Azure Virtual Desktop". The same entry lists Windows Server 2012 and 2012 R2 and Windows 10 22H2 and the LTSC editions as affected; check their own release notes for the KB numbers. KB5132061 applies to all editions of Windows 11 25H2 and 26H2, but on 24H2 only to Enterprise and Education.

See which updates are installed

Microsoft's tip for the build number is to press Win+R and type winver (Microsoft Learn). In Settings, Windows Update, Update history lists what was installed and when (Windows Update FAQ). On a server, PowerShell is faster. These two lines are Microsoft's own Get-HotFix examples with our KB number filled in:

# PowerShell on the machine you are checking
Get-HotFix | Sort-Object -Property InstalledOn
Get-HotFix -Id KB5131080

The output has the columns Source, Description, HotFixID, InstalledBy and InstalledOn. Get-HotFix lists only updates supplied by Component Based Servicing, Microsoft notes, so do not treat it as a full inventory. The surer check is the build number. After the November 10, 2026 update, winver should show at least:

Install the fix

For most people this is one step: open Settings, Windows Update, check for updates, install the November cumulative update and restart. Microsoft says the September fix is in "updates released after this date", so you do not need the September out-of-band packages any more unless you hold updates back on purpose.

If you install by hand from the Microsoft Update Catalog, follow the KB page for your version:

Restart, check the build with winver, then test RDP.

Check the Remote Desktop services and event logs

If RDP still fails on the latest build, check whether the server is listening. The checks come from Microsoft's Remote Desktop can't connect article; run them in an administrator window on the server, from the console if RDP is down:

qwinsta

Microsoft's healthy example contains this line:

 rdp-tcp                    65536 Listen

No rdp-tcp line in Listen state means the listener is down. Next, the services Microsoft says must be running, Remote Desktop Services (TermService) and Remote Desktop Services UserMode Port Redirector (UmRdpService), plus Remote Desktop Configuration (SessionEnv), which Microsoft restarts when it renews the RDP certificate. Get-Service takes all three names at once:

Get-Service -Name TermService, UmRdpService, SessionEnv

Each should show Running in the Status column. For certificate trouble on the server, Microsoft's event ID guide searches the System log for events 1057 and 1058, which say the RD Session Host could not create or replace its self-signed certificate. Its command, in Command Prompt:

wevtutil qe system /c:1 /f:text /q:"Event[System[Provider[@Name='Microsoft-Windows-TerminalServices-RemoteConnectionManager'] and EventID=1058 and TimeCreated[timediff(@SystemTime) <= 86400000]]]" | more

Change 1058 to 1057 for the second check. No output means no such event in 24 hours. To see which Remote Desktop logs your build keeps, list them with Get-WinEvent, then read the newest entries of one by its full name:

Get-WinEvent -ListLog *TerminalServices*
Get-WinEvent -LogName 'LOG_NAME_FROM_THE_LIST' -MaxEvents 20

If the hang is at "Securing remote connection", that is the TLS and CredSSP handshake; our guide to that hang covers it. If users are refused with "no available computers in the pool", read our fix for stuck RDS sessions; a licensing message after 120 days is the RDS grace period, not an update bug.

Error 0xC000000D and Administrator protection

Administrator protection is a newer Windows 11 security feature that changes how administrator rights are granted. Microsoft's release health entry says that since preview KB5124010, non-admin users "might be unable to establish Remote Desktop connections" to devices with it enabled. Microsoft says the bug "primarily affects enterprise-managed remote devices" used as Remote Desktop hosts, and notes that Administrator protection is on by default in the Windows 11 24H2, 25H2 and 26H2 security baselines.

The fix is KB5132061 or later on the remote PC. Before that update existed, Microsoft's workaround was to turn Administrator protection off temporarily by resetting the "User Account Control Type Of Admin Approval Mode" policy in Intune or Group Policy. If you did that, install KB5132061 and switch the protection back on.

Certificate mismatch after the October preview

This one sits on the client. Microsoft's KB5132061 notes say RDP connections "might fail on the client due to a certificate mismatch" after the October 2026 non-security preview, KB5127936 (28 October 2026). If one PC fails against every server while colleagues connect fine, update that PC.

RD shadowing fails with "Unspecified error" on Server 2016

Shadowing lets an administrator watch or control another user's session, for example with the /shadow switch of mstsc. On Windows Server 2016 and 2012 R2, Microsoft says shadow connections "might fail with an 'Unspecified error'" after the October 14, 2026 update. KB5131291 fixes it on Server 2016. Server 2016 has its own deadline as well: support ends on 12 January 2027, which our Windows Server 2016 end-of-support guide plans around.

Roll back an update only as a last resort

Microsoft's position is plain: "We don't recommend that you remove any installed updates," and "not all updates can be removed" (Windows Update FAQ). Every bug in the table already has a fix that keeps your security patches, so rolling back is for a new problem with no fix yet. The costs:

With a desktop, go to Settings, Windows Update, Update history and use the uninstall option there. From the command line, the Windows Update Standalone Installer has an /uninstall switch and a /kb switch for the KB number, usually written like this:

wusa /uninstall /kb:5131291

That fails on modern cumulative updates that bundle the servicing stack. Microsoft's KB articles say running wusa.exe with /uninstall "on the combined package will not work", because the servicing stack cannot be removed. Their documented route is DISM: list the packages, find the cumulative update, remove it by name.

DISM /Online /Get-Packages /Format:Table
DISM /Online /Remove-Package /PackageName:PACKAGE_NAME_FROM_THE_LIST

In a Microsoft Q&A answer the cumulative update shows up as a name starting with Package_for_RollupFix followed by the build number. Restart afterwards. Do this from the console, never over the RDP session you are trying to save.

Known Issue Rollback, in Microsoft's words

Known Issue Rollback (KIR) switches off only the change that caused a problem, "without uninstalling the entire update", and leaves the rest of that update in place (Microsoft Learn, updated 5 November 2026). Three points from that page decide whether it can help you:

The September RDS entries link no KIR download. They mention only a "temporary mitigation through Group Policy" for administrators and then the out-of-band fix. For a single server, installing the latest cumulative update is the answer.

Get in when RDP is down on a VPS

Microsoft's first troubleshooting step is to test the machine through its console. On an RS Computers server that is the console in the client area: it shows the server's screen like a monitor would, so every command above works there with Remote Desktop broken. Check the build with winver, run Windows Update and restart. Restarting the Remote Desktop Services service can cut off open RDP sessions, another reason to work from the console. If the network path is the problem rather than an update, our checklist for Remote Desktop that can't connect starts with a port 3389 test.

Frequently asked questions

Why did Remote Desktop stop working after the September 2026 update?

Microsoft confirmed that the September 8, 2026 security updates could make Remote Desktop Services unstable on Windows Server 2016, 2019, 2022 and 2025 and on Windows 11, with RDP dropping after a few minutes or servers hanging at "Please wait for the Remote Desktop Configuration". Out-of-band updates on 14 September 2026 fixed it, and every later cumulative update includes the fix.

Does KB5131080 fix Remote Desktop on Windows Server 2025?

Yes. The RDS fix first shipped in out-of-band update KB5129235 on 14 September 2026, and Microsoft says it is included in updates released after that date. KB5131080 (10 November 2026, build 26100.33822) is one of those updates.

What does Remote Desktop error 0xC000000D mean?

It is a confirmed Windows 11 bug: non-admin users can't connect to a remote PC with Administrator protection enabled, and see "The token that was passed to the function is invalid." It started with preview KB5124010 on 22 September 2026 and is fixed by KB5132061, released 10 November 2026, installed on the remote PC.

Should I uninstall the update that broke RDP?

Not for the bugs in the table above, because each one already has a fix in a later update that keeps your security patches. Microsoft doesn't recommend removing installed updates. Uninstall only for a new problem with no fix yet, and pause updates so Windows doesn't reinstall it.

Why doesn't wusa /uninstall remove the cumulative update?

Modern cumulative updates are combined with the servicing stack update, and Microsoft says the servicing stack can't be removed after installation, so wusa.exe fails on the combined package. Use DISM /Online /Get-Packages to find the cumulative update's package name and DISM /Online /Remove-Package to remove it.

Can Known Issue Rollback fix the RDS problem?

Microsoft says KIR only covers non-security changes and it doesn't start KIRs for security fixes. The September RDS bug came with security updates, and its release health entries point to a Group Policy mitigation and the out-of-band fix, not a KIR download.

How do I get into my server when RDP doesn't work?

Use the provider's console. On an RS Computers VPS or VDS that is the console in the client area, which shows the server's screen without RDP.

Need a hand with a Windows server?

A few ways we can help:

← All articles

Chat on Telegram