41

I have four machines running Windows 10 Pro, all upgraded from Windows 8.1. I use mstsc to remote between them. When I do this several things commonly go wrong.


The first workflow

1a) On first connection attempt it shows the remote machine login screen, but it freezes. You have to disconnect, it never unfreezes.

1b) You reconnect and get a message saying "The Remote desktop services is currently busy". You have to disconnect.

1c) After trying to reconnect and getting the same message you eventually get granted access and it will start working correctly.


The second workflow goes:

2a) On first connection attempt it freezes showing the login screen. Forcing you to disconnect.

2b) You reconnect and this time it gets as far as the desktop, but it is still frozen and you have to disconnect.

2c) The third time you reconnect everything appears to work fine.

Which machine I use doesn't affect success rate.

Any ideas?

  • 2
    not an answer, but I found all certificates had to be re-accepted [non-corporate environment, so no 'real' certs] & that I had to reset the firewall for RDC on all machines. These were upgrades from WIn 7, so might be a different symptom to a similar issue. – Tetsujin Aug 7 '15 at 15:39
  • 10
    It looks like a Windows 10 bug that needs to be fixed by Microsoft. I'm having exactly the same issue (with a machine upgraded from 8.1). I'm connecting with a Mac Remote Desktop client. It only seems to happen after some time (overnight). Remote logins initiated immediately after a successful one work fine. – Dan Aug 9 '15 at 8:05
  • 7
    This issue has been logged with Microsoft through the Windows Feedback app. If you're experiencing this problem, please upvote the issue in Windows Feedback (category Networks, followed by Remote Desktop Connection). Hopefully they'll notice and fix it. – Robbietjuh Aug 12 '15 at 12:57
  • 3
    @Ian If you add "The Remote desktop services is currently busy" to the title of this question it will attract more people with this problem. I guess this is the keyword for this issue. At least I have used it to find this question. – Dan Aug 12 '15 at 20:49
  • 2
    Exact same issue — On only one of my machines, the rest work fine... I found that logging in as a different user seems to kick it into working when stuck in your first workflow. – Aaron Aug 17 '15 at 19:21
4

After applying the Windows 10 November Update (Version 1511), this appears to have fixed the issue for me.

| improve this answer | |
  • 1
    Thanks. I was a bit astonished by the fact that an answer from August was reporting a November update as fixing the issue... time machine? ... later I realised that you edited the answer recently. – sorin Dec 3 '15 at 11:49
  • 1
    This did not solve the problem for Windows 10 Enterprise. All updates installed, issue remains. – FizxMike Jul 6 '16 at 14:43
0

I don't have Windows 10, but what about a VNC application like TeamViewer as mentioned above or for a little more control of you stuff try UltraVNC or RealVNC

| improve this answer | |
-1

Try and wait ~1 to 5 min or something, if that does not work try installing an ssh server so that you can ssh into the box and restart the Remote Desktop service

Solution 1

Solution 2

  1. install CopSSH on server https://www.itefix.net/content/copssh-free-edition

  2. connect with putty or xshell

  3. restart remote desktop with

    sc stop UmRdpService
    
    sc stop TermService
    
    sc start UmRdpService   
    
    sc start TermService
    
| improve this answer | |
  • 1
    These are not solutions they are workarounds using different technology? – leinad13 Oct 19 '15 at 15:54
  • i found waiting and trying to multiplier reconnections work – nwgat Oct 20 '15 at 18:28
  • there is a solution but I cannot answer here, because bwDraco has protected this thread – Perino Nov 5 '15 at 7:28
  • @Perino can you link to the solution here or let me know somehow please? – leinad13 Nov 12 '15 at 16:44
  • 1
    i believe the windows 10 fall update fixes the issue – nwgat Nov 12 '15 at 17:06
-1

I had a similar issue happen to me. Mine was due to a 3rd party firewall solution that was borking my remote RDP sessions even through the firewall vendor swore it was innocent.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.