Home / server / Questions / 640211
In Process
ya23
Asked: 2014-10-29 02:44:54 +0800 CST

mstsc freezes after entering credentials

  • 772

At some point in Windows session (usually days) I can no longer make RDP connections. When running mstsc and entering credentials, all buttons are getting disabled and the UI freezes. Existing sessions are unaffected, restart solves the problem.

I found advice to clear terminal services cache and disable sound in remote session. Have tried, it didn't help. Event log is empty.

Any suggestions how to fix it please?

Edit: OS is Windows 2008R2x64, SP1 and fully updated. Mstsc version is 6.3.9600. Issue doesn't seem to be specific to the target machine (fails for all I've tried - Win7x64, Win8.1 and Win2008r2).

windows-server-2008-r2

4 Answers

  1. ya23, Could you try unticking the smartcard option in mstsc (Local Resources > Local devices and resources > more > unticking 'Smart Cards') and retry.

    I have this problem on my 2008 Sp1 rds server mstsc connecting to other servers. Once it happens once, I don't seem to be able to connect to any other servers via mstsc until I reboot. However it comes back after a few days.

    You enter credentials for the remote server and then press enter, then the pointer goes to an hourglass and the buttons on the connection dialog are greyed out - but instead of opening an mstsc sesssion it just sits there. Nothing ever happens - from 1 hour +. This doesn't happen with my 2003 TS Jump server.

    Nothing in the event logs at all!

    But removing the Smartcard option seemed to fix it for me today. Not sure if temporary though. Give the suggestion a try and let us know.

    • 2

  2. Very similar situation for me, only no RDP connections could be made ever. I couldn't even cancel the Windows Security dialog without it hanging. I checked my RDP local resources to make sure smart cards were unchecked, but it still hung. I fixed it by disabling the Realtek USB 3.0 Card Reader device. The drivers are from 2019-06-21, so maybe a recent Windows update is bad.

    • 1

  3. I had the same issue but on Windows 8.1. Somebody in one of these forums made the comment that they used Remote Desktop Connection Manager instead of the standard Remote Desktop Connection mstsc.exe just out of preference, but they did not mention that as a solution.

    I installed it from MS and then started playing around with it. I also had the device manager open and was experimenting with disabling the Smart Card Reader(s) and the Realtek Audio as that had been mentioned as well. I noticed that each time I would disable one of the items while trying to connect using the manager, it would then work. Kind of like the disabling would "trigger" the connection. After some experimentation, I realized that I could leave everything enabled, and the connection using Remote Desktop Manager would eventually work. Disabling the drivers only sped up the initialization of the connection. But, the standard client mstsc.exe still does not work even with all drivers disabled.

    So, my "workaround" is to now use the Remote Desktop Connection Manager as my default client and abandon mstsc.exe

    • 0

  4. I experienced the above exactly - I had a finger print scanner/biometric multifactor authentication attached via USB (comes up as smart card in the remote desktop connections). After removing the biometric usb device Remote Desktop Connection worked again as expected.

    • 0