Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, February 3, 2019 10:53 AM | 2 votes
I log into my office computer (W10 Pro) via RDP over the VPN whenever I'm working at our branch offices. Since I updated it to 1809 last week it's been barely usable over RDP - regular freezes, which sometimes resolve themselves after 10 or 20 seconds, and sometimes require disconnecting and reconnecting the RDP session. It never did this before the 1809 update.
Has anyone else experienced this?
David
All replies (18)
Sunday, February 3, 2019 12:53 PM
It could be a bug. Have you installed the updates?
You can try following tips if it helps your situation.
Wednesday, February 6, 2019 7:47 AM
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Otto Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, February 6, 2019 9:47 AM
I had done a check for updates before posting, but I did another one (didn't notice whether it installed anything), and since then it's been a lot better - does occasionally freeze still, but nowhere near as often as it was doing.
David
Monday, February 11, 2019 1:54 AM
Hi,
Thanks for your reply.
What the version of computer did you use to connect to this windows 10 by RDP?
Can it work fine on other computers by RDP?
Looking forward to your reply.
Thanks for your understanding and support.
Best Regards,
Otto
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, February 11, 2019 6:59 PM
I've connected from various machines, including W10 1809, Server 2016 and Server 2012 R2 - all show the same issue, although it's now happening less than it was to start with.
David
Wednesday, February 13, 2019 1:57 AM
Hi,
Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Otto
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, February 25, 2019 8:40 AM
Not sure why my previous post has been 'proposed as answer' - I've not see an answer yet!
David
Friday, March 22, 2019 1:14 PM
Went into the same trouble immediately after applying Update 1809. Running a packet capture for troubleshooting I can conclude that at freezing time (cannot tell exactly, that moment being only estimated) no packets are lost and so I think the issue is not triggered by a communication error. Moreover, I can't recall a freezing occurring whilst moving the mouse cursor or typing, however I can't conclude that it never happens during screen buffer updating.
Cosmin
Monday, March 25, 2019 8:54 PM
Did anyone figure out this issue? Has there been a fix by Microsoft for this yet?
Monday, March 25, 2019 8:59 PM
Still not got to the bottom of it. It's now less frequent than it was, and I can go for several days without it happening - but then it happens again repeatedly in a short time.
Incidentally, does anyone know whether it also happens in the current preview of the April 19 release of W10?
David
Wednesday, April 3, 2019 11:57 AM | 1 vote
Did anyone figure out this issue? Has there been a fix by Microsoft for this yet?
I am having the same RDP freezing problems. And it is starting to drive me nuts. Appreciate working solution please. Desperately.
Small local area network with Windows 10 Professional all running version 1809. And all updated the latest drivers et cetera. Now that was a dumb thing to do was it not?
Thursday, July 11, 2019 3:28 PM
It's still happening with the 1903 cumulative update. Please reply back if you've found any solutions for this issue. Thanks.
Friday, July 12, 2019 6:48 AM
I've been having a similar issue for several months.
I was using a multi-monitor setup with Display Port on all monitors, using a Radeon R7 250 with the legacy drivers.
As I have read about issues with Graphics cards causing RDP freezes, I have replaced this card with a new Radeon RX570 and right now have not been able to reproduce the RDP error. It looks like it's related to the legacy driver and/or the card.
I was always able to 'force' the RDP freeze by looking at Google maps then moving the map - this seemed to cause a big enough screen refresh to trigger the issue.
I will update if the issue returns.
Friday, July 12, 2019 1:49 PM
In our case, the computers are just using onboard Intel graphics.
Does still seem to be doing it under 1903.
David
Thursday, July 18, 2019 10:07 AM
I am having this same problem. It is bit annoying since the RDP can freeze multiple time in just one hour which means that I need to close RDP session and open it again to continue.
Friday, August 2, 2019 5:34 PM
This worked for me:
On the system where you are running Remote Desktop Client:
run gpedit
Navigate to Computer configuration\Admin Templates\ Windows Components\Remote Desktop Services\Remote Desktop Connection Client
Right-click "Turn Off UDP On Client" and select "Edit", then click "Enabled" on the left, and apply the change.
Tuesday, August 6, 2019 6:19 AM
Hello, Any progress on this matter?
I updated 4 of my virtual windows 10 guests to 1903 the other week, unknowing of this problem, and now I can´t connect with RDP. If I do the guest will use 100% CPU, get unresponsive, and a hard reboot seems to be the only way to get control of the machine again.
If I use WMvare-consol, it´s all work well, but I need to use the RDP-consol.
I tried Jeff Walsh solution regarding turning off UDP in gpedit, but it didn’t help me.
I also wonder how several of the posts here is marked as solutions?
/Best regards Lennart
Tuesday, August 6, 2019 7:21 AM
Hold up, i may found a solution, fingers crossed.
I missed that Jeff Walsh solution is to edit on the client side, I tested it on the host.
But I found this post:
Remote-desktop-broken-windows-10-1903
Where you edit the host instead and in that way everyone that has to be able to connect can now du so.
I have tested it on 2 of my machines, and so far it´s promising.
/Best regards Lennart