![]() ![]() The only fix I have found is a reboot.Įdit: Also, the elevation prompt (consent.exe) will not appear on the local session when attempting to run something that needs elevation. In other words, Ctrl+Alt+Del is ignored and does nothing, and any other method of locking the session also does nothing. In addition, after this occurs, unlocking the Windows session locally (using the physically attached keyboard/mouse/display) works fine, but then once unlocked, I cannot re-lock the session. It may be associated with a loss of network connection and a reconnection attempt by the RDP client. Restarting Terminal Services does not fix it. Once this happens, it will never resolve itself. ![]() Every so often it gets into a state where client RDP connections hang after successful (NLA) authentication and just show the "Please Wait" with the indefinite looping dots UI forever. I always have a single logged in session and never logout (only disconnect). I have a Windows 10 Pro machine running Terminal Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |