Issue:
Encryption did not start after reboot\shutdown
SDJob.log log file located in directdory C:\Program Files\WinMagic\Securedoc-nt shows a message: Invalid Key 0xa105
Product version affected:
Any
Environment (OS/hardware/software):
Windows 7, 8, 10
Bitlocker activation or Software Encryption can be affected equally
Scenario:
1) Administrator would kick off the installation via SCCM ,3rd party deployment ,script or manual installation
2) SCCM logic or Administrator or System would reboot (WinMagic has not initiated its own reboot)
3) Once Windows loads, encryption does not start. Referring to the SDJob.log log file shows it contains a message: Invalid Key ID 0xa105
Analysis:
Upon reviewing SDJob.log (located in C:\Program Files\WinMagic\Securedoc-nt), it is possible to see that an elapsed time of approximately 4 minutes between the completion of the "Generating Random Number" stage to the point of attempting to start the Encryption process.
NOTE: If the device in question encounters a random or a scheduled reboot during this critical time, the message Invalid Key 0xa105 will occur.
Generate random number 2015/10/07 09:50 Start...
Generate random number 2015/10/07 09:50 Finish
Encrypt with thorough mode 2015/10/07 09:54 Start...
Encrypt with thorough mode 2015/10/07 09:54 Invalid Key ID (0xa105)
Looking at Windows system event logs for EventID 6006 and 6005 we can confirm reboot did take place.
Solution/Workaround:
It is first essential to understand why the device is being rebooted at this point of the installation process.
Customers encountering this issue should ask:
Is it part of your installation script ?
Is it part of your Securedoc profile/Installation package configuration ?
Was the reboot triggered by some other software, or by Windows update ?
Are any registry values being monitored that might force a reboot?
If the source of the unanticipated reboot is determined, if necessary contact WinMagic Support for guidance on making any additional procedural changes to ensure smooth installation and initial encryption will result.
1511 Conversion Did not Start After Restart/Shutdown Resulting in Error Message, (Invalid Key 0xa105)
- Updated on Feb 11, 2026
- 1 minute(s) read
- VN
Was this article helpful?