Windows video subsystem failed. The relevant status code was 0xD0000001

Question

We have several users remoting onto Windows 10 PCs from other Windows 10 or Windows 11 PC. If the user leaves the local session running and locks the PC, when they try to remote to the PC with the locekd session, the remote desktop client connects briefly, then crashes, producing the error messages below.

This is occuring on systems using Intel Graphic drivers and NVIDIA. We have removed 3rd party AV but that did not resolve issue.

Any help is appreciated on this.

Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/5/2022 5:39:44 PM
Event ID: 20
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: PC-name
Description:
Attempt to send connect (3) message to Windows video subsystem failed. The relevant status code was 0xD0000001.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>20</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2022-05-05T23:39:44.742636200Z" />
<EventRecordID>920</EventRecordID>
<Correlation ActivityID="{F4206694-9EA7-4486-93FC-D1DD28960000}" />
<Execution ProcessID="1036" ThreadID="6712" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>PC-name</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns="Event_NS">
<messageName>connect (3)</messageName>
<errorCode>0xd0000001</errorCode>
</EventXML>
</UserData>
</Event>

Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/5/2022 5:39:44 PM
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: PC-name
Description:
An error occurred when transitioning from DisconnectedLoggedDesktopLocked in response to EvConnected. (ErrorCode 0xD0000001)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>36</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2022-05-05T23:39:44.742640400Z" />
<EventRecordID>921</EventRecordID>
<Correlation ActivityID="{F4206694-9EA7-4486-93FC-D1DD28960000}" />
<Execution ProcessID="1036" ThreadID="6712" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>PC-name</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionId">3</Data>
<Data Name="State">13</Data>
<Data Name="StateName">DisconnectedLoggedDesktopLocked</Data>
<Data Name="Event">3</Data>
<Data Name="EventName">EvConnected</Data>
<Data Name="ErrorCode">0xd0000001</Data>
</EventData>
</Event>

Answer 1

I have the same problem on my company laptop (Windows 10 Enterprise x64 Version 10.0.19044.1645) equipped with Intel iGPU and NVIDIA dGPU.

Problem emerged after installing KB5012599.

If I uninstall KB5012599 and reboot I can again connect to the laptop using RDP.

The errors observed are:

Windows Logs > Application:

• The Windows logon process has unexpectedly terminated.

Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager:

• Attempt to send connect (1) message to Windows video subsystem failed. The relevant status code was 0xD0000001.
• An error occurred when transitioning from DisconnectedLoggedDesktopLocked in response to EvConnected. (ErrorCode 0xD0000001)

NVIDIA Driver version is 512.59 (i.e. the latest one) which I installed to see if it would fix the problem but it didn't.

I have the following local policies configured to optimize RDP performance:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment:

• Use hardware graphics adapters for all Remote Desktop Services sessions (Enabled)
• Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections (Enabled)
• Configure H.264/AVC 444 hardware encoding for Remote Desktop Connections (Enabled)
• Use WDDM graphics display driver for Remote Desktop Connections (Disabled)

I have also ran the NVIDIA OpenGL RDP enabler tool so I can run applications that use OpenGL through RDP, but I removed the NVIDIA driver database where this setting is stored to disable it and determined that the problem is not related to OpenGL support state.

WDDM was disabled for RDP at some point in the past because of issues with NVIDIA drivers. After some digging I see now that XDDM support has been removed from Windows 10 21H1. It seems that KB5012599 has finally hit the kill switch for XDDM, at least when it comes to Windows 10 Enterprise channel.

After changing the policy Use WDDM graphics display driver for Remote Desktop Connections back to Not Configured and rebooting, the RDP connection now works for me just fine.

Answer 2

Hello

Thank you for your question and reaching out.
I can understand you are having some issues related to RDS in Windows 10 or 11.

1. Please try to Update Intel and Nvidia Drivers to latest version.

2 Please try take RDP with Lower Display Resolution as it may that your RDS is not supporting higher Resolution.

3. Change your gateway to explicitly deny redirection except for drives and clipboard.
4. Please power-cycle your RDS servers once to see if it resolved automatically some times.

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Uninstalling KB5013942 fixed this for me.