Hi, I just installed the latest update (1.26.14) and now I can't mount my volume. It says:
The parameter is incorrect.
Source: MountVolume:8899
This happens whether I try to use a batch file I've been using or manually from the GUI.
If I downgrade to 1.26.7, it works perfectly. So the password and keyfile are correct/haven't mysteriously changed.
Please advise?
First, did you reboot after you upgraded to 1.26.14?
https://sourceforge.net/p/veracrypt/discussion/general/thread/8d9f4f9c84/#bb17/373a
Depending how you link or use another copy of the veracrypt.exe could be the problem.
See the thread below.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/#7b76
Does directly using the upgraded 1.26.14 GUI work correctly mounting your volumes but not your batch script?
Please post the batch script.
Confirmed. Rebooting did the trick. Installed and updated via chocolatey on my end... hence didn't get a reboot prompt. Thanks!
Thanks for this. Updated via WinGet I believe (not the normal method at least) and wasn't aware I had to reboot. That was the solution.
Log in to post a comment.
Hi, I just installed the latest update (1.26.14) and now I can't mount
my volume. It says:
The parameter is incorrect.
Source: MountVolume:8899
This happens whether I try to use a batch file I've been using or
manually from the GUI.
If I downgrade to 1.26.7, it works perfectly. So the password and
keyfile are correct/haven't mysteriously changed.
Please advise?
First, did you reboot after you upgraded to 1.26.14?
https://sourceforge.net/p/veracrypt/discussion/general/thread/8d9f4f9c84/#bb17/373a
Depending how you link or use another copy of the veracrypt.exe could be the problem.
See the thread below.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/#7b76
Does directly using the upgraded 1.26.14 GUI work correctly mounting your volumes but not your batch script?
Please post the batch script.
Confirmed. Rebooting did the trick. Installed and updated via chocolatey on my end... hence didn't get a reboot prompt. Thanks!
Thanks for this. Updated via WinGet I believe (not the normal method at least) and wasn't aware I had to reboot. That was the solution.