Skip to content
TroubleGrid

Remote Desktop shows a black screen or drops after the September 2026 updates

Last verified November 2026Tested against NVIDIA GeForce driver 616.56 (26 August 2026) — introduced the RDP black screen, NVIDIA GeForce driver 616.64 (3 September 2026) — still affected, NVIDIA GeForce Hotfix driver 616.86 — first carried the fix, NVIDIA GeForce Game Ready driver 616.92 (9 September 2026) — carries the fix, WHQL, NVIDIA GeForce 617.14, 617.42, 621.01 and 621.14 — RDP black screen stays fixed, no RDP entry at all, September 2026 Windows security update — introduced the Remote Desktop Services instability, KB5129195 (14 September 2026, out-of-band) — carries the RDS fix on 24H2 and 25H2, KB5129194 (14 September 2026, out-of-band) — carries the RDS fix on 26H1, KB5124010 / KB5124006 (22 September 2026) — introduced the 0xC000000D connection failure, KB5127936 (28 October 2026) — fixes 0xC000000D on 25H2 and 26H2, KB5127653 (28 October 2026) — fixes 0xC000000D on 26H1, KB5132061 (10 November 2026) — fixes 0xC000000D on 24H2; Enterprise and Education editions only, Windows 11 24H2 Home and Pro — end of updates 13 October 2026, so no fix is offered on that version, KB5127936 (28 October 2026 preview) — also introduced a client-side RDP certificate mismatch, KB5132061 (10 November 2026) — fixes the client-side certificate mismatch as well, Windows 11 23H2, 24H2, 25H2, 26H1 and 26H2; Windows 10 21H2 and 22H2Well documented

Four updates broke Remote Desktop in four different ways, and the symptom tells you which. A window that stays black is NVIDIA driver 616.56 on the PC you connect to - update it to 616.92 or later. A session that connects then drops after a few minutes is the September 2026 security update - install the 14 September out-of-band update. A refusal with error 0xC000000D is the Administrator protection bug: KB5127936 on 25H2 and 26H2, KB5127653 on 26H1, KB5132061 on 24H2. And a connection that fails on the machine in front of you with a certificate mismatch is the October preview update - KB5132061 fixes that one too. Do not uninstall a security update for any of them.

Two separate September 2026 updates broke Remote Desktop within a week of each other, and almost everything written about it covers only one of them. The coverage that reached most people was about Windows Server, because that is where Microsoft's update caused the loudest failures. But if you are looking at a black Remote Desktop window on a home or gaming PC with a GeForce card, the more likely cause is your graphics driver — a bug NVIDIA acknowledged and fixed, and which no Windows article mentions. Both faults live on the machine you connect to, not the one in front of you, and they produce visibly different symptoms.

Symptoms

  • Remote Desktop connects, but the session window is entirely black and never draws the desktop
  • The black session is otherwise alive — the connection bar works and the machine responds, but nothing is drawn
  • The session connects normally, then fails after several minutes and will not reconnect
  • Signing in over RDP hangs at "Please wait for the Remote Desktop Configuration"
  • Microsoft Management Console, the RDS Licensing Diagnoser or File Explorer stop responding on the remote machine
  • The Windows Update page on the remote machine spins with a loading indicator and never finishes
  • The session refuses to connect at all and fails with error 0xC000000D, "The token that was passed to the function is invalid"
  • The connection fails from the PC you are sitting at because of a certificate mismatch, after the October 2026 preview update

Why this happens

NVIDIA driver 616.56 broke RDP display output

NVIDIA's release notes for 616.92 list "Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]" among the bugs that version fixes. This is a display-output fault, not a connection one: the session is established and alive, so the connection bar and the machine itself respond while the screen stays black. It lives on the machine you connect to. Drivers 616.56 and 616.64 carry the bug; hotfix 616.86 carried the fix first and Game Ready 616.92 carries it as a WHQL release. NVIDIA shipped this alongside fixes for two other 616.56 regressions — browser flicker and virtual displays failing to be created — which is a useful tell: if you also saw either of those on the same machine, you are almost certainly on the affected driver.

Update the NVIDIA driver on the PC you connect to · Roll the NVIDIA driver back to a release older than 616.56

