Activity for Brian
-
Brian posted a comment on discussion Technical Topics
I see many other posts with related, thogh not the exact same, issue. It looks like veracrypt can not extract the backup volume header from the end of the drive. There is no option to do so in the software that I can see. Others have been directed to use winhex or dcs-disk cryptography services. But all the forum posts related to these appear to have failed in getting them to work. Any expert walkthroughs or step by step guides out there to pull the backup header from the last 256 bytes of a boot...
-
I tired with the volume dismounted, select the volume in the main GUI. Click on Volume Tools button and select the Restore Volume Header and then select "Restore the volume header from the backup embedded in the volume" option. The error message I get is: Operation failed due to one or more of the following: incorrect password, incorrect volume pim number, incorrect prf, not a valid volume. Source: RestoreVolumeHeader: 10858 The disk was full disk encrypted. There are 3 partitions. P1 is some hp...
-
A windows 10 update wiped the MBR. The boot/only drive will not boot, saying to use an emergency disk to restore. Usually not a problem, not the first time Windows has done this. Emergency disk is in another country. Problem. I was able to mount the partition on another machine by using the veracrypt app on another windows machine: select device mount mount options: use backup header embedded in volume if available, mount partition using system encryption without pre-boot authentication. But is there...
-
HP EliteBook 840. Bios has been locked for years. Not possible to change the bios to enable secure boot, or disable it. It was a corp machine, and HP doesn't allow unlocking of any sort for these machines anymore. There's only some archaic process involving jumper wires and breadboards, and this machine is not worth that trouble. I've installed, removed, and updated veracrypt many times over the years without boot loader issues.
-
Wait, time? Is there some counter or self destuct that will trigger if the boot loader doesn't match the installed version?
-
1.24 update6 coming from 1.24 update 4. Installer on Windows 10 1909 18363.719 says: "Access is denied. Source: VeraCrypt:File::Write::967 Failed to upgrade the VeraCrypt Boot Loader. Failed to Upgrade VeraCrypt! ...blahblah... you should try installing the original or the new version of VeraCrypt again before you shut down or restart the system." The system reboots fine using the old boot loader, and windows starts. Veracrypt on each reboot complains that the boot loader doesnt match the installed...
-
1.24 update6 coming from 1.24 update 4. Installer on Windows 10 1909 18363.719 says: "Access is denied. Source: VeraCrypt:File::Write::967 Failed to upgrade the VeraCrypt Boot Loader. Failed to Upgrade VeraCrypt! ...blahblah... you should try installing the original or the new version of VeraCrypt again before you shut down or restart the system." The system reboots fine using the old boot loader, and windows starts. Veracrypt on each reboot complains that the boot loader doesnt match the installed...
1
