Cannot mount some of my TrueCrypt volumes
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I'm running Window 10 (64-bit) with VeraCrypt 1.18 (64-bit). I have got several external USB-disks encrypted with TrueCrypt. Over the years I have used TrueCrypt versions 6.1a, 6.2a and 6.3a. When I upgraded from Windows 7 to Windows 10 I replaced TrueCrypt with VeraCrypt and I have been able to mount and use my newer TrueCrypt volumes without any problems (those most likely created by TC 6.3a). Today I needed access to the content of one of my older external disks which contained TrueCrypt volume created possibly by TrueCrypt version 6.1a or 6.2a. But the mount failed with message:
Operation failed due to one or more of the following:
Incorrect password.
Incorrect Volume PIM number.
Incorrect PRF (hash),
Not a valid volume.
Source: MountVolume:7762
I'm 100% sure that the password is correct and I have always relied on the default values of PIM and PRF (I even don't know their meaning). I thought that maybe the old disk is not working correctly any more and I tried another disk from the same era with exactly the same outcome.
Is there any hope to get these old TruyeCrypt volumes mounted? At least the documentation says that TrueCrypt V6.x volumes should be ok for my VeraCrypt version. As a last resort I have considered trying to install TrueCrypt 6.3a on my Windows 10. Does that idea make any sense?
Since you are sure the password is correct, the only explanation is that these disks were encrypted using TrueCrypt 5.x and not 6.x..
TrueCrypt 5.x is old to be supported in VeraCrypt and so your only solution would be to install TrueCrypt 7.1 on a machine in order to extract your data.
If your Windows 10 machine has the latest updates, then TrueCrypt will not run because its driver lacks the appropriate signature. In this case, you will have to boot your Windows 10 machine in test mode, run TrueCrypt, extract your data somewhere else and then uninstall TrueCrypt to avoid security issues linked to TrueCrypt vulnerabilities.
Many thanks! I will follow your advice and return to the subject if I hit a wall.
The method you suggested worked, many thanks. Later I remembered that I started to use TrueCrypt with my old laptop, already scrapped, and at that time the version of TrueCrypt might very well have been V5.x. And with my current PC I started with version 6.x and the oldest installation kit I had saved on it was V6.1. So you were quite right about the version and once again thanks for your help.
I'm sorry about the italics in the message text. I tried to create a list.