I'm having an issue with VeraCrypt 1.23 Beta2, when attempting to do a system encryption. I get an error when doing rescue disk which says: "CAUTION: The Veracrypt Boot Loader is already installed on your system drive!" full pop up in attachments. Which I don't see why it'd say that if it always failed the pretest in 1.22. I select "Yes" and it takes me into saving the rescue disk, when I click "Next", no matter what location it tells me: "The system cannot find the file specified." in a new line it says "Source: VeraCrypt::BootEncryption::CreateRescueIsoImage:3475" with an "Ok" button. Which when pressed brings another window saying "The original system loader will not be stored on the Rescue Disk (probable cause: missing backup file)." with another "Ok" button. When I press that it opens the last window saying "Parameter incorrect.". Then tells me to report the same error thing that was given as source earlier. Any fix for this, I'm very desperate to get VeraCrypt working as the other versions give me a failed pretest and shuts down my computer without starting it back up.
I have done tests using upgrades from 1703 to 1709. The only issue I encountered is if the system is partially encrypted in UEFI case but this is a marginal case and it should never happen in practice.
I am looking to users who are willing to test this version in order to confirm its reliability before rolling it out. Thank you.
Please see link above for more details to perform this test.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been waiting for this update for so long!
I updated my Veracrypt with the beta version, installing the cumulative updates on 1607 works from the update center.
Updating to 1709 from the Windows 10 Update assistant did NOT work, i had to manually launch setup.exe with the command you provided.
After manually launching the setup, the update from 1607 to 1709 works without any problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm confused by this thread. Is there some known issue or conflict between Windows 10 1709 and using VeraCrypt? Or is there a conflict between installing Windows 10 feature releases and using VeraCrypt? I was getting ready to install VeraCrypt on a Windows 10 1803 system, and I really don't want to lose my data. 😉
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a question, maybe it will seem stupid, but I need to know. On the HDD where the information was badly deleted and can be recovered(Local disk NTFS), is it possible in theory to recover this data from a mounted volume, which was created exactly at this place? The volume is fully 100% independent or contains some external data after creation(from hdd, file system, clusters and other)?
Thank you.
Last edit: aleksey kuznetsov 2018-04-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get following error message:
Veracrypt::BootEncryption::CreateRescueIsoImage:3459
It tells me that possible reason may be that the backup file does not exits.
The file original_boot64.vc_backup exists in EFI partition. I'm not sure if this is the file the VC message refers to.
Before it happens Veracrypt tells me that veracrypt boot loader is already intalled and my system may not be bootable if I proceed.
I tried to mark "Skip Rescue Disk Verification" but it doesn't let me to proceed anyway.
Last edit: Jerzy 2018-05-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VeraCrypt looks for the bootloader backup at
"C:\ProgramData\VeraCrypt\Original System Loader".
This file is normally created during system encryption process but maybe
something in your configuration caused the file not to be created.
To fix this, you can simply create this file by copying the original
Windows bootloader from EFI partition to it. But first, you have to
check if the file "EFI\Boot\original_bootx64.vc_backup" is correct one.
If its size is around 20 000 bytes, then it is not good and if its size
if around 1 200 000 bytes, then it should be OK.
In all cases, the file EFI\Microsoft\Boot\bootmgfw_ms.vc is a good
source to create a backup of the bootloader.
Here is a command sequence to fix this in an administrator command prompt:
B:\EFI\Boot\original_bootx64.vc_backup : The term 'B:\EFI\Boot\original_bootx64.vc_backup' is not recognized as the
name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ B:\EFI\Boot\original_bootx64.vc_backup
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (B:\EFI\Boot\original_bootx64.vc_backup:String) [], CommandNotFoundExcep
tion
+ FullyQualifiedErrorId : CommandNotFoundException
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Mounir for explanation.
I restored original bootx64.efi from previous system and it worked.
I understand that my situation was a bit unusual - I'm trying to make the HIDDEN OS with UEFI on HP laptop and I made several consecutive attempts and manual editin of EFI partition. Nontheless since this can only be done manually (hidden os with modern hardware) more people may face thsi problem. Also this seems to be the case when someone just reinstalls windows and starts encryption again on same disk.
Anyway thanks a lot for help!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today my header was somehow corrupted, no idea if it happened because of 1.23 Beta 1 though. I'm on Windows 10 1803 and have upgraded without keeping the installed apps and settings, so the system should be pretty clean. Yesterday I activated hibernate and used it, today the system did a clean boot (instead of restoring everything, hibernate is deactivated again) but didn't mount one of my system favourite volumes. Since I also couldn't mount it manually anymore I restored the embedded backup header and everything worked again.
Sounds to me like Windows screwed something up while going into hibernate mode, but if you would like to investigate this I'm happy to help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2018-05-14
Thank You Mounir for the continuous contribution to the project. I don't see the feature highly anticipated by me, though - the one You said You would try working on. I would gladly hear from the Dev Team if it was considered to implement anymore.
I'm using Windows 10 with 1803 update, on UEFI ssd disk, Lenovo Laptop.
Can I use this 1.23 beta version with no worries?
Version 1.22 of Veracrypt did not work at all with my UEFI 1tb ssd disk and I had a bad time with it.
It's safe to try 1.23beta now?
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, the same problem was already discussed on this forum.
After a normal windows 10 update, the veracrypt bootloader did not load after boot, and using VC rescue disk make things worst. There is known problems on Acer, and HP laptos, mine is Lenovo but has the same/worst problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1.23-BETA is stable and I have just released 1.23-BETA2 that enhances
EFI Rescue Disk decryption compatibility. I didn't release final 1.23
yet because I'm trying to include some new features in it but things
take more time than planned and it's possible that I will release 1.23
as it is now.
There have been many enhancement for EFI system encryption in 1.23-BETA
and it is worth trying in your case. You can choose either to disable
SecureBoot as before or, better, enable SecureBoot by using PowerShell
script that loads VeraCrypt-DCS key into the machine firmware (cf
details about procedure here https://sourceforge.net/p/veracrypt/discussion/technical/thread/ace1e682/?page=1&limit=25#15ef).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@trader5: As I wrote in the other SecureBoot thread, have updated the
SecureBoot powershell script to include your certificates and if you
follow the instructions, you should be able to set SecureBoot mode with
VeraCrypt custom keys, which in turn should resolve any boot issues. It
is better to perform the SecureBoot manipulation before encrypting the
system and after it is done, proceed with system encryption wizard while
SecureBoot is enabled.
Pre-test is a good wait to check compatibility without any risk and you
should always backup the generated Rescue Disk.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 1.23 Beta 0 released April 23, 2018.
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/
I'm having an issue with VeraCrypt 1.23 Beta2, when attempting to do a system encryption. I get an error when doing rescue disk which says: "CAUTION: The Veracrypt Boot Loader is already installed on your system drive!" full pop up in attachments. Which I don't see why it'd say that if it always failed the pretest in 1.22. I select "Yes" and it takes me into saving the rescue disk, when I click "Next", no matter what location it tells me: "The system cannot find the file specified." in a new line it says "Source: VeraCrypt::BootEncryption::CreateRescueIsoImage:3475" with an "Ok" button. Which when pressed brings another window saying "The original system loader will not be stored on the Rescue Disk (probable cause: missing backup file)." with another "Ok" button. When I press that it opens the last window saying "Parameter incorrect.". Then tells me to report the same error thing that was given as source earlier. Any fix for this, I'm very desperate to get VeraCrypt working as the other versions give me a failed pretest and shuts down my computer without starting it back up.
Here are some screenshots;
https://sourceforge.net/p/veracrypt/discussion/general/thread/0135ebe7/9dd1/attachment/VeraCrypt%20Format_2018-07-14_22-40-08.png https://sourceforge.net/p/veracrypt/discussion/general/thread/0135ebe7/9dd1/attachment/VeraCrypt%20Format_2018-07-14_22-41-57.png https://sourceforge.net/p/veracrypt/discussion/general/thread/0135ebe7/9dd1/attachment/VeraCrypt%20Format_2018-07-14_22-42-08.png https://sourceforge.net/p/veracrypt/discussion/general/thread/0135ebe7/9dd1/attachment/VeraCrypt%20Format_2018-07-14_22-42-11.png
Here is the list of changes introduced in 1.23-BETA0 (only for Windows):
.
MacOSX:
.
Linux:
Last edit: Enigma2Illusion 2018-04-29
https://sourceforge.net/p/veracrypt/discussion/general/thread/431df6e5/#22cb
Mounir Idrassi wrote:
Please see link above for more details to perform this test.
Any improvements in performance on Samsung SSDs with this latest beta?
I've been waiting for this update for so long!
I updated my Veracrypt with the beta version, installing the cumulative updates on 1607 works from the update center.
Updating to 1709 from the Windows 10 Update assistant did NOT work, i had to manually launch setup.exe with the command you provided.
After manually launching the setup, the update from 1607 to 1709 works without any problems.
Thank you for these tests which validates VeraCrypt implementation.
Concerning the issue with Windows 10 Update Assistant, it affects all
encryption software not only VeraCrypt since Microsoft did not implement
SetupConfig.ini support in it (Probably Bitlocker is supported...).
Here is for example a forum post from 3 months ago that mentions this:
https://social.technet.microsoft.com/Forums/en-US/6a4c12fb-4dc4-4eeb-ba4c-0aa776b4d7cf/commandline-options-when-using-windows-10-update-assistant?forum=win10itprosetup
I'm confused by this thread. Is there some known issue or conflict between Windows 10 1709 and using VeraCrypt? Or is there a conflict between installing Windows 10 feature releases and using VeraCrypt? I was getting ready to install VeraCrypt on a Windows 10 1803 system, and I really don't want to lose my data. 😉
I have a question, maybe it will seem stupid, but I need to know. On the HDD where the information was badly deleted and can be recovered(Local disk NTFS), is it possible in theory to recover this data from a mounted volume, which was created exactly at this place? The volume is fully 100% independent or contains some external data after creation(from hdd, file system, clusters and other)?
Thank you.
Last edit: aleksey kuznetsov 2018-04-27
MacOSX
.
Linux
Last edit: Enigma2Illusion 2018-04-30
I get following error message:
Veracrypt::BootEncryption::CreateRescueIsoImage:3459
It tells me that possible reason may be that the backup file does not exits.
The file original_boot64.vc_backup exists in EFI partition. I'm not sure if this is the file the VC message refers to.
Before it happens Veracrypt tells me that veracrypt boot loader is already intalled and my system may not be bootable if I proceed.
I tried to mark "Skip Rescue Disk Verification" but it doesn't let me to proceed anyway.
Last edit: Jerzy 2018-05-01
VeraCrypt looks for the bootloader backup at
"C:\ProgramData\VeraCrypt\Original System Loader".
This file is normally created during system encryption process but maybe
something in your configuration caused the file not to be created.
To fix this, you can simply create this file by copying the original
Windows bootloader from EFI partition to it. But first, you have to
check if the file "EFI\Boot\original_bootx64.vc_backup" is correct one.
If its size is around 20 000 bytes, then it is not good and if its size
if around 1 200 000 bytes, then it should be OK.
In all cases, the file EFI\Microsoft\Boot\bootmgfw_ms.vc is a good
source to create a backup of the bootloader.
Here is a command sequence to fix this in an administrator command prompt:
mountvol B: /s
B:
copy B:\EFI\Microsoft\Boot\bootmgfw_ms.vc
"C:\ProgramData\VeraCrypt\Original System Loader"
copy B:\EFI\Microsoft\Boot\bootmgfw_ms.vc
B:\EFI\Boot\original_bootx64.vc_backup
After that, you should be able to create the new rescue disk.
On my side, I will try to see how we could arrive to such situation.
The command sequence tells me;
B:\EFI\Boot\original_bootx64.vc_backup : The term 'B:\EFI\Boot\original_bootx64.vc_backup' is not recognized as the
name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ B:\EFI\Boot\original_bootx64.vc_backup
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (B:\EFI\Boot\original_bootx64.vc_backup:String) [], CommandNotFoundExcep
tion
+ FullyQualifiedErrorId : CommandNotFoundException
Thank you Mounir for explanation.
I restored original bootx64.efi from previous system and it worked.
I understand that my situation was a bit unusual - I'm trying to make the HIDDEN OS with UEFI on HP laptop and I made several consecutive attempts and manual editin of EFI partition. Nontheless since this can only be done manually (hidden os with modern hardware) more people may face thsi problem. Also this seems to be the case when someone just reinstalls windows and starts encryption again on same disk.
Anyway thanks a lot for help!!
Version 1.23 Beta 1 released May 2, 2018 adds the following to Beta 0.
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/
Windows:
.
Explaination of Windows LTSB can be found at the link below.
https://www.howtogeek.com/273824/windows-10-without-the-cruft-windows-10-ltsb-explained/
Last edit: Enigma2Illusion 2018-05-03
Today my header was somehow corrupted, no idea if it happened because of 1.23 Beta 1 though. I'm on Windows 10 1803 and have upgraded without keeping the installed apps and settings, so the system should be pretty clean. Yesterday I activated hibernate and used it, today the system did a clean boot (instead of restoring everything, hibernate is deactivated again) but didn't mount one of my system favourite volumes. Since I also couldn't mount it manually anymore I restored the embedded backup header and everything worked again.
Sounds to me like Windows screwed something up while going into hibernate mode, but if you would like to investigate this I'm happy to help.
Thank You Mounir for the continuous contribution to the project. I don't see the feature highly anticipated by me, though - the one You said You would try working on. I would gladly hear from the Dev Team if it was considered to implement anymore.
1) Allow custom/textless message for Rescue Disk
When talking about time-consuming GUI changes is it all right to ask for one more simple thing at the same time?
2) Option to hide tray icon of the VeraCrypt background task
Last edit: Anonymous 2018-05-15
Bei der Rescue Disk Erstellung erhalte ich den Fehler:
VeraCrypt::BootEncryption::CreateRescueIsoImage:3428
Was kann ich tun?
Bug ?
I'm using Windows 10 with 1803 update, on UEFI ssd disk, Lenovo Laptop.
Can I use this 1.23 beta version with no worries?
Version 1.22 of Veracrypt did not work at all with my UEFI 1tb ssd disk and I had a bad time with it.
It's safe to try 1.23beta now?
Thank you.
Hello
Can you be a little more explicit about the kind of problems you've encountered using VC 1.22?
Thanks
Yes, the same problem was already discussed on this forum.
After a normal windows 10 update, the veracrypt bootloader did not load after boot, and using VC rescue disk make things worst. There is known problems on Acer, and HP laptos, mine is Lenovo but has the same/worst problems.
1.23-BETA is stable and I have just released 1.23-BETA2 that enhances
EFI Rescue Disk decryption compatibility. I didn't release final 1.23
yet because I'm trying to include some new features in it but things
take more time than planned and it's possible that I will release 1.23
as it is now.
There have been many enhancement for EFI system encryption in 1.23-BETA
and it is worth trying in your case. You can choose either to disable
SecureBoot as before or, better, enable SecureBoot by using PowerShell
script that loads VeraCrypt-DCS key into the machine firmware (cf
details about procedure here
https://sourceforge.net/p/veracrypt/discussion/technical/thread/ace1e682/?page=1&limit=25#15ef).
Thank you for your reply, I have upload the keys:
https://sourceforge.net/p/veracrypt/discussion/technical/thread/ace1e682/?page=1&limit=25#1a70
I had a bad time on version 1.22, I need yo be sure this time, thank you.
@trader5: As I wrote in the other SecureBoot thread, have updated the
SecureBoot powershell script to include your certificates and if you
follow the instructions, you should be able to set SecureBoot mode with
VeraCrypt custom keys, which in turn should resolve any boot issues. It
is better to perform the SecureBoot manipulation before encrypting the
system and after it is done, proceed with system encryption wizard while
SecureBoot is enabled.
Pre-test is a good wait to check compatibility without any risk and you
should always backup the generated Rescue Disk.