VeraCrypt Bug with system encryption (automatic windows repair)

[Dominik]

I am running Windows 11 Pro, Version 10.0.26200 (Build 26200).

I am using VeraCrypt 1.26.24.

I used VeraCrypt to encrypt my system partition. Everything works fine so far, but every few days I encounter a problem when booting my PC: instead of loading the VeraCrypt bootloader, Windows Automatic Repair starts.

The automatic repair fails, and I then have to manually select the boot device to boot normally again.

Does anyone have an idea what could cause this? Is this a known bug or possibly a configuration issue?

It also shows me a Logfile called srttrail.txt, but after booting into windows, it is gone, guess it is only available in the recovery-system

[Mounir IDRASSI]

This is typical behavior when VeraCrypt EFI loader is being bypassed, so Windows Boot Manager/Recovery starts directly and then can't read the encrypted system partition.

The fact that selecting the boot device manually lets the system boot normally is important: it indicates that the VeraCrypt loader and the encrypted Windows installation are still OK.

Please try the following from the normally booted Windows session, using an Administrator command prompt:

"C:\Program Files\VeraCrypt\VeraCrypt.exe" /PostOOBE

Then open VeraCrypt > System > Settings and check the EFI boot options. Please make sure “Automatically fix boot configuration issues that may prevent Windows from starting”, “Force the presence of VeraCrypt entry in the EFI firmware boot menu”, and “Force VeraCrypt entry to be the first in the EFI firmware boot menu” are enabled.

If the problem continues, also try enabling “Force machine to boot on VeraCrypt in the next startup”.

[Dominik]

Thank you!

I already solved the problem, I just selected veracrypt bootloader as first option in UEFI - don't know why it sometimes worked and sometimes not, but that seemed so solved the issue