The September 2026 Windows security update destabilised Remote Desktop Services

KB5129195’s own notes record, under "[Remote Desktop Services (known issue)] Fixed", that it addresses an issue affecting Remote Desktop Services after the September 2026 Windows security update, in which "RDS might become unstable, causing RDP connection and sign-in failures or servers to become unresponsive". This is a service-side fault rather than a display one, which is why the session draws normally and then dies. Note that Microsoft names the originating update as KB5122880 in that entry; the release-health pages that described this issue have since dropped the row, so KB5129195 is now the page that documents it.

Install the 14 September out-of-band Windows update

The October 2026 preview update broke RDP on the connecting PC

The only one of these four that lives on the machine in front of you. KB5132061 of 10 November 2026 records, under [Remote Desktop], that it "addresses an issue where Remote Desktop Protocol (RDP) connections might fail on the client due to a certificate mismatch after the October 2026 non-security preview update" — that is KB5127936, released 28 October 2026. Microsoft never opened a release-health known-issue entry for this, so KB5132061’s own notes are the only documentation of it, and they give no error text to match against. Treat it as the candidate when the host is fully patched and healthy but your own PC still cannot connect.

Certificate mismatch: update the PC you are connecting FROM

Fixes

Update the NVIDIA driver on the PC you connect to

about 15 min

616.92 is the first WHQL driver carrying NVIDIA's fix for the RDP black screen that 616.56 introduced.

Applies to: NVIDIA GeForce drivers 616.56 and 616.64, Windows 10 and Windows 11

  1. Do this on the PC you are connecting to, not the one you are sitting at. If you cannot see its desktop remotely, use its own monitor.
  2. Check the installed driver version: open the NVIDIA app and look under Drivers, or open NVIDIA Control Panel and choose Help then System Information.
  3. If it reads 616.56 or 616.64, that is the affected driver. Anything 616.92 or newer already carries the fix — and the fix has held: the 617.14, 617.42, 621.01 and current 621.14 release notes mention Remote Desktop nowhere. On those versions this article’s NVIDIA half is not your problem.
  4. In the NVIDIA app, open Drivers and install the latest Game Ready or Studio driver, then restart the PC.
  5. Reconnect over Remote Desktop. The desktop should draw normally.

Confirmed by the vendor.

Source: NVIDIA, NVIDIA, NVIDIA

Install the 14 September out-of-band Windows update

about 20 min

KB5129195 — KB5129194 on 26H1 — is the cumulative update Microsoft shipped specifically to resolve the Remote Desktop Services instability that the September 2026 security update introduced.

Applies to: Windows 11 23H2, 24H2, 25H2 and 26H1, Windows 10 21H2 and 22H2, Windows Server 2012 through 2025

  1. Again, do this on the machine you connect to. If it is currently hung mid-session, restart it first.
  2. Open Settings, then Windows Update, and select Check for updates.
  3. Install the out-of-band update released 14 September 2026 — KB5129195 on Windows 11 24H2 and 25H2, KB5129194 on 26H1 — or any later cumulative update, which already includes it.
  4. If Windows Update itself hangs with a loading indicator, which is one of this bug's own symptoms, download the .msu from the Microsoft Update Catalog and run it by hand instead.
  5. Restart and reconnect. On Windows 11 24H2 and 25H2 you can confirm the update landed by checking the build number reads 26100.9457 or 26200.9457 or higher.
    winver

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft

Error 0xC000000D: install the update that fixes it on your version

about 20 min

Microsoft fixed this on 28 October 2026 for 25H2, 26H2 and 26H1, and on 10 November 2026 for 24H2. The Administrator-protection workaround is no longer needed on any version that can take its update.

