I made a backup of the configuration file. Before mounting, I refresh this configuration file with the backup configuration file.
I usually select keyfiles for my mount. Once done with the keyfile selection, I click on the OK button to get back to the password dialog. At that point, the configuration xml file gets reset to VeraCrypt's default. This only happens in VeraCrypt, not TrueCrypt. Was this deliberate and why? Or is it a bug?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the quick reply. I also want to thank you for carrying the torch and dedicating your time to this software!
I extracted Beta19 as portable. The EXEs have errors upon launching in 32 bit and 64 bit.
"The system cannot fine the file specified." Source: wWinMain:10227
"Unable to connect to the VeraCrypt device driver. VeraCrypt cannot work if the device driver is not running. Please note that, due to a Window issue, it may be necessary to log off or restart the system before the device driver can be loaded."
Once I rebooted, then the EXEs are operational.
As for the original issue, it still exists in 1.17-BETA19. For some reason, it does not keep the original configuration.xml. Instead, it recreate the file from scratch.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-Make a copy of the configuration file
-Make some edits, such as the <config key="DefaultPRF">1</config> value. VeraCrypt's default is 0.
-Mount and get to the password dialog.
-Compare the configuration files (with a file comparison software). Should be almost exact.
-Add keyfiles and make sure to hit "OK" after done. Even if you don't add any keyfiles, as long as you click "OK" to get back to the password dialog.
-Compare the configuration files (with a file comparison). Defaults back to VeraCrypt's original values.
NOTICE: the other button(Mount Options) works fine. It left the configuration file intact.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mounir, I have extracted and tested 1.17-BETA20 for several hours. Issue is still there. Fortunately, I was able to pinpoint it for you to review.
It is the command line switch of "/quit". Please review the below.
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q"
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"
ERROR: When open KeyFile dialogbox and press OK, it will reset the configuration.xml back to default, causing the lost of all previous settings.
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background
Last edit: WRVC2016 2016-02-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made a backup of the configuration file. Before mounting, I refresh this configuration file with the backup configuration file.
I usually select keyfiles for my mount. Once done with the keyfile selection, I click on the OK button to get back to the password dialog. At that point, the configuration xml file gets reset to VeraCrypt's default. This only happens in VeraCrypt, not TrueCrypt. Was this deliberate and why? Or is it a bug?
Thanks
I have fixed a similar bug in 1.17-BETA19 as indicated in the release notes here https://veracrypt.codeplex.com/wikipage?title=Release%20Notes:
Can you please check that this indeed solves your issue?
Hi Mournir,
Thanks for the quick reply. I also want to thank you for carrying the torch and dedicating your time to this software!
I extracted Beta19 as portable. The EXEs have errors upon launching in 32 bit and 64 bit.
"The system cannot fine the file specified." Source: wWinMain:10227
"Unable to connect to the VeraCrypt device driver. VeraCrypt cannot work if the device driver is not running. Please note that, due to a Window issue, it may be necessary to log off or restart the system before the device driver can be loaded."
Once I rebooted, then the EXEs are operational.
As for the original issue, it still exists in 1.17-BETA19. For some reason, it does not keep the original configuration.xml. Instead, it recreate the file from scratch.
To recreate this issue:
-Make a copy of the configuration file
-Make some edits, such as the <config key="DefaultPRF">1</config> value. VeraCrypt's default is 0.
-Mount and get to the password dialog.
-Compare the configuration files (with a file comparison software). Should be almost exact.
-Add keyfiles and make sure to hit "OK" after done. Even if you don't add any keyfiles, as long as you click "OK" to get back to the password dialog.
-Compare the configuration files (with a file comparison). Defaults back to VeraCrypt's original values.
NOTICE: the other button(Mount Options) works fine. It left the configuration file intact.
Ah...I see: the previous fix was not complete and I missed a line that still had the issue.
This time I have implemented a compelete fix: https://sourceforge.net/p/veracrypt/code/ci/555849607935e2b2c321c606d3e3b0664c5b5a8d/
It will be included in the next beta (maybe released tomorrow).
OK, when the next release comes out, I will test it and let you know. Thanks
I have published installer for 1.17-BETA20 that fixes this issue. You can get it from:
Thank you for making VeraCrypt better!
Last edit: Mounir IDRASSI 2016-02-09
Thanks Mounir IDRASSI. I will test it out later today and let you know.
Mounir, I have extracted and tested 1.17-BETA20 for several hours. Issue is still there. Fortunately, I was able to pinpoint it for you to review.
It is the command line switch of "/quit". Please review the below.
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q"
No Error:
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"
ERROR: When open KeyFile dialogbox and press OK, it will reset the configuration.xml back to default, causing the lost of all previous settings.
"C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background
Last edit: WRVC2016 2016-02-10
Thank you for the extensive testing!
Thank you to you, I was able to locate the bug easily and I pushed the fix: https://sourceforge.net/p/veracrypt/code/ci/aa40e8305442d4611a7c6ad3bdfe255dd30cfa48/
I will upload the installer for 1.17-BETA21 shortly.
Awesome Mounir. Thank you for being so active on this!
I have tested 1.17-BETA21 and the above issue has been resolved. Thank You
Last edit: WRVC2016 2016-02-12
when do i use veracrypt rescue disk and how do i use it