Nick

Hi! Unfortunately, the issue described here initially, has resurfaced! A very recent Windows Update (not sure how to provide details about Windows Updates) has messed with the order of the boot loaders and I am yet again having to enter BIOS on each boot to push Vera Crypt Boot loader back to the top of the list. Using latest VeraCrypt 1.24-Update7

OH THANK YOU THANK YOU FOR THIS FIX FINALLY!!! Release Notes: "Fix issue related to Windows Update breaking VeraCrypt UEFI bootloader." Just upgraded to 1.24 and I am happy! I have waited so long for this! No longer must I enter UEFI-BIOS each and every time I boot my computer in order to place VeraCrypt BootLoader before Windows BootLoader. The only workaround for this was to completely decrypt and re-encrypt system partition after each major Windows Update that messed with the Boot Loader order....

Hi Mounir, yet again after a Windows Update, I am faced with the problem described in the first post above. This time I tried your cmd command but unfortunately it had no effect. It seems I must decrypt and re-encrypt my system drive again and possibly after each future Windows Update. Is this a problem related to my specific Mainboard's UEFI? \Nick

Hi Mounir, thank you for personally helping out with my issue and for your great work with VeraCrypt. Unluckily, I had already proceeded with decrypting and re-encrypting my system drive, as badger suggested above, which fixed my issue. I wish I had known this cli command just a few hours ealier, haha! Therefore, I am unable to confirm if the command would have fixed it, which ofcourse would have been the much simpler solution. Thans again anyway! \Nick

Hi Mounir, thank you for personally helping out with my issue and for your great work with VeraCrypt. Unluckily, I had already proceeded with decrypting and re-encrypting my system drive, as badger suggested above, which fixed my issue. I wish I'd know that cli command just a few hours ealier, haha! Therefore, I am unable to confirm if the command would have fixed it, which ofcourse would have been the much simpler solution. Thans again anyway! \Nick

Thanks! Actually, I had waited several VeraCrypt versions before upgrading to 1.23, when I finally read in the release notes, that it now supports Windows 10 Major Updates: 1.23 Release Notes: "Add compatibility of system encryption with Windows 10 upgrade using ReflectDrivers mechanism" ...doesn't seem like it. :( Oh well, I will follow your advice, badger, and decrypt and re-encrypt my system drive to solve my above mentioned problem. Hope it works...

Badger, have you been having this problem since the most recent Windows Update?

Hi! (VeraCrypt 1.23, Win 10 Pro, i7-3770, ASRock Z77 Extreme4-M) Since the recent Windows Update, I am having the same problem with VeraCrypt that I had a couple years ago: When booting my computer, the VeraCrypt PW Promt does not appear, instead Windows tries to boot and gets stuck in "automatic repair". When I enter BIOS, I find that "Windows boot manager" is listed before "VeraCrypt boot loader". I then move VeraCrypt before Windows, Save&Exit BIOS and then am asked for VeraCrypt PW and after...