Forum Discussion
Windows 10 Version 1809, Remote Desktop Connection not working from PC but working fine from macOS.
Updated yesterday to version 1809,
Remote Desktop Connection from another Windows 10 version 1809 not working.
It looks like connected, but the whole screen is blank and the mouse cursor become hourglass then about 1 minute later, lost connection. Then trying to re-establish the connection, but the screen is still black. This time mouse cursor even stuck and not showing in the screen.
Thanks for your update and contacting us.
If the registry workaround the issue, then mostly this KB should fix it : https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887
install on both client and server ( source, destination)
If you still experience the issue, please do let us know. So we can help you further.
75 Replies
- maydoganCopper Contributor
in case if you are still looking for a solution for this one. Enabling Turn Off UDP On Client worked for me.
Open gpedit and navigate to computer configuration\Admin Templates\ Windows Components\Remote Desktop Services\ Remote Desktop Connection Client
Enable Turn Off UDP On Client apply and try connecting again.
I hope this helps
- Haas07Copper Contributor
disabling UDP did the trick for me!
Kudos to Maydogan & ITManager from bringing this (temporary) workaround!
- ITManagersCopper Contributor
The problem happen only if enabled the UDP on Remote Desktop Connection in 1809
The UDP enabled automatick
So how can desable the UDP ???
- maydoganCopper Contributor
To disable UDP on client machine.
Open gpedit and navigate to computer configuration\Admin Templates\ Windows Components\Remote Desktop Services\ Remote Desktop Connection Client
Enable Turn Off UDP On Client apply and try connecting again.
I hope this helps
Just tested on 1809.
Made a connection from a windows 10 1809 client to a windows 10 1803 client, via hostname and via IP, both seem to work, so OK.
From the same machine, made an RDP connection to a Windows Server 2012 R2 via hostname and IP, screen stays blank for a bit longer, but eventually working. So also ok.
- gcannCopper Contributor
Ditto to all the above symptoms, 1809 version, cannot connect to any RDC enabled OS (W2008 - W2016)
Which blows, as I have several hundred RDP sessions saved. :-/
If you are in a pinch, download the remote desktop app, at least you can connect on the fly until this is fixed or until you can try the UDP disable reg settings mentioned
RDC APP: https://www.microsoft.com/en-us/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot:overviewtab
- David SmithCopper ContributorI have the same problem. Remote Desktop client stopped working right after this update. Very frustrating. Still reading but I hope there is a fix.
- Euclid MatCopper Contributor
I do have the same problem (as Munn). The only workaround is to enable "Turn Off UDP On Client" in the group policy editor.
- Phillip MunnCopper Contributor
Also seeing this problem. When logging in remotely from a PC running 1809 to another PC running 1809 over the WAN RDP draws the first few frames and then suddenly locks up.
- David SmithCopper ContributorYep, I am getting exactly the same symptom.
- Bruce SBrass Contributor
Same issues with RDP. Cannot connect to remote session.
- Péter FülöpCopper Contributor
The only one solution is to, use the computer network name not the ip adress. But this is a half solution......
Have a nice day
- Malcolm ClarkCopper Contributor
As it happens I was using the machine address and not the IP address and it was not working using the machine address. I can't check this any further at present because I've rolled back to 1803.
One thing that seemed odd was that I was able to remote desktop using a machine on the local network, but not over a vpn connection (and I did check the vpn was working correctly by connecting to other machines that were not updated to 1809).
- Martin LarssonCopper Contributor
Same problem here, my rdp server is behind a router with portfoward.
On my computer I can connect from my office but not from home (both places behind NAT)
I have no idea why it works from my office, before 1809 it worked from anywhere.
- Mark SmithCopper Contributor
Same problem. A black screen. Can confirm that the cumulative update didn't resolve this.