I got a new HP 250 in October, and immediately encrypted the whole drive (v1.23), and it has worked fine ever since. However, today, Windows 10 did an update, and on reboot, it failed, going into the automatic repair, which itself failed. I tried a bunch of things to fix it, none of which worked, but finally decided to decrypt the drive, and then start again. So I was expecting that after decryption, it would still not reboot until I'd done a reinstallation, or whatever, of Windows. However, much to my surprise, once the decryption had finished, the computer started up perfectly without anything further needing to be done. This implies to me that there is some incompatibility between the latest Win10 update and Veracrypt. Is that correct?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And the same thing has just happened on my other Win10 computer, a Dell. Again, I needed the veracrypt recovery disk (v1.21) to get it working again. Other people musthave had a similar problem, which, presumably, relates the the current Win10 update.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As it seems that recent Windows updates are changing the bootloader. You need to rename the original bootmgfw.efi to bootmgfw_ms.efi and change the DcsProp file in VeraCrypt folder on EFI partition. You should be able to fix this by running for example a USB Linux Live distro.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got a new HP 250 in October, and immediately encrypted the whole drive (v1.23), and it has worked fine ever since. However, today, Windows 10 did an update, and on reboot, it failed, going into the automatic repair, which itself failed. I tried a bunch of things to fix it, none of which worked, but finally decided to decrypt the drive, and then start again. So I was expecting that after decryption, it would still not reboot until I'd done a reinstallation, or whatever, of Windows. However, much to my surprise, once the decryption had finished, the computer started up perfectly without anything further needing to be done. This implies to me that there is some incompatibility between the latest Win10 update and Veracrypt. Is that correct?
And the same thing has just happened on my other Win10 computer, a Dell. Again, I needed the veracrypt recovery disk (v1.21) to get it working again. Other people musthave had a similar problem, which, presumably, relates the the current Win10 update.
Everybody coming with problems booting encrypted Windows system partition after Windows Update, please take a look at this post: https://sourceforge.net/p/veracrypt/discussion/technical/thread/5b859040/#34c2/a892
As it seems that recent Windows updates are changing the bootloader. You need to rename the original bootmgfw.efi to bootmgfw_ms.efi and change the DcsProp file in VeraCrypt folder on EFI partition. You should be able to fix this by running for example a USB Linux Live distro.