Update from Versio 1.23-H2 to V 1.24-U7 - Password is okay - but it don't boot

[Sauter]

Hello

I have updated my HP ZBook (Windows 10 20H2) from VeraCrypt version 1.23-H2 to 1.24-U7.
So far everything has worked fine.

The update process went smoothly.

After the reboot I was able to enter the password and PIM without any problems.

However, after that the system did not boot, but got stuck.
Picture:
"Enter Password: *
PIM (Leave empty for default): ***
Authorizing ...
Success
Start 0 512753664 len 275457769472
-

Can anyone give me some hints?

Thanks a lot!

PS: Due to the failure of the main system I am technically somewhat limited at the moment. I do have a backup, but I have a lot set up on the system for research data. Therefore it would be very good if I could boot again.

[Sauter]

Hi

The solution is not there yet ... We have the last 2 days much read here in the forum and elsewhere. We are technik afin, but we are in a different field of research.

We have on this EDP system the operating system and the data fortunately in different partitions. For such a case, this is worth a lot.

We created a live Windows system and were able to boot from that USB stick. This allowed us to access our data volumes.
But we did not manage to access the operating system volume, where there is also data.

Before updating from V 1.23 hotfix2 to VeraCrypt version 1.24 update 7, we put the Rescue Disk 1.23 aside. The update process was successful according to the VeraCrypt message. Also otherwise this system was without problems for years. During the update we created a current Rescue Disk 1.24 u7. This was created in the download folder of C and then backed up to a new encrypted USB stick. Unfortunately, we can no longer open this stick (may have been unplugged too quickly when removed or formatted when re-inserted). However, we believe that the Rescue Disk 1.24 is still in the download folder. However, we do not have access to it yet.

Questions:
- Is it possible to open the partition/volume saved with the preboot password from a Windows live system? We tried it with password + PIM, but it did not work.

• Can we customize the boot file differently?
  We have the correct password yes. But with the Rescue Disk 1.23 it does not work. It comes when booting from stick the message wrong password etc. ...

We would be very grateful for any help. Perhaps it is quite simple, Mounir has written in another thread "Don't panic". We do not, but we do not want to destroy something else with own poking around.

[Gary Marks]

Questions:
- Is it possible to open the partition/volume saved with the preboot password from a Windows live system? We tried it with password + PIM, but it did not work.

First click the button in the lower right corner marked "Mount Options..." and make sure to check the box marked "Mount partition using system encryption without pre-boot authentication." Then click OK and enter the password + PIM in the previous dialog. You're certainly not the first to overlook this critical detail. Cheers.

[Sauter]

@Gary
Hi, your cheers went through the team round, the system partition was open quickly, thanks a lot and a cheers back.

Problem and the questions:
Instead of the Rescue Disk 1.24, we found our screenshot of the installation end and then immediately remembered:
"VeraCrypt Setup.
The VeraCrypt bootloader has been successfully updated.
It is strongly recommended to create a new rescue disk (which contains the latest version of the VeraCrypt bootloader) by clicking on "System" > "Create rescue disk ..." after restarting the computer."

Now this is also the weakness after the update. If something goes wrong, you can not work with a current rescue disk, because none exists yet. But if the first boot doesn't work because something is missing or incorrect in the boot DCS, then a rescue disk of that wouldn't help either.

If you read through the forum, you will also find other same update problems:
- https://sourceforge.net/p/veracrypt/discussion/technical/thread/5dfa2f0f88/
- https://sourceforge.net/p/veracrypt/discussion/technical/thread/8e1a0860ab/
- https://sourceforge.net/p/veracrypt/discussion/technical/thread/0d85f21b25/

Should we now decrypt the system partition and then do a clean install with V 1.24 U7?
- Does the decryption with V 1.23 H2 work at all after the update to V 1.24 U7?
https://sourceforge.net/p/veracrypt/discussion/general/thread/f1db70da87/
- And does a clean install work then?
https://sourceforge.net/p/veracrypt/discussion/general/thread/310d8cb577/

Mounir wrote on 2019-12-13:
I confirm that since version 1.24, VeraCrypt automatically fixes boot problems after Windows is started. Also, in some cases, just shutting down the machine after the update reboot the PC solved the boot issue.
so, there is no need anymore for manually fixing the boot.

Robert confirmed this - 2019-12-13:
... This morning my laptop didn't boot after a Windows Update yesterday. Same problem as discussed here before. But now the problem is somehow solved by itself!

I doublechecked this with my college (same laptop). He updated Windows, rebooted and got stuck too (Windows Automatic Repair started). He switched off his laptop (just power off with the button) and started with F9 (to manually select the VeraCrypt EFI file). From here, we are not absolutely certain if we booted into Windows or not, but both of us are certain we have not fixed the issue like we normally do (copy \EFI\VeraCrypt\DcsBoot.efi over Microsoft's one or use VcFixBoot64.exe) and on both laptops it works fine again now...

... and petitlou60 - 2021-01-19:
Help for creating better script for loading VeraCrypt SecureBoot keys:
hello,
please not that alll this topic is now obsolete
last version of veracrypt bootloader is now certified by microsoft , so secure boot can remain enable and no need of installation of any key inside UEFI

So how to proceed? Did we overlooked an actual solution in the forum?

Thanks for Help!