Applies to: Windows 11 25H2 and 26H2 (KB5127936), Windows 11 26H1 (KB5127653), Windows 11 24H2 Enterprise and Education (KB5132061), Hosts with Administrator protection enabled

  1. Check which Windows version the host is on: press Windows+R, run winver, and read the version line.
    winver
  2. On Windows 11 25H2 or 26H2, install KB5127936 or later. On 26H1, install KB5127653 or later. Both shipped on 28 October 2026.
  3. On Windows 11 24H2, install KB5132061 or later — the 10 November 2026 security update, which Microsoft lists as resolving this issue on 24H2. Note that it applies to 24H2 in Enterprise and Education editions only; 24H2 Home and Pro reached end of updates on 13 October 2026, so on those editions you must move the host to 25H2 or 26H2 instead, or keep using the Administrator-protection workaround below.
  4. Go to Settings > Windows Update and select Check for updates. KB5127936 is a preview update, so on an unmanaged PC you may need to turn on "Get the latest updates as soon as they are available" for it to be offered. KB5132061 is a normal security update and needs no such opt-in.
  5. Once installed, you no longer need to leave Administrator protection turned off. If it was disabled by policy as a workaround, put it back.

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft, Microsoft, Microsoft

Certificate mismatch: update the PC you are connecting FROM

about 20 min

The one fault on this page that is not on the host. KB5132061 fixes an RDP client failure caused by a certificate mismatch that the October 2026 preview update introduced.

Applies to: The PC initiating the connection, Clients that installed KB5127936 (28 October 2026 preview), Windows 11 24H2, 25H2 and 26H2

  1. Do this one on the PC you are sitting at — the opposite of every other fix on this page.
  2. Check whether it took the October 2026 preview update. Go to Settings > Windows Update > Update history and look for KB5127936, released 28 October 2026. Preview updates are only offered when "Get the latest updates as soon as they are available" is on, or when an administrator deploys them, so many PCs never received it and are not affected.
  3. If KB5127936 is there, install the 10 November 2026 security update on this PC: Settings > Windows Update > Check for updates, then restart.
  4. Confirm the build with winver — 26300.9974 on 26H2, 26200.9974 on 25H2, 26100.9974 on 24H2 — and try the connection again.
    winver
  5. Microsoft gives no error message or code for this one, only "connections might fail on the client due to a certificate mismatch". So treat it as a candidate rather than a diagnosis: if the host is fully patched, its driver is 616.92 or newer, and the failure happens before any session window appears, this is worth ruling out before you look at certificates or Group Policy yourself.

Confirmed by the vendor.

Source: Microsoft, Microsoft

Roll the NVIDIA driver back to a release older than 616.56

Check before applyingabout 25 min

NVIDIA documents the black screen as appearing after updating to 616.56, so a driver older than that does not carry it. This is the fallback when you cannot move forward to 616.92.

Applies to: NVIDIA GeForce drivers 616.56 and 616.64

Before you do this

Rolling back gives up the security fixes and game-specific work in the newer drivers, and reintroduces whatever 616.56 itself fixed. Moving forward to 616.92 is the better answer wherever it is possible; use this only when it is not.

  1. Download a driver older than 616.56 for your GPU from NVIDIA's driver archive before you start, so the machine is never left without an installer to hand.
  2. Open Device Manager, expand Display adapters, right-click the NVIDIA GPU and choose Properties, then the Driver tab, then Roll Back Driver.
  3. If Roll Back Driver is greyed out — it usually is once a restart has happened — run the older installer you downloaded and pick the clean installation option.
  4. Restart the PC and reconnect over Remote Desktop.

Source: NVIDIA

