When you create a Remote Desktop Protocol (RDP) connection to a computer that is running Windows Server 2012, the computer freezes.
This issue occurs because of a deadlock condition that involves terminal services (termsrv.dll), lsass (kerberos), and redirector. The deadlock occurs when terminal services tries to load the user configuration data by issuing remote registry calls to the domain controller.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To fix this issue in WIndows Server 2012, you have to upgrade to Windows Server 2012 R2. Then, create the fQueryUserConfigFromLocalMachine registry entry. To make the registry change, follow these steps:
- Start Registry Editor. (Press Windows logo key + R, type regedit.exe in the Open box, and then click OK.)
- In Registry Editor, locate and then click one of the following registry subkeys:
- HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\<Connection Name>
Note By default, the value for <Connection Name> is RDP-Tcp. This value RDP-Tcp can be renamed or configured to something else.
- On the Edit menu, select New, and then select DWORD Value.
- Type fQueryUserConfigFromLocalMachine.
- Press and hold (or right-click) fQueryUserConfigFromLocalMachine, and then select Modify.
- In the Value data box, type 1, and then select OK.
- Exit Registry Editor.
You can also upgrade to Windows Server 2016 to fix this issue.
Note You do not have to update registry keys in Windows Server 2016.
Article ID: 4021856 - Last Review: 2017, മേയ് 14 - Revision: 12