1.19 Rescue Disk Bug

EDITED for 1.20 Release.

If you are currently using VeraCrypt 1.19 version for system encryption, upgrade and recreate your Rescue Disk using VeraCrypt 1.20 or higher version.

https://sourceforge.net/projects/veracrypt/files/

The 1.19 bug does not correctly decrypt the first 50 MB which is why the partition will not be visible by any data recovery tool since all filesystem information is located in the first 50 MB.

If you are currently decrypting your system encryption using the 1.19 version Rescue Disk, after the decryption completes, you need to use the repair utility at the post below.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/11717ff8/#891f/2964/d007/b951/b81a

Please, I need help.
I updated my HP from 1.19 to 1.20-beta2 to recreate a rescue disc without a bug.
But now I get the message, thats the file is not found

With (the OLD) rescue stick, I can enter these option, but it differs from the explanations I can find.
(I dont know why it says beta3, I installed beta2)

Please put it in layman's terms.

And is it an option to wipe the partition and install windows again (absolute emergency option)?

1. Was 1.19 a new install or upgrade from an older version of VeraCrypt?
2. When you originally encrypted your HP system partition, did you have to perform the procedures in the link below to get your HP system to work with EFI and VeraCrypt?

https://sourceforge.net/p/veracrypt/discussion/technical/thread/f403d1d8/

Thanks for the answer
1) It was a new installation
2) no, I tried but at first it failed at step six and on a second try, i always got "wrong parameter" at step 1 "mountvol o: /s"

I have an older laptop, the bootloader looks very different and as I know it from truecrypt. Is the layout from the picture above a result from the wrong startup sequence which should be fixed with the link?

I am not sure what is happening with your system and your answers are unclear to me.

You originally installed 1.19, then encrypted your system partition without having to perform any manual steps per the link I provided and the system encryption worked successfully. Correct?

The link I provided as an example of the manual steps some people had to perform when using UEFI on certain models. It was not suggested that you perform these steps.

You say that you have an older laptop. Are you using UEFI or MBR booting?

Currently you have upgraded to 1.20 Beta 2. Are you able to boot into Windows successfully either with or without the Rescue Disk?

Sorry, I try to be clearer:
I installed 1.19 a while, did a system encryption. It worked, even though I was confused that while booting it only says "Enter Password:" and not the usual layout.
Since it is an HP and I read that they often jump into automatic repair, I tried the solution here
https://sourceforge.net/p/veracrypt/discussion/technical/thread/f403d1d8/#0bfd
It failed, but since I did not have the problem yet, I decided to try it again later.
Then I read this thread here, upgraded to 1.20-beta2 (with the target to create a new rescue disc), at the end of the upgrade I was asked to reboot, what I did. And this is where I got stuck.
I still only have the rescue disc from 1.19

The older laptop uses UEFI (just like the current one)

Do you concur with the following sequence of events?

1) Installed 1.19 version.
2) You encrypted the system partition/drive successfully and you did not manually perform any changes to the bootloader configuration.
3) Your read about HP boot repair loop from the link in your post above and you performed steps 1 - 5 successfully.

1 Hit windows key, type “cmd”, right click command prompt and select “Run as Administrator”
2 Type: “mountvol o: /s” and hit enter
3 Type: “ren o:\EFI\Microsoft\Boot\bootmgfw.efi bootmgfw_ms.efi” and hit enter
4 Type: “notepad o:\EFI\VeraCrypt\DcsProp” and hit enter
5 A notepad window should have appeared. Enter the following text to the top of the list:
“<config key="ActionSuccess">postexec file(EFI\Microsoft\Boot\bootmgfw_ms.efi)</config>”
It should look like:
<tag>
<config key="ActionSuccess">stuff</config>
<config key="blah">stuff</config>
<config key="blahblah">stuff</config>
<config key="ActionBlah">stuff</config>
</tag>
The "ActionSuccess" config key needs to be at the top. Make sure it is placed within the other tags. Keep the quotes around “ActionSuccess” but not around the whole line (remember what I said at the beginning). Location of text here is important.
Use “ctrl + s” to save and X out of notepad

4) Tried to perform step 6 “cd EFI” and hit enter which failed.
5) Days, weeks or months later, you tried the apply the same steps from the link unsuccessfully starting at step 2 "mountvol o: /s".
6) Today, you upgraded to 1.20 Beta 2 and now you are unable to boot into Windows.
7) You still have your 1.19 Rescue Disk.

If you are unable to boot into Windows, how did you manage to create the 1.20 beta 2 Rescue Disk since the reboot after the software upgrade occurs first?

If the above sequence is correct, hopefully someone can suggest the best course of action to undo the partial implementation that you performed in manually changing the bootloader configuration by using your 1.19 Rescue Disk.

Sorry, I am not sure how to resolve this issue.

PS: Did you create the 1.19 Rescue Disk before manually altering the bootloader configuration?

Yep thats it.

If you are unable to boot into Windows, how did you manage to create the 1.20 beta 2 Rescue Disk since the reboot after the software upgrade occurs first?

I don't have a 1.20 beta 2 rescue disc, before I could create it, I got stuck

Yes, I created the 1.19 rescue before altering anything

Is this thread still monitored? I have some issues & questions regarding the boot disk:
https://sourceforge.net/p/veracrypt/discussion/technical/thread/11717ff8/#891f/2964/d007/b951/b81a/2c8c

https://sourceforge.net/p/veracrypt/discussion/technical/thread/11717ff8/#891f/2500

Thank you

Simple question over rescue disk !
After create it on my hard disc
Do i have to extract it to USB disc as is
or i need to make ISO bootable file of it ?

thanks i understand it now :)

The Trend Micro Rescue Disk is a free tool that lets in you to use a CD, DVD, or USB pressure to examine your laptop barring launching Microsoft Windows. It finds and gets rid of continual or difficult-to-clean safety threats that can lurk deep within your running system.