1903.116 remote desktop problems

All computers are same specs: HP Elite 8000 4GB RAM - with SSD.

Client machines that I'm having problems with are both running WIN10 1903.116. (Fresh install not Upgrade)

If I try and RDP (over VPN or LAN) to computer I get a connection, can see the bar at the top of screen showing IP address but the rest of the screen is BLACK. Ctrl+Alt+End does nothing.

The computer I'm using to connect is WIN10 1809.529 - I use this computer to connect to other units on network & via VPN running 1809 & 1803 without a problem.

I also find that I can't use my 1903.116 computer to instigate a VPN connection just tries for a white then times out.

If I'm not mistaken, I think that the display adapter in that system may not have current Win 10 drivers available. As a test, try disabling the display adapter on one of the systems to force it to use the standard Windows display driver. They try connecting to that system via remote desktop. Does it work now?

BTW, I have the exact same problem on a really old system. Fortunately for me, I use this system headless so using the standard Windows display driver is acceptable for me.

hsehestedt,

Thanks for your reply, you are correct - Display drivers. I uninstalled and then it worked with basic drivers.

I have:

Intel(R) Q45/Q43 Express Chipset(Microsoft Corporation WDDM 1.1)
Driver Date: 11/3/2013
Driver Version: 8.15.10.2702

This machine works fine running 1809.529, I will put a graphic card into it and try again, This is not critical I was just testing the new 1903.116.

Same for me. Worked fine on 1809, not 1903. Wish I knew the exact cause.

I spoke to Microsoft support and they told me that 1903 is not ready for all computers. When my is ready for 1903 it will be made available via Windows Update. He said not all drivers had been included in the "Media Creation 1903" download.

I did not ask about VPN.

Here you get a 'solution', deinstall driver and use basic MS driver, you will loose higher resolutions or more monitors of course.
https://answers.microsoft.com/en-us/...0efb539?page=1
Denis Gundarev (Microsoft Employee) made a good posting, we will have to wait and hope for their solution.
There’s a known issue with some of the old display drivers.