Windows 10 V1903 black screen with Remote Desktop

Anonymous
2019-05-24T01:45:13+00:00

I upgraded my secondary machine from 1809 to 1903. When I access it now using Remote Desktop all I get is a black screen in the RDP windows. I then upgraded my primary machine to 1903 hoping that would help, but no. Fortunately I also have GoToAssist installed so I was able to log into the secondary machine that way and checked for updates, still no help. Finally I reverted it back to 1809 and Remote Desktop once again works. I could keep using GoToAssist but RDP over my local LAN is much faster.

As long as this version as been (more or less) gold before going public, I can't possibly be the first one with this issue. It's no big deal to me that my secondary is running 1809, it's primarily a file server, but upgrading would be nice.

Granted, that secondary system is an older Core2 Quad, but at 3.3GHz and 8GB of memory and a SSD, it's plenty fast enough. I suppose I could try a different video card, but it shouldn't be necessary for a feature update.

Anyone have some insight into why RDP isn't working. I've already been through all the "guesses".   :-)

*Modified title for accuracy*

*Original title: Windows 10 1903 (May update) black screen with Remote Desktop*

Windows for home | Windows 10 | Internet and connectivity

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
Answer accepted by question author
Anonymous
2019-07-14T03:31:57+00:00

Workaround reported here is to set the group policy to force RD sessions to use XDDM instead of WDDM:

Gpedit.msc: Computer Configuration->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Remote Session Environment


Moderator's note:

If Group Policy method doesn't works, open administrative Command Prompt, type this, and press Enter key:

REG ADD “HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services” /v “fEnableWddmDriver” /t REG_DWORD /d 0 /f

Microsoft has also released update KB4512941, which addresses this issue:

https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941

The update page mentions:

  • Addresses an issue that displays a black screen when you use Remote Desktop to connect to a machine running Windows 10, version 1903.

You can install KB4512941 and this would resolve the issue for you. 


Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2019-05-30T19:52:43+00:00

In my case all Intel G41 drivers currently available, from Intel (2009), and from Microsoft (2013), showed black screen with RDP, even though they are Ok with the monitor connected to the PC.

So I've decided to use the "Microsoft Basic Graphics" driver, shown in the compatibility list when I tried to update the driver manually, and now RDP works.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

148 additional answers

Sort by: Newest
  1. Anonymous
    2019-07-15T15:42:49+00:00

    I don't think he's talking about having done that, is he?  Not sure why he'd still have that fix in effect now when there's a better way.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-07-15T15:31:02+00:00

    Not exactly.  The fix that some of us are using (disable the graphics driver and use the Microsoft Basic Driver) may work for RDP to the host machine, but then using the host machine directly is borked.  Fix one, break the other; pick your poison.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-07-15T15:20:13+00:00

    That sounds like a different classification of problem, since you're talking about things like black screens on boot and other local scenarios. The bug in this thread narrowly pertains to RDP only, never when using the given machine itself.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments