Fix device stuck in Temp AutoBoot
How to resolve problem of device stuck in temp autoboot
Occasionally, after installing SecureDoc the SecureMoment is not achieved automatically, and there is no prompt for ownership. Usually this happens when Owner Identification Rules of the Provisioning Rules section of the Installation package settings is set to “Automatically identify owner …”, but the automatic identification process fails. The workaround for this is to force the device to prompt for ownership. This is done by opening the registry, going to HKLM\Software\WinMagic, and changing “SecureMomentType” to 2. Reboot the machine, it will continue to by in temp autoboot and go straight to Windows. Log in as the user, and they will now get the ownership prompt. Reboot again, and they will get the Boot logon.
If SecureMomentType is already 2, but the device is still in temp autoboot, and the local SDCC will not open, download the attached checksds zip file, and extract it onto the device having problems. Open an elevated command prompt, navigate to the appropriate architecture folder (98% of devices will use 64-bit version), and then run CheckSds --modifyAttr=1287. This will return “4”. Run CheckSds --modifyAttr=1287 --modifyValue=1, which will return the device to temp autoboot. Reboot the device and login to Windows to achieve the secure moment, and then reboot the machine. If this was successful, you will now get the boot logon.
To verify that everything is ok, open an elevated command prompt and run CheckSds --modifyAttr=1287 again, and will probably return a value of “1”. (If it returns a value of “4”, then the next step is not required.) Run CheckSds --modifyAttr=1287 --modfiyValue=4