RDP stuck at configuring remote session

whatever61

Distinguished
Jul 29, 2010
242
0
18,690
RDP stuck at configuring remote session from time to time.

After I restart my PC, it starts working again.

I am using the default Remote desktop (mstsc) and also a Remote Desktop Manager and it' same problem on both of them.

When this happens I can't connect to any RDP (tested on 5 different one's).

Any ideas?

Thanks
 
I am having the same issue with some of my users and it is driving me absolutely crazy! I have no idea why this happens and am trying to find patterns with no luck. Nothing online has any information pertaining to this except for doing some things then eventually rebooting which is exactly what I don't want to do (reboot). Can someone please give us a good answer to this issue? Thanks
 
This is happening to Windows 7 Enterprise edition machines. They cannot remote into Windows Servers sand other Windows 7 machines until a reboot happens. What is funny is that before the reboot happens, the host machines are pingable and can be reached by other machines just not by this one.
 
I am not sure what you mean. I am not stating a different issue here. I even said that I am having the same exact problem as the thread starter which is:

"RDP stuck at configuring remote session from time to time.

After I restart my PC, it starts working again.

I am using the default Remote desktop (mstsc) and also a Remote Desktop Manager and it' same problem on both of them.

When this happens I can't connect to any RDP (tested on 5 different one's).

Any ideas?"
 
You may have the same exact problem but since this thread has been started by whatever61, you're considered to be hijacking it for a solution, either open a thread of your own detailing your system specs and your issue and wait for a user to respond or perhaps wait and see if OP of this thread has found a solution.

If you have any more queries please PM me.
 
I was referring to the updates that Microsoft pushes every Tuesday :). Regardless it's a good thing your issue has resolved though a solution can't be offered to those who may be on the same boat as you.

Here's hoping that the issue has been resolved at Microsoft's end and is later trickled down to the end user 😉