Share via

Remote Desktop black screen

Anonymous
2019-07-03T13:24:51+00:00

After installing update 1903 on second computer I get a black screen when remote desktop connects. Tried rolling back video driver which took me back to a Microsoft basic driver from 2006 but only offers 1024x768 for best setting. This causes programs to be so large you can see everything. Both computers are running update 1903. With the old graphic driver I don't get black screen.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

17 answers

Sort by: Most helpful
  1. Anonymous
    2019-07-16T03:27:31+00:00

    We faced this problem last month and found that it’s related to XDDM vs WDDM display driver model.

    Finally solved by using GPO to force use back the old XDDM display driver.

    In [Computer Configuration->Policies->Windows Settings->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Remote Session Enviroment], set the Policy [Use WDDM graphics display driver for Remote Desktop Connections] to Disabled.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-07-17T15:17:52+00:00

    Thank you for the solution it worked on both computers that I ran into the issue. I made just a few changes to your instructions to make it easier for lesser experienced individuals to locate.

    In [Local Group Policy Editor->Local Computer Policy->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Remote Session Enviroment], set the Policy [Use WDDM graphics display driver for Remote Desktop Connections] to Disabled.

    Note: If you have trouble finding the Local Group Policy Editor go to settings and type in Administrative Templates in search box and you will see it in the results.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-07-18T06:30:02+00:00

    You're welcome! We discovered the problem in our testing environment since end of May and solved a week later, as seeking help to local MS support was no used. I didn't find any reference about this problem on internet or any Microsoft Community/forum, so apologize for the relate reply here after the problem rose public concern. Anyway, for registry method, it's mentioned here in Deutsch: https://www.mos-computer.de/pages/posts/windows-10-1903-remote-desktop-probleme-464.php

    Here is the english translation:

    You can alternatively set the following in the registry ; 

    REG_ADD "HKLM \ SOFTWARE \ Policies \ Microsoft \ Windows NT \ Terminal Services" / v "fEnableWddmDriver" / t REG_DWORD / d 0 / f

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-09-04T14:34:56+00:00

    Thank you for the solution it worked on both computers that I ran into the issue. I made just a few changes to your instructions to make it easier for lesser experienced individuals to locate.

    In [Local Group Policy Editor->Local Computer Policy->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Remote Session Enviroment], set the Policy [Use WDDM graphics display driver for Remote Desktop Connections] to Disabled.

    Note: If you have trouble finding the Local Group Policy Editor go to settings and type in Administrative Templates in search box and you will see it in the results.

    The last windows build for the 30th august didn't solve the issue but this one did! Thank you!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-07-04T19:42:55+00:00

    Seems like a Microsoft bug, I think its too new to have a fix yet.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments