Hi after I install and run Seagate Discwizard to clone a non encrypted data disc to a bigger one I was forced to a reboot. But now my encrypted system disk hold on boot whit mbr error 1 & 3. I read the normaly solution to fix this issue for non encrypted system is Bootrec.exe /FixMbr and Bootrec.exe /FixBoot but the question is can i fix it like that on a full encrypted vera volume?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Seagate software damaged the VeraCrypt bootloader. This is something that happens with some software that do nasty things behind the scene without the consent of the user.
That's why the VeraCrypt Rescue Disk is very important: it is your only way to make your system boot in such situation and you can also use it to restore the damaged VeraCrypt bootloader.
In your case, boot on the rescue disk (or a USB bootable key created from the ISO file) and then press F8 to show the repair options and select "Restore VeraCrypt Boot Loader".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2014-12-30
Thank you for your advice, but the rescue cd image it's on the encrypted system drive 😭 blame on me. So it's possible to mount the system drive to a other pc whit veracrypt installed? or its possible to repair the mbr whit a fresh created rescue cd from a other pc whit veracrypt?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can't repair the bootloader using another Rescue Disk: each Rescue Disk is unique to the system it was created for. This is part of the security of the system encryption with VeraCrypt.
You can loader the encrypted partition in another PC provided that only the bootloader was damaged and not the system encryption header.
Just select it using the "Select Device" button, then go to menu "Volumes -> Mount Volume with Options" : in the displayed dialog check "Mount partition using system encryption without pre-boot authentication", click OK and enter your password.
This works as long as the system encryption header was not also damaged. If it doesn't work, I afraid there is nothing you can do to recover it as only the Rescue Disk holds the backup system header.
The maximum security offered by system encryption requires a recovery policy through the secure storage of the Rescue Disk in case of damage. Obviously, the password is also very important to remember because it is needed even for the Rescue Disk.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2015-01-02
@Idrassi
Thank you again and a happy new year. The solution to mount the system drive at a other computer works, so i can recover my rescue cd iso and restore successful the veracrypt bootloader. Windows boot up and crash repeatedly shortly after the animated win7 bootlogo whit a bluescreen but now i can boot to the win7 system recovery options so I'm not sure what's the next safe step. Should I use the win7 start up repair to fix the bluescreen or should I first permanently decrypt the system drive and restore the original bootloader and then try to fix the win boot bs whit the win recovery start up repair? Thanks in advance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you start Windows in safe mode (F8)? If it works, you can try uninstalling Seagate Discwizard and see if the BSOD disappears.
Since you already have the rescue disk, you can perform the windows system recovery. There is no risk and even if the recovery damage the bootlaoder, you can always restore it.
Happy new year to you, with my best wishes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2015-01-02
Thank you so much for all you effort. I was a bit scared and do a permanently decrypt, after that win boots up flawless (nothing to fix), deinstall the f*** Discwizard, update Veracrypt to final F version and now i encrypt the system again. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi after I install and run Seagate Discwizard to clone a non encrypted data disc to a bigger one I was forced to a reboot. But now my encrypted system disk hold on boot whit mbr error 1 & 3. I read the normaly solution to fix this issue for non encrypted system is Bootrec.exe /FixMbr and Bootrec.exe /FixBoot but the question is can i fix it like that on a full encrypted vera volume?
The Seagate software damaged the VeraCrypt bootloader. This is something that happens with some software that do nasty things behind the scene without the consent of the user.
That's why the VeraCrypt Rescue Disk is very important: it is your only way to make your system boot in such situation and you can also use it to restore the damaged VeraCrypt bootloader.
Please read the documentation chapter about the rescue disk : https://veracrypt.codeplex.com/wikipage?title=VeraCrypt%20Rescue%20Disk
There is also a chapter talking about an equivalent issue that happens with products using Products Using FLEXnet Publisher/SafeCast : https://veracrypt.codeplex.com/wikipage?title=Incompatibilities
In your case, boot on the rescue disk (or a USB bootable key created from the ISO file) and then press F8 to show the repair options and select "Restore VeraCrypt Boot Loader".
Thank you for your advice, but the rescue cd image it's on the encrypted system drive 😭 blame on me. So it's possible to mount the system drive to a other pc whit veracrypt installed? or its possible to repair the mbr whit a fresh created rescue cd from a other pc whit veracrypt?
You can't repair the bootloader using another Rescue Disk: each Rescue Disk is unique to the system it was created for. This is part of the security of the system encryption with VeraCrypt.
You can loader the encrypted partition in another PC provided that only the bootloader was damaged and not the system encryption header.
Just select it using the "Select Device" button, then go to menu "Volumes -> Mount Volume with Options" : in the displayed dialog check "Mount partition using system encryption without pre-boot authentication", click OK and enter your password.
This works as long as the system encryption header was not also damaged. If it doesn't work, I afraid there is nothing you can do to recover it as only the Rescue Disk holds the backup system header.
The maximum security offered by system encryption requires a recovery policy through the secure storage of the Rescue Disk in case of damage. Obviously, the password is also very important to remember because it is needed even for the Rescue Disk.
@Idrassi
Thank you again and a happy new year. The solution to mount the system drive at a other computer works, so i can recover my rescue cd iso and restore successful the veracrypt bootloader. Windows boot up and crash repeatedly shortly after the animated win7 bootlogo whit a bluescreen but now i can boot to the win7 system recovery options so I'm not sure what's the next safe step. Should I use the win7 start up repair to fix the bluescreen or should I first permanently decrypt the system drive and restore the original bootloader and then try to fix the win boot bs whit the win recovery start up repair? Thanks in advance
Can you start Windows in safe mode (F8)? If it works, you can try uninstalling Seagate Discwizard and see if the BSOD disappears.
Since you already have the rescue disk, you can perform the windows system recovery. There is no risk and even if the recovery damage the bootlaoder, you can always restore it.
Happy new year to you, with my best wishes.
Thank you so much for all you effort. I was a bit scared and do a permanently decrypt, after that win boots up flawless (nothing to fix), deinstall the f*** Discwizard, update Veracrypt to final F version and now i encrypt the system again. :)
I managed to solve this problem, please look at this other thread:
https://sourceforge.net/p/veracrypt/discussion/technical/thread/2fbcacd0/