You reboot or logoff your ThinDesktop session, hold down and press the Shift key but ThinDesktop ignores the key sequence. Instead of returning you to the Secure Attention Sequence (SAS) where you can provide a user name and password, ThinDesktop logs back in and starts of the ThinDesktop shell.
This behavior is not by design. Microsoft has confirmed the issue as a bug in kbdhid.sys. Microsoft development is aware of the issue and is working on a resolution. Given win32k.sys is also affected, it is expected the fix will take several months before a hotfix is available.
Note: The issue is not related to any defect in ThinDesktop. Microsoft will need to fix the issue in their keyboard device driver.
To work around the issue:
1. Be sure to hold down the Shift key before choosing to log off or restart the system. Alternatively, you can try pressing the Shift key multiple times. If that does not work, hold down the left shift key, while holding down, press the right shift key, release left, and repair (left->right, right->left) in a see-saw pattern.
2. From a WinRM or remote command prompt (i.e. psexec session) issue td.cmd.exe -off from the ThinDesktop program files directory.
Sysinternals PsExec can be downloaded from http://live.sysinternals.com.
Example command line:
psexec \\server "c:\program files\thinlaunch\thindesktop\tdcmd.exe" -off
psexec \\server "c:\program files (x86)\thinlaunch\thindesktop\tdcmd.exe" -off
Note: To return autologin issue the "-on" command instead of "-off" and restart the workstation.
3. If remote registry is enabled set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon from AutoAdminLogon to REG_SZ "0". To return box to auto-login state run tdcmd.exe from the ThinDesktop directory or set ThinDesktop to "on" in Builder.
Note: You may need to turn ThinDesktop off in Builder and back on then restart the system.
4. A "admin hotfix" is under development as another work around for Windows 10 systems by ThinLaunch Software and should be released by Q1 2017. Please check this KB article for an update.