Fail to read Veracrypt container on a second computer
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Background:
My partner and I both have ASUS Zen Laptops (not identical); my OS is Windows 11, hers is W10. We both have Malwarebytes Pro running.
We both use Veracrypt to store sensitive data, some of which is relevant to each other. From time to time (say every 3 months) I copy her container to my laptop to access, transfer and update certain files. This is an arrangement that has worked smoothly for years. Usually I copy her file to an external USB SSD and work from that copy, which I then copy back to her laptop, and the up to date version copied to my laptop for backup.
I am absolutely sure the password is correct and I can open the container on her laptop without problem.
Veracrypt works fine on my laptop.
The problem
The last time I tried to open her container file on my laptop or the SSD it failed, and I haven't been able to get in after several tries. I have recopied the file to the SSD and cannot open it neither on the SSD nor on my laptop. The error message is shown in the attached image.
Is it possible that my update to W11 has broken something?
I'm a bit baffled. Any suggestions please? TIA.
Last edit: Rob 2022-01-08
Last edit: Alex 2022-01-09
Can you still open the file on the SSD using your partner's laptop? If that's the case, there seems to be something odd on your end. If not, maybe the SSD causes the issue.
Greets
Thank you Alex and RealTehreal.
Password - I'm sure it's correct, and I display it to be sure.
"Can you still open the file on the SSD using your partner's laptop?"
Yes.
New data: I checked the version numbers of Veracrypt. They were both oldish versions, hers older than mine. I updated to the latest versions on both machines.
My Veracrypt continues to work OK, apart from still not reading her file.
However, her Veracrypt can no longer read her file container (gulp!)
So it looks like the problem is related to Veracrypt version incompatibility.
My first priority is to reinstall an old version of Veracrypt on her machine (otherwise I will be deep in the s--t).
Then I'll try searching for reasons. But any suggestions are still very welcome!
I've installed version 1.22 (portable) on my partner's laptop and that opens the container file. Much to my relief.
This is due to the fact that your password is longer than 64 characters and versions older than 1.23 were silently truncating it.
Now maximum password length has increased to 128 characters and an option was added to remain compatible with old behavior so you can mount such volumes with new version of VeraCrypt. you can read details at this answer https://sourceforge.net/p/veracrypt/discussion/general/thread/c4500f7f13/?limit=25#f6f4
Thank you Mounir. The password is much less than 64 characters long so I doubt if this is the root of the problem. I've had a quick look at the thread you mention, and the links contained in it.
I have avoided the problem with a simple workaround - I installed the latest version on both machines, created a new container for my partner and copied all the data across. I can open the new container on both laptops.
I'm aware that this doesn't properly 'solve' the issue, but at least I'm back up and running.
"New data: I checked the version numbers of Veracrypt. They were both oldish versions, hers older than mine. I updated to the latest versions on both machines."
-> How old were the VC versions? Any chance the volume has been made in TrueCrypt format?
If not TC, how about you have non-default iterations to deal with?
Last edit: Alex 2022-01-10
I'm not really sure what you mean by: "If not TC, how about you have non-default iterations to deal with?"
Alex: My partner's version was 1.22 and mine was 1.24. When I reverted the version of Veracrypt on her computer I installed 1.22 and it worked fine. So: 'old' but not 'ancient'.
Was it originally a Truecrypt file? Probably yes (we've been following this routine a long time!) and transferred from an older laptop into the bargain. But again, I doubt if this is the root of the problem because I was successfully following this pattern using Veracrypt right up to the time I tried and failed to open the file between Xmas and New Year. And I'm pretty sure the file wasn't corrupted because I made clean copies on the SSD and my laptop: same results.
I'm inclining towards a Win11 vs Win10 problem, because I think that's the only major change I made since the last time I tried it.
Last edit: Rob 2022-01-10
Rob,
Please try the following with the "problem" volume. Try to open it on the computer where it did NOT work. Before you enter the password, please be sure to check the box "TrueCrypt Mode".
Let's see if it will work :)
Well, that's odd. It looks like I already had Truecrypt mode checked, and when I tried with TC mode unchecked ... it worked OK.
Thanks, good idea! I'm going to do a bit more experimenting around that, but it will be tomorrow.
Last edit: Rob 2022-01-10
I am glad I could help :)