Use this article to validate whether automatic RDP disconnects are caused by Remote Desktop graphics policies on non-GPU Azure VMs, especially during multi-monitor sessions. |
Symptoms
Users may connect successfully but are disconnected immediately after sign-in. The issue is commonly seen with RDP Error Code 3, Subcode 17 (Workspot Watch trace can help to identify the error & sub error code), especially when using multiple monitors.
Immediate disconnect after a successful login or session launch.
Failures are most visible when a user connects with multiple monitors.
Applies to
We have observed this issue, when the affected environment includes:
Windows 11 multi-session or Windows desktop operating systems.
Azure virtual machines without dedicated GPU resources.
Users connecting with two or more monitors.
Remote Desktop graphics acceleration Group Policy settings enabled.
Validation steps
Use these checks to confirm whether the issue is related to Windows/RDP graphics policy or the VDI platform.
Step | Action | Interpretation |
1 | Test single-monitor and multi-monitor connections with the VDI client. | If only multi-monitor fails, review graphics policy. |
2 | Repeat the same test with native Microsoft Remote Desktop Connection (mstsc). | If mstsc also fails, investigate Windows/RDP stack or policy. |
3 | Disable GPU-focused RDP graphics policies on a validation pool and retest. | If stable, keep those policies disabled for non-GPU VMs. |
Group Policy settings to review
Remote Desktop graphics policies can force sessions to use GPU-accelerated encoding or specific graphics display paths. On non-GPU Azure VMs, these settings can contribute to session instability during launch, particularly when users connect with multiple monitors. Use this section only to identify the relevant policy settings and their recommended state before making changes.
Check the following policy path on the VDI machine: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.
Policy | Why it matters | Recommendation |
Configure H.264/AVC hardware encoding for Remote Desktop Connections | May force hardware-assisted encoding that is not suitable for non-GPU VM sizes. | Disable or leave Not Configured unless validated. |
Prioritise H.264/AVC 444 graphics mode for Remote Desktop Connections | Increases graphics encoding requirements and may affect multi-monitor session stability. | Disable or leave Not Configured for non-GPU pools. |
Use hardware graphics adapters for all Remote Desktop Services sessions | Directs RDP sessions to use hardware graphics adapters, which may not exist on standard non-GPU Azure VMs. | Disable for non-GPU session hosts. |
Use WDDM graphics display driver for Remote Desktop Connections | Changes the display driver model used by RDP sessions and may influence session launch behavior. | Validate carefully; disable if disconnects stop after change. |
For non-GPU session hosts, these policies should generally remain Disabled or Not Configured unless the customer has validated them on GPU-backed workloads.
Remediation workflow
Use this workflow to make the change safely. Start with a limited validation pool, confirm the effective policy state, and expand only after the customer confirms that the disconnect issue is resolved and no new display issues are introduced.
Identify a limited validation pool or test VM that reproduces the issue. Avoid changing all production pools until the behavior is confirmed.
Set the GPU-focused RDP graphics policies to Disabled or Not Configured for non-GPU session hosts, based on the customer’s baseline policy standard.
Refresh Group Policy by running gpupdate /force if appropriate, then reboot the VM or refresh the validation pool when required by the customer’s change process.
Confirm the effective policy using gpresult or the customer’s standard policy validation method.
Retest user login with both single-monitor and multi-monitor sessions through the VDI client and native mstsc.
Promote the change only if sessions remain stable, RDP Error Code 3/Subcode 17 no longer appears, and no new display or performance issues are observed.