Page History
Created date | Updated date | Affects version | Fix version |
---|---|---|---|
|
| Drive Eraser - All versions | N/A |
Problem
Booting Blancco Drive Eraser fails due to a Secure Boot with a message "Secure Boot – Selected boot image did not authenticate” or “No valid digital signature found, booting stopped by Secure Boot”.
...
For certain devices it may be enough to restore the Secure Boot keys to factory state/reset all Secure Boot keys to platform defaults through the BIOS/UEFI settings.
Resolution
Long term fix to mitigate this change will be implemented in a future Blancco Drive Eraser release. Once implemented booting Secure Boot enabled devices will be supported.
There is a limited availability release available based on Drive Eraser 7.6.0 where this issue is fixed. Contact Blancco Technical Support for more details.
Info |
---|
February 2023 Introduced a limited availability variant of Drive Eraser 7.6.0 which includes a fix to the Secure Boot issue. Contact Blancco Technical Support for more details. |
Info |
---|
Update November 2022 - January 2023 Blancco has added some updates on the SHIM and on the application, the Linux community has asked a couple of questions, but still ”in-progress”. |
Info |
---|
Update November 2022 Blancco submits a new SHIM (as well as an official application) to be signed by Microsoft. This SHIM has to be reviewed by the Linux community first, then by Microsoft. If everything is OK, Microsoft signs the SHIM and Blancco can add it into Blancco Drive Eraser. This procedure is not in the hands of Blancco and there is no clear ETA on when the Linux community will review the SHIM or when Microsoft will approve it. |
Info |
---|
Update October 2022 Blancco Development team starts building a new SHIM (binary that is signed by both Microsoft and Blancco, re-enabling the Secure Boot process). |