WVD black screen at logon

Occasional Contributor

We've noticed over the course of the past couple weeks some sporadic WVD logons exhibiting a black screen when attempting to logon from the RD client.  Thirty seconds later the connection is closed.  Attempting to access the VM using RDP also shows the same problem.


In the past week, however, we're now unable to provision WVD personal instances without the instances exhibiting this WVD black screen issue for each and every logon rendering the instances useless.  


In researching this issue this morning I stumbled on the following thread as we have 1909 instances.  



Disabling the use of the WDDM driver via HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\fEnableWddmDriver = 0 (Dword) [aka disabling the WDDM graphics display driver for Remote Desktop Connection Group Policy setting) has resolved the issue for us, but I'm concerned that this is even required at all.


Having no previous experience using XDDM over WDDM, are there any obvious negative consequences running this configuration?  Is a patch for Win10 1909 under development to address this black screen similar to this 1809 patch?




Improvements and fixes

  • Addresses an issue that displays a black screen to Windows Virtual Desktop (WVD) users when they attempt to sign in. 
5 Replies
1809/RS5 end of support is coming soon, you should upgrade your Windows 10 Vms. XDDM is the next generation that replaces WDDM. If you're running RS5, disabling it should not impact you negatively. Yes, we are working on the patch to address this black screen issue for for 2004, 1909.

@Soo Kuan Teo - thanks for your reply.   Do you have any insight on whether or not the 1909-related patch will be made available for the November patching cycle?

@anthonyschneider365 It would be great if we can get debug data see why the black screen is showing when using WDDM. Is there any way to reproduce and get us some data? Using the older framework isn't going to work on the long run, it will be deprecated in a future release of Windows.

@Soo Kuan Teo Any update on a fix for 2004 & 1909? Does going to 20H2 solve the issue?

@Soo Kuan Teo Are you sure about this? I thought XDDM is the older one. Could you kindly share any reference links to your statement?