Windows 10 V1903 black screen with Remote Desktop

Anonymous

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*

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

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.

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

148 additional answers

Anonymous

2019-08-19T15:25:28+00:00

This is an 'Old Microsoft' driver issue. This has happened before
Was this answer helpful?

0 comments No comments
Anonymous

2019-08-19T15:47:46+00:00

This issue must absolutely be fixed. It is related to the last update.

This issue must absolutely be fixed. It is related to the last update.

This issue must absolutely be fixed. It is related to the last update.

Hello? Microsoft? Hello? This issue is documented ALL OVER THE WEB.

Please FIX THIS ISSUE NOW.
Was this answer helpful?

0 comments No comments
Anonymous

2019-08-19T16:13:55+00:00
Update:

I recently reported that disabling the Triton Forcepoint (Websense) client 'fixed' the issue I reported. Someone else also reported this but using a different web filtering agent (Carbon Black).

I have done further testing. It is also now apparent that disabling the Sophos anti-virus also 'fixes' the issue. When I say 'fixes', I mean the issue does not occur in this scenario.
1. With Sophos ant-virus installed and Websense agent installed, the issue DOES occur. (see my previous post for detail).
2. With Sophos anti-virus uninstalled and Websense agent installed, the issue does not occur.
3. With Websense agent uninstalled and Sophos AV installed, the issue does not occur.
4. The Sophos agent AND the Websense agent can both be installed without issue on older releases of Windows (< 1903).
So in a nutshell, it would appear to be all three components all living together under one roof that causes the issue. web filtering, AV and Windows 10 build 1903. My suspicions are that other web filtering and / or AV products may have the same issues with 1903.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments