I was running Veracrypt fine on Windows 10 the day before, but after a Windows 10 update, I am no longer able to mount my volume.
Attempting to mount reads:
Operation failed due to one or more of the following:
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF(hash).
- Not a Valid Volume.
I am 100% sure my password is correct.
Any ideas? I have tried restoring the volume header from the backup embedded in the volume
Last edit: Spencer Buik 2016-01-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Normally in the error message, there is a function name and a number? Can you give thise? What version of VeraCrypt are you running?
If you are running an older version of VeraCrypt, try installing the latest stable 1.16.
One test that can be done is to mount the volume in another machine, but of course this is not always possible (you didn't say if you are using a file container or a partition).
Anyway, let's wait for the error number to see where the error occured exactly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A volume can be a file container or a partition...but maybe you want to say a file container (this means you are selecting a file to mount and not a disk, correct?).
This is error happens when a wrong password is entered and I don't see how a Windows update could cause this unless there was some kind of corruption to your file.
Yes, I am trying to mount a container.
I was able to successfuly mount the test containers, but still can't mount mine.
As I said, I know that I am using the right password :/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
well...it appears that somehow your container file was totally corrupted since even the embedded backup is not working.You can check the file container size, timestamp to try to see if something changed on this side.
I'm afraid there is not much that can be done unless you have a backup somewhere.This is not a software problem.
Last hope is that there some kind of keyboard mapping issue and you are just not typing the correct password (few weeks ago a user reported a similar issue and at the end he found he had an issue with the "space" key).
I'm sorry but I can't help more.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Like Mounir, I would also suggest to try mounting on a different system. It's just the easiest and fastest way to exclude any possible sources of error related to the surrounding system, but not to the container itself. With the exception of an OSI Layer 8 Error of course ... ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Friends!
Probably is very late to make my contribution for murphy but I had the exactly same problem yesterday and after reading what Mounir said about the possible file corruption I've managed to solve it. Lucky!! (I'm sure that my problem was that we had an electricity failure and I haven't dismounted the volume the night before).
Method? Well, first of all in the dialog of Veracrypt I market the Truecrypt Mode box under the password box.
It came out a Windows dialog about file corruption, advising me to make a backup before windows attemp to repair the file.
After, on confirming with my password, it started a DOS Window with an automatic work. Asked to confirm the reparation of some files of the file container, and ended up MOUNTING THE VOLUME PERFECTLY!!!
I hope it can useful for somebody. Is worth to try it!!! ;-)
Best Regards.
Note: Yes. I had installed, from long ago, the Truecrypt software. I ignore if this method would work without it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was running Veracrypt fine on Windows 10 the day before, but after a Windows 10 update, I am no longer able to mount my volume.
Attempting to mount reads:
I am 100% sure my password is correct.
Any ideas? I have tried restoring the volume header from the backup embedded in the volume
Last edit: Spencer Buik 2016-01-09
Normally in the error message, there is a function name and a number? Can you give thise? What version of VeraCrypt are you running?
If you are running an older version of VeraCrypt, try installing the latest stable 1.16.
One test that can be done is to mount the volume in another machine, but of course this is not always possible (you didn't say if you are using a file container or a partition).
Anyway, let's wait for the error number to see where the error occured exactly.
I updated to the latest version of VeraCrypt, and still get the error:
I'm trying to mount a volume
A volume can be a file container or a partition...but maybe you want to say a file container (this means you are selecting a file to mount and not a disk, correct?).
This is error happens when a wrong password is entered and I don't see how a Windows update could cause this unless there was some kind of corruption to your file.
To be sure, download the following archive that contains several test VeraCrypt containers: https://bitbucket.org/veracrypt/veracrypt/downloads/VeraCryptTestVolumesWindows.zip
The password for these contains is test.
Are you able to mount them on your machine?
Yes, I am trying to mount a container.
I was able to successfuly mount the test containers, but still can't mount mine.
As I said, I know that I am using the right password :/
well...it appears that somehow your container file was totally corrupted since even the embedded backup is not working.You can check the file container size, timestamp to try to see if something changed on this side.
I'm afraid there is not much that can be done unless you have a backup somewhere.This is not a software problem.
Last hope is that there some kind of keyboard mapping issue and you are just not typing the correct password (few weeks ago a user reported a similar issue and at the end he found he had an issue with the "space" key).
I'm sorry but I can't help more.
Like Mounir, I would also suggest to try mounting on a different system. It's just the easiest and fastest way to exclude any possible sources of error related to the surrounding system, but not to the container itself. With the exception of an OSI Layer 8 Error of course ... ;)
Dear Friends!
Probably is very late to make my contribution for murphy but I had the exactly same problem yesterday and after reading what Mounir said about the possible file corruption I've managed to solve it. Lucky!! (I'm sure that my problem was that we had an electricity failure and I haven't dismounted the volume the night before).
Method? Well, first of all in the dialog of Veracrypt I market the Truecrypt Mode box under the password box.
It came out a Windows dialog about file corruption, advising me to make a backup before windows attemp to repair the file.
After, on confirming with my password, it started a DOS Window with an automatic work. Asked to confirm the reparation of some files of the file container, and ended up MOUNTING THE VOLUME PERFECTLY!!!
I hope it can useful for somebody. Is worth to try it!!! ;-)
Best Regards.
Note: Yes. I had installed, from long ago, the Truecrypt software. I ignore if this method would work without it.