When I try to mount my container, Veracrypt fails to mount it and shows me the following message
Keyfile and Password are correct (both are located on another disk)
Volume seems to be okay, did a chkdsk /F /R on my external hard disk drive, no error
I tried to backup and restore the volume header and it didn't work.
I also tried to mount the container on another system and it showed me the same error message as on my computer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just installed veracrypt and started to encrypt in place my 5400 rpm 4tb partition loaded with data. It said "6 days" and I said "oh hell no". (task manager/resource monitor says that the drive is being hit for 11 MB/s read + 11 MB/s write for a total of 22 MB/s. I'm using only AES). I hit defer, try to permanently decrypt, entered password, and got this error. If I try to resume encrypting, it works fine. Help would be greatly appreciated (I don't got days to wait).
Update:
I installed the latest beta, rebooted, and the decryption process started. Sorry for hijacking the thread, but maybe I provided a clue. I'm disappointed that veracrypt didn't work out for me. I dislike the thought of upgrading to pro just to use bitlocker (backdoorlocker?). I'll probably backup my data and encrypt an empty drive (which i will oddly be faster than encryption in place?), but right now I'm recovering from quite a scare (setting up new laptop while traveling put me in awkward place).
Last edit: bio blood 2017-07-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Glad it worked for you, but neither the beta version nor the 1.19 version are able to mount my volume. It only shows me same error message, just with another numbers.
1.19 - 7763
1.21 - 8031
Beta - 8044
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This type of wrong password error can happen if something corrupted the volume header that is present at the begining of the disk.
For such situation, VeraCrypt stores a backup header at the end of the disk. So, the first thing to try is to mount the volume using the embedded backup header. To do so, click on "Mount Options" in the password dialog and check "use backup header embedded in volume if available" as shown in the screenshot below.
In order to try to solve this, just enable AutoMount under Windows : start a command prompt as an Administrator ("Run as an Administrator"). In this command prompt, type : diskpart. Then after diskpart has started, type : AUTOMOUNT ENABLE
Restart Windows and try again.
Does any of this fix your problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The encryption of my hdd was interrupted at the beginning because the hdd's power connector was a bit loose for a second but it continued normally after I connected the power source correctly. Could it be that this is why I can not mount it anymore?
(sorry for overtaking this thread here)
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 after changing the password and I was able to access the drive one time and this is how I know that the password is correct. I also follow the sugestions above and my drive is not accessible. I have this thread that I have created https://sourceforge.net/p/veracrypt/discussion/technical/thread/b0c8c9e7/
Do you think spinrite from gibson corporation might fix the problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally got it open again only to discover that there was was at least 40 spaces behing it the password and invisible. I quickly did a backup, and was able to change the password. The disk is accessible.
Unfortunately none of it worked. I Updated from version1.21 to the BETA3, and now also have the error code 8044 like clay above.
1.21 - 8031
Beta - 8044
There´s medical data on that drive that I think I didnt save before, so I need my data back (my first encryption experience failed into my worst nightmare, like I was afraid... help)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
I have the same problem of error 8031 on a fully encrypted non-system volume. After a Windows Update reboot, this error keeps coming up and I'm unable to access the data, on the original computer or on any other, using first original VeraCrypt v1.19 then v1.21.
I think I've noticed something but am uncertain: I'm quite sure the volume was a basic 2TB GPT drive when I created it but now it appears in windows computer management as a Dynamic disk. Converting from Dynamic back to Basic is possible with tools like EaseUs but I'm not sure I should do that without further info.
I browsed/trawled with no success so far...Does anyone have a clue ?
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 after changing the password and I was able to access the drive one time and this is how I know that the password is correct. I also follow the sugestions above and my drive is not accessible. I have this thread that I have created https://sourceforge.net/p/veracrypt/discussion/technical/thread/b0c8c9e7/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally got it open again only to discover that there was at least 40 spaces behing it the password and invisible. I quickly did a backup, and was able to change the password. The disk is accessible.
Last edit: jean 2017-08-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
Couple of days ago got brand new ssd for my laptop, installed win 7 on it, then made system partition encryption (VC 1.21, AES). After installing all drivers and win updates it refused to boot with error c0000145. VC bootloader is ok, it accepts password, windows start booting,then getting BSOD.
I tried to use VC rescue disk, but my password never matched.
Then I booted from old drive into windows, installed VC 1.21, succesfully mounted ssd encrypted partition, checked everything, and it seems like Ok, files were there, no damages.
When I try to make permanet decryption I'm getting 8031 error, and password never matches. So permanet decryption is impossible nor with bootloader nor with win application for me.
I noteced that when I try to make permanent decrytion with win app window header has name "VeraCrypt Volume Creation Wizard" - is that correct?
After unsuccesful permanent decryption win app stucks with this partiotion and it is impossible to mount it again until reboot.
Any ideas how I can decrypt it? Maybe it is a bug?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I try to mount my container, Veracrypt fails to mount it and shows me the following message
Keyfile and Password are correct (both are located on another disk)
Volume seems to be okay, did a chkdsk /F /R on my external hard disk drive, no error
I tried to backup and restore the volume header and it didn't work.
I also tried to mount the container on another system and it showed me the same error message as on my computer.
I'm getting this error too.
I just installed veracrypt and started to encrypt in place my 5400 rpm 4tb partition loaded with data. It said "6 days" and I said "oh hell no". (task manager/resource monitor says that the drive is being hit for 11 MB/s read + 11 MB/s write for a total of 22 MB/s. I'm using only AES). I hit defer, try to permanently decrypt, entered password, and got this error. If I try to resume encrypting, it works fine. Help would be greatly appreciated (I don't got days to wait).
Update:
I installed the latest beta, rebooted, and the decryption process started. Sorry for hijacking the thread, but maybe I provided a clue. I'm disappointed that veracrypt didn't work out for me. I dislike the thought of upgrading to pro just to use bitlocker (backdoorlocker?). I'll probably backup my data and encrypt an empty drive (which i will oddly be faster than encryption in place?), but right now I'm recovering from quite a scare (setting up new laptop while traveling put me in awkward place).
Last edit: bio blood 2017-07-31
Glad it worked for you, but neither the beta version nor the 1.19 version are able to mount my volume. It only shows me same error message, just with another numbers.
1.19 - 7763
1.21 - 8031
Beta - 8044
I'm getting the same error. Just encrypted my external hdd over the weekend with v1.21 (x-64)
Error when backing up the volume header is 10092.
Last edit: Alex Cazes 2017-07-31
This type of wrong password error can happen if something corrupted the volume header that is present at the begining of the disk.
For such situation, VeraCrypt stores a backup header at the end of the disk. So, the first thing to try is to mount the volume using the embedded backup header. To do so, click on "Mount Options" in the password dialog and check "use backup header embedded in volume if available" as shown in the screenshot below.
If this doesn't solve the problem, the issue could be linked to the fact that AutoMount is disabled in Windows (as explained in https://sourceforge.net/p/veracrypt/discussion/technical/thread/5948980c/#106d). In this case, you have to do the following:
Does any of this fix your problem?
Unfortunateley not. Both of these option resulting in the same error message as mentioned in my first post.
The encryption of my hdd was interrupted at the beginning because the hdd's power connector was a bit loose for a second but it continued normally after I connected the power source correctly. Could it be that this is why I can not mount it anymore?
(sorry for overtaking this thread here)
The Power Connector isn't the problem, since the file was located on my external HDD and everything on it was and is working correctly.
Hi,
I have the same problem after changing the password and I was able to access the drive one time and this is how I know that the password is correct. I also follow the sugestions above and my drive is not accessible. I have this thread that I have created
https://sourceforge.net/p/veracrypt/discussion/technical/thread/b0c8c9e7/
Do you think spinrite from gibson corporation might fix the problem?
I finally got it open again only to discover that there was was at least 40 spaces behing it the password and invisible. I quickly did a backup, and was able to change the password. The disk is accessible.
Unfortunately none of it worked. I Updated from version1.21 to the BETA3, and now also have the error code 8044 like clay above.
1.21 - 8031
Beta - 8044
There´s medical data on that drive that I think I didnt save before, so I need my data back (my first encryption experience failed into my worst nightmare, like I was afraid... help)
Hello all,
I have the same problem of error 8031 on a fully encrypted non-system volume. After a Windows Update reboot, this error keeps coming up and I'm unable to access the data, on the original computer or on any other, using first original VeraCrypt v1.19 then v1.21.
I think I've noticed something but am uncertain: I'm quite sure the volume was a basic 2TB GPT drive when I created it but now it appears in windows computer management as a Dynamic disk. Converting from Dynamic back to Basic is possible with tools like EaseUs but I'm not sure I should do that without further info.
I browsed/trawled with no success so far...Does anyone have a clue ?
I have the same problem after changing the password and I was able to access the drive one time and this is how I know that the password is correct. I also follow the sugestions above and my drive is not accessible. I have this thread that I have created
https://sourceforge.net/p/veracrypt/discussion/technical/thread/b0c8c9e7/
I finally got it open again only to discover that there was at least 40 spaces behing it the password and invisible. I quickly did a backup, and was able to change the password. The disk is accessible.
Last edit: jean 2017-08-14
Hi!
Couple of days ago got brand new ssd for my laptop, installed win 7 on it, then made system partition encryption (VC 1.21, AES). After installing all drivers and win updates it refused to boot with error c0000145. VC bootloader is ok, it accepts password, windows start booting,then getting BSOD.
I tried to use VC rescue disk, but my password never matched.
Then I booted from old drive into windows, installed VC 1.21, succesfully mounted ssd encrypted partition, checked everything, and it seems like Ok, files were there, no damages.
When I try to make permanet decryption I'm getting 8031 error, and password never matches. So permanet decryption is impossible nor with bootloader nor with win application for me.
I noteced that when I try to make permanent decrytion with win app window header has name "VeraCrypt Volume Creation Wizard" - is that correct?
After unsuccesful permanent decryption win app stucks with this partiotion and it is impossible to mount it again until reboot.
Any ideas how I can decrypt it? Maybe it is a bug?
Sorry wrong infos
Last edit: jaroc 2017-12-21