Error codes
You can find errors in the AIS logs located in %ProgramData%\ESET\ESET Full Disk Encryption\AIS\:
Error code |
Error code message |
Troubleshooting |
|---|---|---|
536871024 |
Failed to copy the EFI loader to the ESP |
The EFI System Partition (ESP) on your system is full. By default, Windows allocates only 100 MB to this partition. We recommend increasing the size of ESP by at least 50 MB. |
3225157640 3225157649 |
A TPM command failed The required Persistant Handle is not stored in the TPM |
If TPM usage is desired: 1.Install all pending Windows updates. 2.Ensure the BIOS/Firmware is up to date. If neither option is successful, modify the EFDE policy to disable the requirement for TPM-based encryption—disable the Use TPM option within the encryption policy. |
3221291021 |
A required bootloader file could not be created |
Third-party software such as antivirus programs, rollback utilities, or encryption tools may be interfering with the creation of the test file C:\pre-flight.bin, or with the subsequent renaming of this file to C:\dlploadr.bin. Review any installed software that may be actively monitoring, restricting, or blocking file creation or modification in the root of the C: drive, and consider temporarily disabling or configuring exceptions as needed. |
3225223188 |
DLP_ERROR_OPAL_NOT_AUTHORISED |
If OPAL usage is desired: 1.Check the BIOS settings for options such as Block SID Authentication or similar that may prevent TCG OPAL authentication. 2.If the first point fails, perform a PSID revert on the OPAL drive (back up all important data beforehand as this will erase the drive) and reinstall Windows, see the instruction in the Knowledgebase article. If neither option is successful, modify the EFDE policy to remove the requirement for OPAL-based encryption—disable the Use OPAL option within the encryption policy settings. |
After troubleshooting, you need to Retry failed encryption. You can initiate the EFDE Safe Start process by three methods:
•In ESET PROTECT, click the computer > View Details > Alerts > click the Encryption failed to start and select Retry failed encryption.
•In ESET PROTECT, click Configuration > Advanced setup and change the policy’s Settings:
1.Remove the current EFDE policy.
2.Add a new EFDE policy with the disabled Enable Encryption option.
3.Wait for processing at the EFDE client to reset the Safe Start state.
4.Remove the EFDE policy with the disabled Enable Encryption option.
5.Add the desired EFDE policy.
6.Uninstall and reinstall the EFDE client app.
If you continue encountering issues, submit a support ticket using the log.