KB5083769 Windows 11 Pro RDP display crash upon connection - Multi Monitor

Question

KB5083769 Windows 11 Pro RDP display crash upon connection - Multi Monitor

Adam 0

Since updating to KB5083769, my Windows 11 host that I RDP to (Remote Desktop) gets a black screen, sends a message that the administrator ended the connection for 0x3, 0x11. When examining the logs on the host I can see the Remote Desktop virtual graphics adapter is crashing.

Things I have attempted -

Disabling Hardware accelerated RDP
Disabling WDDM RDP
Disabling UDP (This was because I could see it failing as it was estimating connection quality)
Disabling the algorithmic check for connection quality
Rolling back KB5083769 (System failed to do this)
Updating to the May preview (KB5089549)
Updated Graphics drivers
Updated Bios
Updated all other system drivers

None of those things worked.

I then noticed upon connection one screen would show connectivity first, then a few seconds later the other screens in my multi monitor setup would show black screens as it was connecting and then the crash.

The workaround -

If I connect with one screen first, in my four-monitor setup it seems to always work. If I then disconnect, I can connect sometimes with all four of my screens. With two screens, I can connect to one monitor and disconnect back to two monitors fairly consistently each time. With three screens, going to a single monitor then back to three screens seems to have the success rate as four screens.

My hardware setup-

Ryzen 5950X on x570 chipset

64GB of Ram

A310 Intel GPU

0 comments

2 answers

Your answer

Answer 1

The described behavior matches a known Remote Desktop issue introduced by recent Windows 11, version 24H2 updates, where RDP sessions can freeze or disconnect shortly after connection, especially in multi‑monitor or UDP/WDDM scenarios.

From the available information:

After installing the January 2025 Windows preview update KB5050094 and later updates, Windows 11 24H2 devices can experience:
- Remote Desktop sessions freezing shortly after connection, with mouse and keyboard becoming unresponsive and requiring reconnect.
- RDP sessions unexpectedly disconnecting (often around 65 seconds) when using UDP-based connections to older RDS hosts.
Similar symptoms are also documented after installing later cumulative updates (KB5051987, KB5053598), with increased reports of RDP disconnects and freezes.
A fix for at least the “Remote desktop might freeze” issue on affected builds is included in the April 8, 2025 update KB5055523. Guidance is to ensure the system is fully updated to that or later build so that the RDP stability fixes are applied.

Given the steps already tried (disabling hardware acceleration, WDDM, UDP, updating drivers/BIOS, and attempting rollback), the next concrete remediation path supported by the documentation is:

Ensure the Windows 11 host is on a build that includes the RDP fix:
- Install the April 8, 2025 update KB5055523 (OS Build 26100.3775) or any later cumulative update that supersedes it.
- After updating, reboot and test RDP again with the full multi‑monitor configuration.
If the host is running Windows Server 2025 as an RDS host, the same guidance applies: install KB5055523 or later to resolve the “Remote desktop might freeze” issue.
Until the host is on a fixed build, continue using the single‑monitor connection workaround that avoids triggering the crash, as this aligns with the documented behavior of RDP instability on affected builds.

If, after updating to a build that includes KB5055523 or later, the problem persists with multi‑monitor RDP, collect fresh event logs and consider opening a support case, as the documented RDP issues should be mitigated by that update.

References:

Answer 2

Hi,

Since you have already tried standard driver updates and Group Policy overrides for WDDM and UDP, this specific failure is a flaw introduced in recent Windows 11 updates where the host fails to allocate virtual framebuffers for dense multi-display layouts. Since your system is actively blocking a rollback of the problematic update, the best permanent fix outside of your single-monitor connection workaround is to wait for an official hotfix from Microsoft.

In the meantime, you can try to bypass the layout negotiation crash by forcing the client to connect using a matching, static resolution file instead of relying on the dynamic full-screen multi-monitor handshake. You can do this by opening your Remote Desktop Connection client, navigating to the Display tab, unchecking "Use all my monitors for the remote session," setting the slider to a fixed custom resolution that spans your screens, and saving it as an .rdp file to see if that stabilizes the connection.