I have an EFI system running on an acer model laptop (Windows 10). Has anything changed since version 1.18 in terms of the issue with the boot loader on EFI System?
I have installed veracrypt version 1.21 on my system. during the pretest I get the statment - secure boot loader failed - and veracrypt asked me to try it again or cancel it.
Have you figured out a proper workaround which doesn't require much of IT knowledge? Or is the option only I have left to change my system to legacy mode and turn my disk from gpt to mbr?
Last edit: Des646L 2017-12-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Secure Boot:
In order to allow VeraCrypt EFI bootloader to run when EFI Secure Boot is enabled, VeraCrypt EFI bootloader files are signed by custom key(DCS_sign) whose public part can be loaded into Secure Boot to allow verification of VeraCrypt EFI files.
to update Secure Boot configuration steps:
1. Enter BIOS configuration
2. Switch Secure boot to setup mode (or custom mode). It deletes PK (platform certificate) and allows to load DCS platform key.
3. Boot Windows
4. execute from admin command prompt
powershell -ExecutionPolicy Bypass -File sb_set_siglists.ps1
It sets in PK (platform key) - DCS_platform
It sets in KEK (key exchange key) - DCS_key_exchange
It sets in db - DCS_sign MicWinProPCA2011_2011-10-19 MicCorUEFCA2011_2011-06-27
All DCS modules are protected by DCS_sign.
All Windows modules are protected by MicWinProPCA2011_2011-10-19
All SHIM(linux) modules are protected by MicCorUEFCA2011_2011-06-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have an EFI system running on an acer model laptop (Windows 10). Has anything changed since version 1.18 in terms of the issue with the boot loader on EFI System?
I have installed veracrypt version 1.21 on my system. during the pretest I get the statment - secure boot loader failed - and veracrypt asked me to try it again or cancel it.
Have you figured out a proper workaround which doesn't require much of IT knowledge? Or is the option only I have left to change my system to legacy mode and turn my disk from gpt to mbr?
Last edit: Des646L 2017-12-08
Probably you can setup custom secure boot or disable the option in BIOS. .
https://sourceforge.net/p/veracrypt/code/ci/master/tree/src/Boot/EFI/
Secure Boot:
In order to allow VeraCrypt EFI bootloader to run when EFI Secure Boot is enabled, VeraCrypt EFI bootloader files are signed by custom key(DCS_sign) whose public part can be loaded into Secure Boot to allow verification of VeraCrypt EFI files.
to update Secure Boot configuration steps:
1. Enter BIOS configuration
2. Switch Secure boot to setup mode (or custom mode). It deletes PK (platform certificate) and allows to load DCS platform key.
3. Boot Windows
4. execute from admin command prompt
powershell -ExecutionPolicy Bypass -File sb_set_siglists.ps1
It sets in PK (platform key) - DCS_platform
It sets in KEK (key exchange key) - DCS_key_exchange
It sets in db - DCS_sign MicWinProPCA2011_2011-10-19 MicCorUEFCA2011_2011-06-27
All DCS modules are protected by DCS_sign.
All Windows modules are protected by MicWinProPCA2011_2011-10-19
All SHIM(linux) modules are protected by MicCorUEFCA2011_2011-06-27