Fix 0XC01E05E0: Remote Desktop Graphics Session Error

What Triggers 0XC01E05E0 and Why It's Almost Always a Registry Issue

You're running a GPU-accelerated app over RDP — maybe a CAD tool, a 3D renderer, or a game. You get the 0XC01E05E0 error: STATUS_GRAPHICS_ONLY_CONSOLE_SESSION_SUPPORTED. The message is blunt: this function can only run in the local console session. You're not on the console, you're remote. That's the whole deal.

The culprit here is almost always the Remote Desktop Session Host registry key blocking GPU fallback. Microsoft's default behavior in Server 2016, 2019, and Windows 10 (build 1809+) is to restrict DirectX and OpenGL access in remote sessions unless explicitly allowed. The fix? Two registry changes. Let's get to it.

Cause #1: Missing or Wrong Registry Values for GPU Acceleration

This is the fix that works 90% of the time. Your remote session can't talk to the GPU directly because the fEnableVirtualizedGpu and fEnableSoftwareGPU values aren't set.

Step-by-Step Registry Fix

1. Open Regedit as Administrator.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppSrv\Parameters
3. Create a new DWORD (32-bit) called fEnableVirtualizedGpu if it doesn't exist.
4. Set its value to 1.
5. Create another DWORD: fEnableSoftwareGPU and set to 1.
6. Restart the Remote Desktop Services service (or reboot the server).

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppSrv\Parameters]
"fEnableVirtualizedGpu"=dword:00000001
"fEnableSoftwareGPU"=dword:00000001

After the restart, try your app again. If the error's gone, you're done. If not, read on.

Cause #2: Group Policy Blocking RemoteFX or Remote Desktop Session Host

If the registry fix didn't work, someone's group policy is overriding it. It's common in domain-joined environments — IT locked down RemoteFX or Remote Desktop Session Host settings without telling anyone.

Check and Fix Group Policy

1. Run gpedit.msc (Local Group Policy Editor).
2. Navigate to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment
3. Find "Use hardware graphics adapters for all Remote Desktop Services sessions". Set it to Enabled.
4. Also find "Do not use RemoteFX Adaptive Graphics" — set it to Disabled.
5. Run gpupdate /force from an admin command prompt.
6. Reboot the server.

Heads up: On Server 2019 and later, RemoteFX is deprecated. If you're on Server 2019 or 2022, stick with the registry fix above. The group policy options for RemoteFX might be missing entirely — that's normal. Focus on enabling hardware graphics adapters through the policy shown.

Cause #3: Hyper-V Enhanced Session Mode Interfering with GPU Passthrough

This one's specific but I've seen it a lot. If you're running Windows 10/11 as a VM inside Hyper-V with Enhanced Session Mode (ESM) enabled, the guest OS sees the RDP session as non-console. The error pops up because Enhanced Session Mode maps the remote session to a virtual console — but the app expects direct GPU access.

Fix for Hyper-V VMs

1. On the Hyper-V host, open Hyper-V Manager.
2. Select your VM and go to Settings.
3. Under Management, click Enhanced Session Mode Policy.
4. Uncheck "Use enhanced session mode if available".
5. Connect to the VM using a standard RDP session (check "Show Options" → "Display" tab → uncheck "Use all my monitors").

Alternatively, you can keep Enhanced Session Mode enabled but use the registry fix from Cause #1 on the guest OS. That's often enough to bypass the restriction. If you need full GPU passthrough, you'll need Discrete Device Assignment (DDA) — that's an advanced topic for another day.

Quick-Reference Summary Table

That's the lot. Nine times out of ten, the registry tweak alone kills the error. If you're still stuck after trying all three, check the GPU driver version — some older drivers don't support remoting at all. Update to the latest OEM driver, not Microsoft's generic one.