Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Win10 rel 1803, VeraCrypt 1.23-BETA1 always fails pretest #323
After updating to Windows 10 Pro April 2018 Version 1803, VeraCrypt no longer works. All was fine before the Windows update. Old version was 1709.
** WHAT I DID **
I decrypted the C: drive, (system drive on my system)
VeraCrypt does it stuff, but the pretest fails
** NEXT STEPS **
Boot using the ver 1803 ISO downloaded from Microsoft.
In the command prompt (still in Windows recovery)
format V: /fs:fat32
At this point, in theory, I have a pristine boot loader.
** MORE TRYING **
I tried 1.23-BETA1
Still stuck in the Post-reboot loop regardless of boot device options or boot order. Can only exit the loop by reformatting the V: drive and reinstalling via bcdboot.
** Other info
msinfo32 Bios mode = UEFI
I can confirm that VeraCrypt v. 1.21 (64-bit) on Windows 10 (64-bit) Build 1709 is blocking the MS Windows "functional update" (Windows 10 Pro April 2018 Version 1803).
After a lot of different tries (there where only serveral hints that a corrupt driver could be the problem) I found the soloution here:
It says that when using "a non Microsoft disk encryption method/tool" the update could lead to problems.
I don't know if this is a VeraCrypt or Microsoft issue but I took me a lot of time and it was a very hard process to find exact information for that strange behavior.
Please take a look at that! Thanks!
@blu-IT : Thank you for sharing your experience. Indeed, VeraCryption version before 1.23-BETA1 didn't implement a Windows specific mechanism (called ReflectDrivers) that became mandatory for major upgrades like 1803. This was implemented starting from 1.23-BETA1 and upgrades like 1803 have been confirmed to work without the need of decryption. @MCS000: Can you please try with the latest 1.23-BETA4 build available at https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/? I'm not quiet sure about the cause of your issue but there was a workaround implemented for some special cases and it is possible that this may fix the issue.
I had problems with booting Windows after latest Windows update (KB4487017).
VeraCrypt v. 1.23 (64-bit) & Windows 10 Pro 64-bit (1803)
There are still cases where Windows Update can break the bootloader but it is never necessary to decrypt the system in order to recover. Often, Windows can be booted by manually selecting VeraCrypt DCS in boot menu of the motherboard BIOS or by using the BIOS function to manually boot from the file "EFI\VeraCrypt\DcsBoot.efi".
In all cases, a combination of Rescue Disc usage and manual fix of EFI system partition content restores the system to its normal state.
That being said, and after studying the issues reported with 1.23, I have developed a new mechanism to ensure that VeraCrypt will always fix the boot partition if Windows Update corrupts its content and I have also made the Rescue Disk EFI repair mode more clever in handling such cases.
The latest 1.24-Beta2 includes these enhancements and it can downloaded from https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/.
Moreover, I have developed a tool called VcFixBoot that can be used to fix the EFI bootloader but it requires the user to be able to boot Windows manually as I described at the beginning of this post. This tool can be found at https://sourceforge.net/projects/veracrypt/files/Contributions/
yes, I had to go that way: Boot Windows by manually selecting VeraCrypt DCS in boot menu, but every time until the boot record/menu was fixed. To do that I booted, decrypted my system partition and encrypted again.
I hope that with 1.24 the auto fix ease things :-)
referenced this issue
Feb 15, 2019
Just to complement that topic: