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
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
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

148 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-09-10T22:42:53+00:00

    I now have very similar symptoms on only one of my three machines after the update. I am not yet convinced that the RDP interplay is the cause as the update addresses other issues besides the RDP 'black screen' issue.  Interestingly, the machine that is now failing ( Compaq V6000) is NOT the machine I had to patch the registry to disable WDDM 1.1 (Acer Aspire 5338) to get RDP working. This machine (Acer Aspire 5338) is working fine with the update installed and the patch removed.

    I have now completely re-built The Compaq V6000 with X86 rather than X64 - then loaded up to Insider Preview 1903 18362.10019 and the machine is working just fine with RDP. I am assuming here that 18362.10019 includes KB4512941 and this took the build to 18362. 329.

    Compaq V6000 

    AMD Turion 64 X2 TL-60 2Ghz

    4GB 

    NVIDIA GeForce Go 6150

    Acer Aspire 5338

    Intel Celeron Dual Core T3000 1.8Ghz

    8GB

    Mobile Intel(R) 4 Series Express Chipset Family (Microsoft Corporation - WDDM 1.1)

    Will now run the V6000 for a few days then re-load back to X64 1903 without the update. Will then install the WDDM1.1 registry patch then slowly ramp up to KB4512941 with a view to pinning it down.

    Will keep you posted guys...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-09-10T16:20:49+00:00

    Just to be clear ... Opti 380's were discontinued more than 7 years ago and they don't have two video card slots.

    I had problems with the Nvidia on one PC and moved the drive to a different PC, assuming the first one had hardware problems. (It was locking up, had to be forced-shutdown several times, etc.)

    I ran into the exact same set of problems on the second PC, so I replaced the Nvidia with the AMD. I'm not seeing the lock-ups, etc., but I am still seeing the RDP issues.

    So ... it's not a case of "You're running two brands of video cards and the two sets of drivers are probably interfering with each other." (And I did remove the Nvidia drivers when I installed the AMD.)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-09-10T16:15:39+00:00

    I'm running into this too, on two Dell Optiplex 380 SFF PC's with both an Nvidia GEForce 210 GPU and AMD 5450 cards.

    Those are low-end cards and the latest drivers are 2015-2016.

    Oddly, I can go into the PC using Chrome Remote Desktop, close CRD--and then RDP into that PC will work! ...

    But it's not a case of "use CRD once and then RDP will work permanently" or "use CRD, then RDP will work until you reboot."

    Was this answer helpful?

    0 comments