The update could have altered your UEFI, and not allowed the update to reboot properly, so it fails install and falls back to the backup, the prior version.
I have 6 Win10 Home PCs I personally manage with Veracrypt 1.24.7, and know an additional 10 self managed by the owners. My 6 had 20H2 from last year, but are now are on 21H2. They are all system encrypted.
They are 4 Acer desktops, and 2 Acer laptops. All use mechanical HD.
All updates are automatic, that is forced by Microsoft, we do not voluntarily install any recent updates, this insures all known bugs or issues with the updates are resolved. The oldest PC is a laptop from 2016, that I also use for testing new versions of Veracrypt. All installs have been flawless and automatic, 'turnkey' easy, for many years.
The biggest problem I encountered was somewhere in the update cycle for 20H1 or 20H2, was a optional update for firmware drivers, including UEFI updates for all the PCs. Over the years, there were reports of security issues with chipsets etc., that were patched, and the firmware updates were the permanent solution.
All my UEFI firmware are admin password protected to prevent changes. During the Windows update, and unknown to me at the time, rather than half the update and ask for the password, Windows update overwrote the UEFI firmware, and forced all settings to factory default, and erased my UEFI passwords. This changed the boot settings, TPM settings and turned off hardware AES, among many others. When the systems rebooted, the PCs went into a repair loop and VC would not boot. During the troubleshooting, I checked the UEFI and noted the changes; I set UEFI back to the proper settings, the VC boot manager was still there just it was not set as the primary boot.
All has been well since.
Good luck!
Last edit: Robert iXj Smith 2022-03-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anyone else who can't update Windows 10 to version 20H2 with system encryption?
Tried updating VeraCrypt but it just restarts after I write password then starts the old version of Windows again.
What version of VeraCrypt are you using on your PC?
Windows Home edition or Pro edition?
I am curious why you are not updating to 21H2 or is that a typo?
Updating VeraCrypt software will not update the Windows OS to a newer version.
The update could have altered your UEFI, and not allowed the update to reboot properly, so it fails install and falls back to the backup, the prior version.
I have 6 Win10 Home PCs I personally manage with Veracrypt 1.24.7, and know an additional 10 self managed by the owners. My 6 had 20H2 from last year, but are now are on 21H2. They are all system encrypted.
They are 4 Acer desktops, and 2 Acer laptops. All use mechanical HD.
All updates are automatic, that is forced by Microsoft, we do not voluntarily install any recent updates, this insures all known bugs or issues with the updates are resolved. The oldest PC is a laptop from 2016, that I also use for testing new versions of Veracrypt. All installs have been flawless and automatic, 'turnkey' easy, for many years.
The biggest problem I encountered was somewhere in the update cycle for 20H1 or 20H2, was a optional update for firmware drivers, including UEFI updates for all the PCs. Over the years, there were reports of security issues with chipsets etc., that were patched, and the firmware updates were the permanent solution.
All my UEFI firmware are admin password protected to prevent changes. During the Windows update, and unknown to me at the time, rather than half the update and ask for the password, Windows update overwrote the UEFI firmware, and forced all settings to factory default, and erased my UEFI passwords. This changed the boot settings, TPM settings and turned off hardware AES, among many others. When the systems rebooted, the PCs went into a repair loop and VC would not boot. During the troubleshooting, I checked the UEFI and noted the changes; I set UEFI back to the proper settings, the VC boot manager was still there just it was not set as the primary boot.
All has been well since.
Good luck!
Last edit: Robert iXj Smith 2022-03-20