asked on
Remote Desktop Freezes after a few seconds
Hello. Whenever I connect to remote server through Remote Desktop Connection, it connects but after a few seconds it freezes. I have tried connecting to it on two different computers but the same thing happens. I can connect to other remote computers but this specific one has this problem. What's odd is that I can connect to it through an Android phone app called RD Client, but just not through Remote Desktop Connection.
I have tried disabling the audio and printers in the Local Resources tab, lowered the resolution and changed the connection settings (I have a 50mbps connection so that shouldn't be an issue), but nothing has worked so far. Any help will be greatly appreciated!
Both my server and my local computer uses Windows 10 x64.
I have tried disabling the audio and printers in the Local Resources tab, lowered the resolution and changed the connection settings (I have a 50mbps connection so that shouldn't be an issue), but nothing has worked so far. Any help will be greatly appreciated!
Both my server and my local computer uses Windows 10 x64.
Windows 10Remote Access
Last Comment
McKnife
ASKER
Hello McKnife. I have tested it from 3 different machines. My own laptop that didn't manage to stay connected after initial connection. Then 2 more machines (A and B) didn't manage to stay connected to the target (machine C) either.
I must clarify that I have updated to the latest version of Windows on my Laptop and the target (machine C), after which this problem has started. I can connect to ANY other machine using RDP on all these computers (my own laptop, machine A and machine B). The only problem I'm getting is when connecting to the machine C.
I must clarify that I have updated to the latest version of Windows on my Laptop and the target (machine C), after which this problem has started. I can connect to ANY other machine using RDP on all these computers (my own laptop, machine A and machine B). The only problem I'm getting is when connecting to the machine C.
Well, either something is broken on C (speaking of windows' internals) or you have some software on C that is simply malfunctioning/interfering
I would try and do an inplace upgrade to 1607 (like you already did) again in order to repair it.
I would try and do an inplace upgrade to 1607 (like you already did) again in order to repair it.
ASKER
Thank you for your answer. I do think so that might be the case, since I restarted the target machine when it was taking a long time to update (I didn't realize it was still updating).
I must clarify that I do not have direct access to the target machine. The only way I can access it is through RDP. Will I still be able to do an in-place upgrade?
I must clarify that I do not have direct access to the target machine. The only way I can access it is through RDP. Will I still be able to do an in-place upgrade?
Sure, you will. I upgraded many machines using RDP. Even Bitlocker (if enabled) will be automatically suspended. The machine will of course reach a point when it has to reboot and then, depending on the speed and size of your installation, it might take up to an hour until you can reconnect to it. If it is still an hdd, it might take even longer.
ASKER
Alright, that sounds wonderful! I'll give it a shot. Thanks a lot!
ASKER
Well, even after that it's still the same. It's freezing after a few seconds of connection.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hello. All the drivers are up to date and there are no 3rd party anti virus or firewall softwares installed. I have double checked it but still there's no progress towards the solution.
It is very rare that I have to surrender, but this time, I would. Do you have a backup/image of a working state?
ASKER
I checked the device manager and there was some sort of "sensor" device that had no drivers. I deleted that and now it's working fine. Thanks for all the help!
ASKER
I checked the device manager and there was some sort of "sensor" device that had no drivers. I deleted that and now it's working fine. Thanks for all the help!
You deleted it and on next reboot, it didn't get re-detected? That would be strange. Please do a reboot and report the behavior to me.
ASKER
I did a reboot just now and it didn't detect that device. I am able to use RDP as normal now though after I deleted it. If I knew it'd fix the error, I'd have taken a screenshot of it.
:-) What a killer device...
ASKER
Haha indeed. Well at least my issue is resolved. Thanks a lot for all the help. I didn't have to reinstall the Windows and start from the beginning. You are a life saver. I appreciate the help!
Very welcome. I see strange issues like this very often. Everyday a new big laugh. Or big outcry :-|
I use RDP win10->win10 very frequently. Never ever froze.
Please retry with clean machines or from A to B this time.
Most probably it's some weird effect that is due to 3rd party software or driver problems.