Known issues

  • NVIDIA: "Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]." Listed as fixed in Game Ready 616.92 WHQL, and in hotfix 616.86 before it. It has not come back: re-read on 11 November 2026, the 617.14, 617.42, 621.01 and current 621.14 notes mention Remote Desktop nowhere, and both 621.01 and 621.14 list no open issues at all.

    Affects NVIDIA GeForce 616.56, NVIDIA GeForce 616.64 · Status: fixed

  • Microsoft: Remote Desktop Services might become unstable after the September 2026 security update, causing RDP connection and sign-in failures or servers hanging. Resolved by the 14 September 2026 out-of-band update — KB5129195 on 24H2 and 25H2, KB5129194 on 26H1. Re-checked 11 November 2026: this row has aged off the release-health pages, so KB5129195’s own notes are now where it is documented.

    Affects KB5129195 (24H2 and 25H2), KB5129194 (26H1) · Status: fixed

  • The other KB5124008 regression readers arrive with — USB Audio Class 1.0 devices showing Code 10 or producing no sound — is now fixed too. Microsoft resolved it on 10 November 2026 with KB5132061, and with KB5132059 on 26H1. The multichannel half had already been fixed by the 14 September out-of-band update.

    Affects KB5124008, Fixed by KB5132061 / KB5132059 (10 November 2026) · Status: fixed

  • Windows 11 version 26H2 reached general availability on 29 September 2026, after both of the September fixes on this page shipped, and its release-health page has never carried a Remote Desktop Services entry. As of 28 October 2026 Microsoft says 26H2 is available for all eligible devices.

    Affects Windows 11 26H2 · Status: fixed

  • The third Remote Desktop issue - non-admin users failing to connect with error 0xC000000D on hosts with Administrator protection enabled - is now resolved on every affected version. Microsoft lists it as Resolved by KB5127936 on 25H2 and 26H2 and KB5127653 on 26H1, both 28 October 2026, and by KB5132061 on 24H2 on 10 November 2026. It originated in the 22 September preview update (KB5124010, or KB5124006 on 26H1).

    Affects Windows 11 25H2 and 26H2 (KB5127936), Windows 11 26H1 (KB5127653), Windows 11 24H2 (KB5132061) · Status: fixed

  • Windows 11 24H2 waited two weeks longer than the other versions for the 0xC000000D fix, and one edition still cannot get it. Microsoft resolved it on 24H2 with KB5132061 on 10 November 2026, but lists that update as applying to 24H2 in Enterprise and Education editions only. 24H2 Home and Pro reached end of updates on 13 October 2026, so the fix cannot reach them; moving the host to 25H2 or 26H2 is what does.

    Affects Windows 11 24H2 Home, Windows 11 24H2 Pro · Status: open

  • A fourth Remote Desktop regression, and the only client-side one. KB5132061 of 10 November 2026 records under [Remote Desktop] that it addresses RDP connections failing on the client due to a certificate mismatch after the October 2026 non-security preview update (KB5127936, 28 October 2026). Microsoft opened no release-health entry for it, so there is no status history, no error code and no affected-platform list — only this one line in the November update notes.

    Affects KB5127936 (28 October 2026 preview) — introduced it, KB5132061 (10 November 2026) — fixes it · Status: fixed

If none of this worked

If the machine you connect to has no NVIDIA GPU and is already patched past 14 September, neither of the first two causes applies to you. A black screen that also appears on that machine’s own monitor is a display or GPU fault rather than an RDP one - the flicker and virtual-display articles below cover the other 616.56 regressions. A refused connection with no 0xC000000D error is usually network, firewall, or Remote Desktop simply being switched off. Microsoft states the RDS issue does not affect Windows 365 or Azure Virtual Desktop, so a failure on either of those is something else. And check which Windows version the host runs before chasing a KB number: on 26H1 the September originating update is KB5124012 and the fix is KB5129194, the 28 October fix is KB5127653 rather than KB5127936, and on 24H2 the 0xC000000D fix is KB5132061 of 10 November 2026.

Common questions

