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
I've been struggling with something similar for some time. The upgrade to Windows 10 1903 made no difference. Disabling UDP and changing the display emulation on my 3 VMs (all running Windows 10 1903 as well) also had no effect. The RDP connection appears to freeze on the login screen and requires a reboot of the VM.
Today I found a fix by deleting the stored profiles on the client PC, remaking them and ticking the "Always ask for credentials" box. I can now connect to all 3 VMs, entering the login password when prompted. If I revert to not asking for credentials (I.e. storing the passwords) the login freeze returns.
Change Firewall Settings Windows Firewall is also one of the most common causes of Remote Desktop problems.
If Remote Desktop is blocked by Firewall, you won’t be able to connect it with another device. To check if Windows Firewall blocked Remote Desktop, do the following:
Go to Search, type firewall and open Windows Defender Firewall.
Remote Desktop can't connect to the remote computer for one of these reasons Windows 10 Go to Allow an app or feature through Windows Firewall. Windows 10 RDP client not working Click on Change Settings.
RDP this computer can't connect to the remote computer Find Remote Desktop, check it, and click OK to save changes. Remote Desktop not working after Windows 10 upgrade Now try to connect your computers via Remote Desktop, and it should work.
- Check of Windows Defender Firewall rules revealed that ones for Remote Desktop were disabled after I did update to version 1903. After enabling them RDP started working.
Hey Harry,
Rebooting temporarily fixes the problem.
Disabling bitmap caching or changing resolution on RDP client.
Pressing CTRL + ALT + END doesn't do anything.
Created a new account and tried logging on to that to test if it is account related.
try doinf a sfc /scannow to do a system scan and fix corrupt files.
Regards,
Akshay
System Admin | Apps4Rent
Hi,
I have the same problem after updating to 1903, "Turn Off UDP On Client" did not help for me.
It's an issue also with Win 10 1809 to Win 10 1809
You can work around this by disabling UDP session used by MSTSC on your affected Win 10 1809 computer (the one where you're running the Remote Desktop client).
Run Group Policy Editor. Navigate to Computer Configuration > Administration Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. Set the "Turn Off UDP On Client" setting to Enabled.
Try connection again in MSTSC. Should work OK. No reboot required.
Copied from https://social.technet.microsoft.com/Forums/windowsserver/en-US/dff1a051-afa9-48e5-ba77-4c5cffd54634/issue-connecting-to-rdp-only-win10-1809-gt-windows-server-2019? and fixed the problem for me, thought worth sharing.
I have the exact same problem. Win 10- 1809.
Upon opening mstsc windows client and the app store version, both freeze completely and are unusable. I am connected to an l2tp Meraki vpn and also via l2tp Windows 2012 vpn. I cannot even use the rdp client without these vpn connections either. It completely freezes on open. As soon as I begin to enter an address, it stops responding. After waiting a very long time, I can slowly get the address in but if I hit connect, it stops responding again. Very frustrating issue....
ImSkiZZeR It has been fixed in Windows 10 Version 1903. Use the Windows Update Assistant to update to this version: https://www.microsoft.com/en-us/software-download/windows10
- after installing windows 10 may 2019 update, everything works for me again
We recently experienced this when using RDP from Windows 10 v1809 to another Windows 10 v1809 machine. This worked for us.
Add a new registry entry in:
"HKLM:\Software\Microsoft\Terminal Server Cient"
UseURCP
REG_DWORD 0
Supposedly Microsoft is working on releasing an update sometime in April that fixes this issue.
- Yeah we know the workaround.. Great but editing the registry is not an acceptable fix!
FerasShehadehMicrosoft
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.
Has anyone here tried reporting it to Feedback Hub? If yes, please share your link so that the rest of us can upvote. After all, that's the official way of getting Microsoft's attention.
I think the issue discussed at https://social.technet.microsoft.com/Forums/windowsserver/en-US/dff1a051-afa9-48e5-ba77-4c5cffd54634/issue-connecting-to-rdp-only-win10-1809-gt-windows-server-2019
stems from the same problem, or is in fact the same issue.
Just like here, Microsoft also ignores them there.
- Microsoft ignored? Did you try getting Microsoft's attention in the first place? The correct way of doing it is to post to Feedback Hub and share a link to the report here, so we can upvote it.
Any update on MS from this?
Hey there buddy,
Use RDC Wrapper.
https://github.com/stascorp/rdpwrap/issues/578
It helped me. You need to find exact configuration for Your current Windows version.
Wrote to Windows live support, they told me that RDP Wrapper is not illegal so that's that.
With kind regards
Bryanseriously microsoft it's time to fix this. It's confirmed that disabling UDP in firewall to the RDP-host is a fix for this, so why don't you fix it? I can't go around blocking udp everywhere.
This is hurting.
Okay, so Sys Admin at the company I work at told me, that there's some chance that Remote Desktop Connection and Remote Assistance [which use the same GUi and libraries] have most likely been severed. Now You need to issue invitations. It works for me via invitations. I have Windows 10 Home @ work and Windows 10 Pro @ home, so I can connect, via invitation. I switched to TightVNC and original RealVNC client. Works much better.
Cheers!
//edit: Well, not even dayum invitations are working :(Hello,
I stumbled across a similar problem.
Between 2 Win10 Pro 1809 I only got a black picture, but I could control the computer in the session: It was possible to write texts, click icons and move windows.
After some debugging I noticed that I had different MTU settings for host and client.
I then tested the following settings:
- Host: jumbo frames 9k + client: jumbo frames off = black screen as described above
- Host: jumbo frames off + client: jumbo frames off = runs immediately
- Host: jumbo frames 9k + client: jumbo frames 9k = runs immediately
- Host: jumbo frames off + client: jumbo frames 9k = frozen waiting-cursor with login image, which is also frozen. After approx. 40 sec. desktop appears and it seems to work normally
I hope I can help someone with their problem.
sincerely yours,
Heiko
Translated with www.DeepL.com/Translator
Same stuff, different day, or how it goes. I have the same problem. Good job MS, on Your third iteration of 1809, which forced unto my work computer and now I need to pay for AnyDesk in order to use it full time. "Good job, really good job"
Same problem here, but I can confirm that I, in fact, have control! Once I opened a folder full of Microsoft Virtual Academy videos. Then, I connected using Remote Desktop. I double-clicked somewhere in the black. The target computer started playing an MVA video: I could hear the video's sound through the target computer's speakers. When I logged in via the console, I saw the video player was on screen.
