Origingallyposted in General Discussion, Deleted and moved here
Win10
VeraCrypt 1.24 Update 6
Keyfile and Password used
Non-Removable drive
Drive is fully encrypted, no hidden volumes on drive.
Worked yesterday
Fun times! Yeah, lets just say this is a bit annoying when Google fails you on an error message.
I'm attempting to mount one of my encrypted drives (they all error this way) when I'm confronted with the error "MountVolume:8370".
I use the correct keyfile (sadly it had to be recovered from its backup location) and correct password (tried it over and over even after a reboot) and it still doesn't work.
I've also tried it with Admin elevation and without same error.
I've ticked "Use backup header embedded in volume if available" and it still doesn't give me any love.
I try the "Remove all keyfiles" route thinking I'm gonna be slick about it and BAM! Now I'm confronted with a new error "ChangePwd:561"
Again Google failed me with any help on decrypting what the hell either error means.
The error number you are referencing is internal for the developer to tell him where in the code the issue occurred by function name and the line number. The line number may change between releases depending on code modifications.
In your case, I suspect that the keyfile is damaged or altered in the first megabyte (1024 kilobytes) that is preventing you from mounting your volumes.
If you are certain that the password, PIM and keyfile(s) are correct and you have already tried the embedded backup header, I do not have any other ideas in order to mount the volumes.
Just out of curiosity, is your keyfile extension for a known application like ".jpg" or audio files?
The picture, video and audio files are known to have their metadata updated by applications which changes the first megabyte of the file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have the same problem, MountVolume:8370.... on my laptop with win8.1
i youse a countainer. And i have the same probleme on my Win10 pc too with other countainer...
plz help me
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
There is visibily a regression with the latest release 1.24: I had the same error.
I was sure of the password (no keyfile or other) and got 2 volumes that were created in Truecrypt Mode, that couln't be opened.
Then I rolled back to version VeraCrypt v1.23-Hotfix-2 and it is working again!...
I guess I will have to convert these to Veracrypt volumes...
Hope this helps
Last edit: Gregory B 2020-05-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same problem, and v1.23-Hotfix-2 fixed it. For info, I had the problem on two computers which have just updated to latest Win10 update, but did not have the problem on a laptop with Win10 but without the latest update. Could be coincidence, of course.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had the same problem! i thought i've lost my all files!
guess what? Use another drive lette (like F to G) and igot my files back! mine version is 1.24-up6
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Origingallyposted in General Discussion, Deleted and moved here
Fun times! Yeah, lets just say this is a bit annoying when Google fails you on an error message.
I'm attempting to mount one of my encrypted drives (they all error this way) when I'm confronted with the error "MountVolume:8370".
I use the correct keyfile (sadly it had to be recovered from its backup location) and correct password (tried it over and over even after a reboot) and it still doesn't work.
I try the "Remove all keyfiles" route thinking I'm gonna be slick about it and BAM! Now I'm confronted with a new error "ChangePwd:561"
Again Google failed me with any help on decrypting what the hell either error means.
Thanks in advance!
The error number you are referencing is internal for the developer to tell him where in the code the issue occurred by function name and the line number. The line number may change between releases depending on code modifications.
In your case, I suspect that the keyfile is damaged or altered in the first megabyte (1024 kilobytes) that is preventing you from mounting your volumes.
https://www.veracrypt.fr/en/Keyfiles%20in%20VeraCrypt.html
Last edit: Enigma2Illusion 2020-03-31
That was my worse fear. Don't tell me, my drives are tanked.... Stupid keyfile doing what files do best and getting corrupted/altered some way. Frak.
If you are certain that the password, PIM and keyfile(s) are correct and you have already tried the embedded backup header, I do not have any other ideas in order to mount the volumes.
Just out of curiosity, is your keyfile extension for a known application like ".jpg" or audio files?
The picture, video and audio files are known to have their metadata updated by applications which changes the first megabyte of the file.
Hello,
i have the same problem, MountVolume:8370.... on my laptop with win8.1
i youse a countainer. And i have the same probleme on my Win10 pc too with other countainer...
plz help me
Hi everyone,
There is visibily a regression with the latest release 1.24: I had the same error.
I was sure of the password (no keyfile or other) and got 2 volumes that were created in Truecrypt Mode, that couln't be opened.
Then I rolled back to version VeraCrypt v1.23-Hotfix-2 and it is working again!...
I guess I will have to convert these to Veracrypt volumes...
Hope this helps
Last edit: Gregory B 2020-05-18
Was having the same error. Rolled back to this exact version and I got into my volume no problem. Many thanks!
Same problem, and v1.23-Hotfix-2 fixed it. For info, I had the problem on two computers which have just updated to latest Win10 update, but did not have the problem on a laptop with Win10 but without the latest update. Could be coincidence, of course.
I had the same problem! i thought i've lost my all files!
guess what? Use another drive lette (like F to G) and igot my files back! mine version is 1.24-up6