Intermittent RDP display stops refreshing (session still responsive) on Azure VM

Question

When connected to one of my virtual machines via RDP, the session periodically stops updating the display. The VM does NOT appear to freeze and the RDP connection does not drop—I can still move the mouse, click, and type—but the screen does not visually refresh, so I can’t see any changes. The only workaround is to close the RDP session and reconnect.

Why would this be occurring?

Answer 1

BA - When this occurs, the RDP session on the VM remains active and healthy, and the system continues to process keyboard and mouse input. However, the visual updates sent to the client stop refreshing, which makes the screen appear frozen until the user disconnects and reconnects.

Microsoft confirms this behavior in multiple RDP cases where:

• The user can still interact “blindly” (typing, clicking).
• The session immediately resumes normally after reconnecting.
• No crash or reboot is recorded on the VM.

This is consistent with how RDP operates: input/control traffic and graphics output are handled separately within the protocol. A disruption in the graphics encoding or transport path can stall screen updates while leaving the session itself unaffected.

This condition typically occurs due to one or more of the following supported causes:

1. RDP graphics transport or codec issues RDP encodes desktop frames (software or GPU‑accelerated) and delivers them over RDP graphics channels. If this encoding or delivery path stalls, screen updates stop even though the session is still running. This behavior is documented as expected when there is a disruption in the graphics pipeline rather than a session failure. [learn.microsoft.com]
2. UDP transport instability Modern RDP sessions use UDP (in addition to TCP) to improve responsiveness. Microsoft acknowledges that on unstable or high‑loss networks, UDP‑based RDP graphics can stall while the TCP control channel (input) continues to work. In such cases, reconnecting refreshes the graphics stream, which explains why reconnecting temporarily resolves the issue.
3. Display driver / graphics acceleration interaction on the VM Microsoft‑documented cases show that outdated or incompatible display drivers, or certain hardware acceleration paths, can cause RDP rendering to stop updating even though the VM and user session remain healthy.

Microsoft recommends first determining whether the issue is client‑side or VM‑side:

1. Shadow the session from another admin machine - If an administrator shadows the session and sees live updates while the user’s own RDP window is frozen, this confirms the issue is client‑side (RDP client or network path), not the VM.
2. Test from a different RDP client or network

• Try a different device or operating system.
• Test with the latest Microsoft Remote Desktop client (native mstsc.exe or Microsoft‑provided app). If the issue only occurs from specific endpoints, Microsoft guidance is to focus on that client stack rather than the VM.

Supported mitigations on the Azure VM

The following actions are within Microsoft support boundaries and commonly resolve this behavior:

1. Ensure the VM OS and display drivers are up to date Keep Windows fully patched and validate the active display driver. Driver mismatches are a known contributor to frozen RDP visuals. [learn.microsoft.com]

Adjust RDP graphics acceleration settings (GPO‑based) On Windows Server / multi‑session hosts, Microsoft supports testing with:

Hardware graphics acceleration for RDP disabled.

• Less complex graphics modes if enabled previously.
• These changes can stabilize the graphics pipeline when rendering issues are observed. [learn.microsoft.com]
• Verify VM resource health Microsoft notes that when CPU or memory pressure exists, the Desktop Window Manager and RDP encoding path can be impacted, resulting in delayed or frozen screen updates without a session drop.

Supported client‑side mitigations

Even when the VM is healthy, Microsoft supports the following client‑side actions:

Update the RDP client to the latest Microsoft version Several Microsoft Q&A cases confirm that newer RDP client builds resolve rendering and refresh issues seen in older clients.

1. Reduce RDP visual complexity In the RDP client settings, temporarily lower visual experience options (effects, animations, high color depth) to reduce graphics encoding stress. This is a supported diagnostic step to confirm client‑side rendering sensitivity. [learn.microsoft.com]
2. Evaluate UDP vs TCP behavior If the issue reproduces mainly on high‑latency or VPN‑based connections, Microsoft supports testing RDP with TCP‑only transport to validate whether UDP graphics traffic is contributing to the stall. [learn.microsoft.com]

Answer 2

The host’s RDP draw‑queue is stalling, so the session stays alive while the screen won’t update; turn off AVC/H.264 on your client, and if it still freezes, a Redeploy will move the VM to a clean host.