The latest VeraCrypt Final/Beta seems to have some troubles with latest Windows changes, which means the pretest fails. This test is needed to verify if your HDD/SSD can be proper encrypted before the actual process really starts to avoid running into problems.


The guide is a workaround however this needs to be fixed within VeraCrypt with the next final version.

The Problem

Once you installed VeraCrypt Final / Nightly you might want to start the full disk-encryption (FDE) to encrypt the whole OS partition/drive, you start the setup and do everything what you get asked for - The system shutdowns , yep no reboot! - it shutdown, bad signal already! Okay so you power on your machine and you won’t see any input field to type in your password, Windows just boots or you see a error which says that the authentification failed. Well, you just boot into Windows but nothing got encrypted and you see the error (see picture above). That’s bad and it sucks!


    1. Copy the file: EFI\Microsoft\Boot\bootmgfw.efi to bootmgfw_ms.efi
    2. Copy and replace EFI\VeraCrypt\DcsBoot.efi to EFI\Microsoft\Boot\bootmgfw.efi
    3. Edit EFI\VeraCrypt\DcsProp and put the key within the configuration: <config key="ActionSuccess">postexec file(EFI\Microsoft\Boot\bootmgfw_ms.efi)</config>
    4. After the reboot you finally can enter your password and VeraCrypt finally says that the pretest is okay.

I took me one day to figure it out. The issue is already reported on GitHub with similar or exactly the same symptoms.

I hope this gets fixed because as of right now no version - no matter FInal or Beta- seems to have a solution for this.

Stay secure friends! 🕵🏻