Should I uninstall KB5124008 to get Remote Desktop back?
No. The out-of-band update is cumulative - it contains everything KB5124008 did, plus the fix - so installing it forward is strictly better than removing the update and losing September's security fixes. The same goes for the 0xC000000D bug: the 28 October updates fix it, so there is no version of this problem that is best solved by uninstalling anything.
The news said this only affects Windows Server. Why is my PC affected?
Reporting concentrated on Windows Server because that is where RDS deployments failed most visibly. Microsoft's own affected-platforms list for the issue names Windows 11 versions 23H2 through 26H1 and Windows 10 21H2 and 22H2 as clients, alongside the server releases. Separately, if your symptom is a black screen rather than a dropped session, no Windows version is involved at all - that one is the NVIDIA driver.
Is the 616.86 hotfix still worth installing?
No. Hotfix drivers are optional releases distributed from NVIDIA Customer Care rather than through the NVIDIA app. 616.86 carried this fix first, but Game Ready 616.92 is WHQL-certified, carries the same fix, and supersedes it - and every WHQL driver since, up to the current 621.14, still carries it.
Does any of this affect the PC I am connecting from?
One of the four does, as of November. Three of them — the NVIDIA black screen, the Remote Desktop Services instability and the 0xC000000D refusal — are all on the machine hosting the session, so updating the PC in front of you will not change those symptoms. But KB5132061 also fixes an RDP failure that happens on the client because of a certificate mismatch, introduced by the October 2026 preview update KB5127936. If the host is patched and healthy and your own PC still cannot connect, update your own PC too.
How do I tell the two apart quickly?
Watch what happens in the first minute. A window that is black from the moment it opens, on a machine with a GeForce card, is the driver. A session that draws the desktop normally and then dies a few minutes later, or never gets past "Please wait for the Remote Desktop Configuration", is the Windows update.
I get error 0xC000000D when connecting. Is that one of these two?
It is a third, separate problem - and it is now fixed everywhere. Non-admin users could not connect to a remote device with Administrator protection enabled, failing with 0xC000000D and "The token that was passed to the function is invalid". It came in with the 22 September preview update. Install KB5127936 on 25H2 or 26H2, KB5127653 on 26H1, or KB5132061 on 24H2 - that last one shipped on 10 November 2026 and applies to 24H2 Enterprise and Education editions only, so a 24H2 Home or Pro host has to move to 25H2 or 26H2 instead. Until the host is patched, the workaround is not a user-side one: an administrator has to reset the User Account Control "Type Of Admin Approval Mode" policy in Intune or Group Policy. Neither driver fix on this page will help, so do not change drivers for it.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • Microsoft · Release notes · checked Nov 11, 2026

    • Re-checked 11 November 2026: on Windows 11 24H2 the 0xC000000D Remote Desktop entry is now Resolved by KB5132061, resolved 10 November 2026 at 10:00 PT
    • The 0xC000000D issue originated in OS Build 26100.9550 (KB5124010) of 22 September 2026 and affects non-admin users connecting to hosts with Administrator protection enabled
    • Before KB5132061 the only mitigation was for IT administrators to reset the User Account Control Type Of Admin Approval Mode policy to turn off Administrator protection
    • Re-checked 11 November 2026: the Remote Desktop Services instability entry is no longer listed on this page — the table now shows only issues open or updated recently
    • As of 13 October 2026 Windows 11 version 24H2 Home and Pro editions reached end of updates; Enterprise and Education remain supported until 12 October 2027
    • The USB Audio Class 1.0 regression from the same September update is now Resolved by KB5132061
  • Microsoft · Release notes · checked Nov 11, 2026

    • Re-checked 11 November 2026: on Windows 11 26H1 the 0xC000000D entry is Resolved by KB5127653, released 28 October 2026
    • On 26H1 the originating update for the September 2026 regressions is KB5124012, and the 22 September preview update is KB5124006
    • Re-checked 11 November 2026: the USB Audio Class 1.0 entry on 26H1 is Resolved by KB5132059, released 10 November 2026
    • Re-checked 11 November 2026: the Remote Desktop Services instability entry is no longer listed on this page
  • Microsoft · Release notes · checked Nov 11, 2026

    • Windows 11, version 26H2 reached general availability on 29 September 2026
    • Re-checked 11 November 2026: on 26H2 the 0xC000000D entry is Resolved by KB5127936, released 28 October 2026
    • Re-checked 11 November 2026: the 26H2 known-issues table still carries no Remote Desktop Services entry
  • Microsoft · Knowledge base · checked Nov 11, 2026

    • KB5129195 was released on September 14, 2026 and produces OS builds 26100.9457 and 26200.9457 for Windows 11 versions 24H2 and 25H2
    • Its notes record under "[Remote Desktop Services (known issue)] Fixed" that it addresses an issue affecting Remote Desktop Services after installing the September 2026 Windows security update, in which RDS might become unstable, causing RDP connection and sign-in failures or servers to become unresponsive
    • KB5129195 names the originating update for the RDS instability as KB5122880, not KB5124008
    • It is offered through Windows Update and Windows Update for Business, and can also be downloaded manually as an .msu from the Microsoft Update Catalog or deployed through WSUS
  • NVIDIA · Release notes · checked Nov 11, 2026

    • Section 3.1.2 Fixed General Bugs in version 616.92 WHQL lists: "Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]"
    • The same fixed-bugs list includes the browser flicker [6673430] and the failure to create virtual displays after updating to 616.56 [6674464]
    • The notes are dated September 9, 2026
    • NVIDIA attributes the RDP black screen to updating to driver 616.56, so releases older than 616.56 do not carry it
    • Re-verified 11 November 2026: section 3.1.2 still lists the RDP black screen fix with bug id 6687328
  • NVIDIA · Knowledge base · checked Nov 11, 2026

    • GeForce Hotfix driver 616.86 fixes the RDP black screen introduced by driver 616.56 [6687328], the browser flicker [6673430] and the broken virtual displays [6674464].
    • Hotfix drivers are optional releases distributed from NVIDIA Customer Care rather than through the NVIDIA app.
    • 616.86 was the first release to carry the RDP black screen fix, ahead of the WHQL Game Ready driver.
  • NVIDIA · Release notes · checked Nov 11, 2026

    • The 617.14 release notes are dated September 22, 2026 (RN-08399-617.14_v01)
    • Re-verified 11 November 2026: the notes contain no mention of Remote Desktop or RDP
    • Section 3.1.2 lists the Samsung Odyssey G95NC HDMI issue and DisplayPort monitors failing to wake from sleep as fixed in 617.14
  • NVIDIA · Release notes · checked Nov 11, 2026

    • Document RN-08399-617.42_v01, dated October 6, 2026, for the Release 615 driver branch
    • Re-verified 11 November 2026: the 617.42 notes contain no mention of Remote Desktop or RDP
    • Section 3.1.1 lists Assassin’s Creed Shadows crashing to desktop after updating to 616.56 as fixed
  • NVIDIA · Release notes · checked Nov 11, 2026

    • Re-verified 11 November 2026: the 621.01 release notes contain no mention of Remote Desktop or RDP anywhere
    • Section 3.2, Open Issues in Version 621.01 WHQL, lists "N/A"
  • NVIDIA · Release notes · checked Nov 11, 2026

    • The 621.14 release notes are document RN-08399-621.14_v01, dated November 4, 2026, for the Release 620 driver branch
    • Section 3.2, Open Issues in Version 621.14 WHQL, lists "N/A" — NVIDIA records no open issues for this release
    • The 621.14 release notes contain no mention of Remote Desktop or RDP anywhere, so the 616.56 RDP black screen remains fixed in the current WHQL driver
    • Section 3.1.2 Fixed General Bugs lists only the RTX 50 Series / RTX Spark video playback freeze after updating to 621.01 [6979343]
  • Microsoft · Knowledge base · checked Nov 11, 2026

    • KB5127936 was released on 28 October 2026 and produces OS builds 26300.9818 (26H2) and 26200.9818 (25H2)
    • Under "[Remote Desktop (Known issue)] Fixed" it records that it addresses the issue preventing non-admin users from establishing Remote Desktop connections to remote devices with Administrator protection enabled, failing with error 0xC000000D and the message "The token that was passed to the function is invalid"
    • It applies to Windows 11 version 26H2 and version 25H2, all editions
    • It also fixes HDMI and DisplayPort audio playback on certain AMD graphics cards and Always On VPN connections stuck in Connecting
    • KB5127936 of 28 October 2026 is the October 2026 non-security preview update for Windows 11 25H2 and 26H2
  • Microsoft · Support page · checked Nov 11, 2026

    • KB5132061 was released on 10 November 2026 and produces OS builds 26300.9974, 26200.9974 and 26100.9974
    • KB5132061 applies to Windows 11 version 26H2 all editions, version 25H2 all editions, and Windows 11 Enterprise and Education version 24H2 only
    • KB5132061 states "Microsoft is not currently aware of any issues with this update"
    • Under [Remote Desktop], KB5132061 "addresses an issue where Remote Desktop Protocol (RDP) connections might fail on the client due to a certificate mismatch after the October 2026 non-security preview update"