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
Tuesday, August 11, 2015 5:29 AM | 11 votes
i have 2 windows 10 installations, and found the remote desktop connections much less smooth than before.
1. when it's win 10 TP, I met with several remote desktop connections stop serving, hanging on login screen, and then (had to) exit.
2. after win10 rtm, sometimes I got remote desktop connected, I can see the remote windows there, living , but just couldn't click anything or input anything. I had to exit, and login again, would showing remote desktop service (terminal service) busy, or everything got fine.
All replies (28)
Tuesday, August 11, 2015 8:32 PM | 3 votes
Yes I am experiencing the exact same problems outlined here. Have you found any resolution as yet?
Wednesday, August 12, 2015 12:34 PM | 1 vote
Hi,
I have tested on my clean installed Windows 10 and there is no such issue.
Firstly, this issue can be caused by 3rd part security applications (especially Trend OfficeScan) or incompatible software, please first test this issue in clean boot mode:
How to perform a clean boot
http://support.microsoft.com/kb/929135
If the issue doesn’t appear, you can determine which one can be the cause by using dichotomy in MSconfig. Checking on half of Non-Microsoft service and restart, determining which half of the services cause the issue and repeating to check half of the problematic half services.
If the issue still persists in clean boot, try following suggestions:
1. Make sure your computer is up to date.
2. Disable TCP/IP auto-tuning by entering in Command Prompt that is Run as Administrator:
netsh interface tcp set global autotuning=disabled
3. In the RDP Options, Experience tab, adjust the Performances settings.
Note: Export the old settings of this key as backup.
Turn off Scalable Networking Pack with this registry hack :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
EnableTCPChimney=dword:00000000
EnableTCPA=dword:00000000
EnableRSS=dword:00000000
Post back if you need further support.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, August 13, 2015 11:48 AM | 2 votes
I am also experiencing this problem with the RTM of Windows 10 Pro. I did a clean install and even still, when I RDP in, it will show a black screen or freeze on logon. I will have to wait a minute and reconnect, then it will login, but still be frozen. The mouse cursor still moves and the screen isn't black, but I am unable to click anything. On the 3rd connect, everything works properly.
Sunday, August 16, 2015 10:12 AM | 2 votes
I am also experiencing this problem with the RTM of Windows 10 Pro. I did a clean install and even still, when I RDP in, it will show a black screen or freeze on logon. I will have to wait a minute and reconnect, then it will login, but still be frozen. The mouse cursor still moves and the screen isn't black, but I am unable to click anything. On the 3rd connect, everything works properly.
seems the latest updates fixed a bit? i mean less that frequently.
however, sometimes still need 4 times connection, 1. black, 2. service busy, 3. live, frozen, 4. fine!
the 2 installation were both upgraded from windows 10 tech preview, and one even from win 8.1.
Tuesday, August 18, 2015 2:35 PM | 2 votes
I am also experiencing this problem with the RTM of Windows 10 Pro. I did a clean install and even still, when I RDP in, it will show a black screen or freeze on logon. I will have to wait a minute and reconnect, then it will login, but still be frozen. The mouse cursor still moves and the screen isn't black, but I am unable to click anything. On the 3rd connect, everything works properly.
seems the latest updates fixed a bit? i mean less that frequently.
however, sometimes still need 4 times connection, 1. black, 2. service busy, 3. live, frozen, 4. fine!
the 2 installation were both upgraded from windows 10 tech preview, and one even from win 8.1.
It has definitely gotten less frequent, but still occurs. I have also noticed though that if I let it sit for a minute after connecting the first time, it will connect and the black screen will go away and it won't be frozen. While it's annoying to have to wait, it's better than disconnecting and reconnecting a number of times more.
Tuesday, August 18, 2015 5:21 PM | 3 votes
I have this exact same issue on one of my machines.
It seem to be related to how long ago I logged in via RDP before. If I have recently logged in to the machine (via RDP), there is no problem. But if I haven't been connected/logged in for ~1 hour, I will almost always get a black screen when connecting...
If tryng to reconnect, I get a message that the RDP service is busy. After a few minutes I can connect, but often I can't click on anything. After logging out and in again everything finally works...
My maching does not go inte sleep or anything, and I have disabled power-saving features on the NIC, etc.
When the RDP is "busy", I can ping the machine, but I can't ping or access a virtual machine running in VMWare on it (connected via a bridged network).
It does not matter from where I try to login - I get the black screen also from an RDP-client on my iPhone when the machine has not been accessed in a while.
Sunday, August 30, 2015 6:35 PM | 1 vote
Same here, it seems to mostly affect my virtual machines running on ESXi.
This happens when the VM has been idle for a long time.
I can see that the CPU of the machine is going very high for the time that the login is 'waiting'
Just wondering if this may be due to the 'memory compression' features of Windows 10, but these VM's are not at all starved for memory.
[EDIT] Can also see some disk READ access at that time, and vmware 'active memory' going way up.
Saturday, October 3, 2015 12:57 PM | 1 vote
I have the same problems. After the third reconnect it works. Newest updates installed.
Friday, October 9, 2015 9:03 PM | 1 vote
Accurate description of the sequence I am also experiencing. Once in a while, it connects on the second go around. But so far, never on the first attempt.
Both systems were 8.1pro - and worked very reliably, before being upgraded to 10.0 pro.
MS - please take note and fix this annoying problem.
Tuesday, October 13, 2015 1:58 PM | 1 vote
Same error in my ESXi environment, still in october no update yet that fix this annoying problem, I'm considering to rollback to windows 7...
Friday, October 23, 2015 5:14 AM | 1 vote
hey,guys, now with windows 10 build 10565, the matter seems gone, how about yours.
Tuesday, October 27, 2015 11:45 AM | 1 vote
hey,guys, now with windows 10 build 10565, the matter seems gone, how about yours.
I really hope you are right! I just installed 10565 here and will check...
For me this problem has been 100 % repeatable, so I'll probably see in a day or so if the problem is indeed fixed in 10565. I'll get back...
Thursday, October 29, 2015 6:28 AM | 1 vote
This problem is definitely better in build 10565.
Sometimes it still takes an unreasonable time (10-15 seconds over a LAN) to connect again a few hours after the last disconnect from an RPD-session, but it's far better now (it used to take several minutes before able to connect)
Tuesday, December 8, 2015 9:15 AM | 1 vote
Unfortunately, the problem still persists. Seems to have gotten better with the latest W10 build but it still takes up to about a minute to log on to a ESXi W10 VM.
On the same ESXi, W7 is lightning fast...
Sunday, December 27, 2015 7:58 PM
Im getting the exact same problem even on the latest build. It takes 3 attempts to log in. I get it on a fresh install with no other apps installed and it affects both my laptop and desktop PCs. Running the latest updates also but the issue persists.
Wednesday, January 20, 2016 12:05 PM
Here same issue with windows 10 on vmware.
Slow logon and logon-screen is freezing. After a minute the login will exceed...
Is there already a solution of workarround yet?
Thursday, January 28, 2016 12:14 AM
I have the same problem as well.
I use remote desktop for most of my work, and with windows 8.1 this never happened.
The screen is constantly freezing even after successfully connecting, and the connection blacks out and reconnects every 5 minutes.
This is so frustrating that I am considering deleting my windows 10 and going back to 8.1
Monday, February 15, 2016 8:01 PM
I have also been having this problem on every Windows 10 machine, whether virtual or physical. it is always the same thing, though it doesn't always happen. When it happens I can get a frozen screen, a black screen or a screen where applications won't open. If I close the session and try again 5 minutes later it works fine. this is on 4 Windows 10 Pro physical machines and 2 Windows 10 Pro VMs. These same machines worked fine on Windows 7 or 8.1 prior to upgrading to Windows 10. The RDP client can initiate the session from Windows 10 or 8.1 with the same results. It is clearly the destination client not the initiating client.
Tuesday, March 22, 2016 5:13 AM
I have the exact same issue here.
Saturday, March 26, 2016 2:59 PM
Me too, same issue as described by all these folks. Consistent and repeatable, glad it's not just me.
Tuesday, March 29, 2016 3:49 PM
Same here, using an RDP gateway to connect to computers on the network, no issues with other computers on the network only Windows 10 machines.
Tuesday, August 9, 2016 11:48 PM
I have a Dell Latitude E5450 running Windows 10. I ran into this problem as soon as I installed the Dell Data Protection Drivers that permitted fingerprint authentication. RDP client worked properly before then.
I tried all the items previously cited with no success. Finally I found a couple of articles on bypassing RDP authentication which actually did the trick for me.
What I did was create a Default.rdp file using the RD Client and, without actually connecting, set up the connection. I then saved the result to %homepath%. Using notepad, I then opened the file and removed the lines containing:
"full address:s:<my remote server>"
and
"gatewayhostname:s:<my remote server>"
I then changed the line:
"authentication level:i:2" to "authentication level:i:0"
and added the following line at the end:
"enablecredsspsupport:i:0"
Then saved the file out.
I then opened the Remote Desktop Connection icon and modified the target to read:
"%windir%\system32\mstsc.exe "%homepath%\Default.rdp""
and my remote desktop connection finally worked to any of my servers with the credentials contained in the Default.rdp file.
Friday, August 19, 2016 12:30 AM
I have a Dell Latitude E5450 running Windows 10. I ran into this problem as soon as I installed the Dell Data Protection Drivers that permitted fingerprint authentication. RDP client worked properly before then.
I tried all the items previously cited with no success. Finally I found a couple of articles on bypassing RDP authentication which actually did the trick for me.
What I did was create a Default.rdp file using the RD Client and, without actually connecting, set up the connection. I then saved the result to %homepath%. Using notepad, I then opened the file and removed the lines containing:
"full address:s:<my remote server>"
and
"gatewayhostname:s:<my remote server>"
I then changed the line:
"authentication level:i:2" to "authentication level:i:0"
and added the following line at the end:
"enablecredsspsupport:i:0"
Then saved the file out.
I then opened the Remote Desktop Connection icon and modified the target to read:
"%windir%\system32\mstsc.exe "%homepath%\Default.rdp""
and my remote desktop connection finally worked to any of my servers with the credentials contained in the Default.rdp file.
After I change "authentication level:i:2" to "authentication level:i:0", I get the following error message:
The remote computer requires that authentication be enabled to connect. The connection cannot proceed because authentication is not enabled...
Wednesday, December 28, 2016 10:36 PM | 1 vote
I don't experience any particular delays, but in general, the performance of remote desktop is worse than horrible compared to previous versions of Windows. In Windows XP the performance was excellent, to a degree where while working with regular desktop applications (no video, no large graphics), you did not see much difference between working on remote computer vs local. In Windows 7 it already became somewhat worse, but still acceptable. In Windows 10 it slowed down probably 20 times.
Saturday, June 10, 2017 7:14 PM | 1 vote
After upgrading to the newest build version 1703 (build 15063). The problem is still there. I try everything I can think of and Widows support suggested, nothing helps. It is repeatable. Sometimes, after I you type two letters, the first start to show up. It is bothersome when you drag windows. Even worse, some lag sensitive device does not work anymore. I can never get my Blomberg BUnit to sync through a RDP window. I have never have such issue with my old notebook running Windows 7 pro. Microsoft ask for $149 for additional help. So far, I feel it is a microsoft bug as it shows up in a clean boot. My machine is brand new and actually not too much third party software. I even remove my antivirus software before the clean boot. Here is my original post.
Thursday, June 15, 2017 9:20 PM | 2 votes
RDP in Microsoft windows 10 is completely trash. I gave up and decide to connect my notebook to monitor through a docking station. I feel better to pay $280 to get a new docking station rather than being robbed of $149 by Microsoft. Once a great company, now, it is more and more like an Indian $10 notebook, cheap and broker but more and more profit oriented.
Tuesday, November 14, 2017 8:30 PM
" there is no such issue." You're are not helpful.
Wednesday, November 22, 2017 12:08 PM
I got same issue with RPD of win 10. Does anyone have solutions to solve?