Windows Disk Partition Won’t Mount
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I recently encrypted the SSD C drive of a Windows computer that has the OS on it and had no problems.
Then I went on to encrypt the D drive of the same computer, which is a partition of an HDD attached to the computer. The other accessible partition of the HDD is accessible and not encrypted, and remains so.
After a day and a half of encrypting it told me it was a success. The D drive/partition was encrypted with the data remaining on it.
When I try to mount it however (regardless of mount or auto-mount) I get the following error message:
“Operation failed due to one or more of the following:
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.
- Volume uses an old algorithm that has been removed.
- TrueCrypt format volumes are no longer supported.
Source: MountVolume:9135”
I type in the password correctly and use auto detection for PKCS.
The partition appears in the Windows disk management program as “healthy” and a “RAW” file system. It also appears in File Explorer under the d drive as "local disk". If I try to open it there, it first says I need to format it before I use it. If I click cancel, it tells me it is not accessible, it does not contain a recognized file system, and to make sure all required file system drivers are loaded and that the volume is not corrupted.
I tried restarting my computer with no luck, and then changing the drive assigned to it by Windows in the disk management program to something else, but that didn’t seem to help either.
What can I do? I can't even find the error number online anywhere, though I may be missing it. I know the password is correct.
Please let me know if you need me to provide any other info.
Start by going into Windows Disk Management and simply removing the drive letter, D or anything else. The drive letter should always be assigned at mount time by VeraCrypt. An unmounted volume should have no drive letter. Now see what happens when you try to mount it to the letter of your choice.
Thank you for the suggestion. I removed the drive and then tried mounting it again (without restarting the computer or anything) and got the same error with the same code. I then tried assigning a different drive to it in disk management and then mounting it again, but no luck.
I should also add that I tried entering the password from my c drive encryption, which I know to be wrong, and I received the same error message and code. Not sure if there is any significance to that.
One more thing: the HDD has another partition (G) which does have an OS on it, but not one the computer boots with (I added an SSD to this computer, cloned the HDD to it, and then got the computer to boot from the SSD). That partition is accessible and works fine, but is mounted. Should I unmount it as well?
As long as you're assigning all drive letters for encrypted volumes thru VeraCrypt and not thru Windows Disk Management, you're doing that part right. That was the only problem I saw with your initial procedure because you said the unmounted volume was showing up as the D drive in Explorer. My only advice would be to unmount all non-boot partitions, reboot, and start fresh working with just the one newly encrypted partition you've been unable to mount.
Thank you for your reply.
I unmounted the D drive again in disk management and rebooted the computer, then tried mounting the volume. Same error as before.
Then I did the same with the other partition, G, and rebooted the computer. Still no luck mounting the volume. Same error as before.
I really don't know what to do here. Could it be something with PIM? Key files? I didn't adjust any of the settings when doing the encryption but did see key files put up starred out at some point. I'm not sure if that's relevant?
Maybe I should install an older version of veracrypt? I don't want to mess up the C drive being able to mount, though.
I tried to decrypt the partition just to see if I'd be able to get past the password stage, and no luck! Same error message and error code.
same thing happens to me. did you fix it?