I managed to get VeraCrypt running on my Acer ES 15; I'm just curious if there's any better way....
I managed to get it running (to boot) by using solution from other thread - overwriting windows' efi file by veracrypt's efi file.
I've also tried to copy veracrypt's efi file into folder which should be predefined by my bios (according to some other forum post this should be e.g. efi/android/bootx64.efi or efi/Linux/BOOTX64.efi) however bios still won't detect this boot option (with secured boot disabled; acer removed option of "trusting" other sources from this version of bios...). I'm surprised that overwriting windows efi file works while creating "predefined" folder in EFI partition still wont force bios to notice new boot option - or is there any way to "force reload" boot options?
Anyone have more "elegant" solutions? Are there any vulnerabilities in a system running witch replaced windows' efi file (and then redirected to original windows efi file...)
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey,
I managed to get VeraCrypt running on my Acer ES 15; I'm just curious if there's any better way....
I managed to get it running (to boot) by using solution from other thread - overwriting windows' efi file by veracrypt's efi file.
I've also tried to copy veracrypt's efi file into folder which should be predefined by my bios (according to some other forum post this should be e.g. efi/android/bootx64.efi or efi/Linux/BOOTX64.efi) however bios still won't detect this boot option (with secured boot disabled; acer removed option of "trusting" other sources from this version of bios...). I'm surprised that overwriting windows efi file works while creating "predefined" folder in EFI partition still wont force bios to notice new boot option - or is there any way to "force reload" boot options?
Anyone have more "elegant" solutions? Are there any vulnerabilities in a system running witch replaced windows' efi file (and then redirected to original windows efi file...)
Thanks.
the problem is option of your ACER firmware. (it differs from EFI boot loader spec)
You can try DcsProp key DcsBmlDriver=1 (it lock boot menu to veracrypt)
or you can add dcsint.dcs to driver list via EFI shell "bcfg driver add" command
note: the experiment is not safe. it can lock your boot disk. to restore: remove disk, enter bios, reset bios