Volume decrypting successfully under 1.19 but not 1.24 Update 7

[Junjie Wu]

I wasn't good at keeping up with updates, so I was still on 1.19 until I
updated to 1.24 Update 7 today. The file container I had no longer
decrypts with the newer version, but reverting to 1.19 decrypts again.

My volume isn't Truecrypt volume, and when decrypting on 1.19, I have
"Truecrypt Mode" and all other boxes unselected while PKCS-5 PRF is set
to "Autodetection".

Are there known changes between 1.19 and 1.24 Update 7 that could have
made my volume incompatible? I know that's a long time in between, and I
can go and bisect it, but I wonder if anyone know the answer already tha
would save me quite a lot of time. I searched for a while in the forum
and changelogs, but couldn't find anything obvious. Thanks.

[Enigma2Illusion]

To help the developer @idrassi troubleshoot the issue, please provide your type of OS and OS version.

Example: Widows 10 64-bit version 2004 build 19041.450

Do you remember which version of VeraCrypt was used when you first created the encrypted volume?

[Junjie Wu]

I am on Windows 10 Pro 64-bit Version 2004 Build 19041.450. I've figured it out after reading all major changelogs from 1.19 to 1.24 again. This is the one that caused problem for me. Not sure how I missed it in the first pass before making the post...

Changes between 1.23-Hotfix-2 and 1.24 (6 October 2019) :

    All OSs:
        Increase password maximum length to 128 bytes in UTF-8 encoding for non-system volumes.
        Add option to use legacy maximum password length (64) instead of new one for compatibility reasons.

My password was a 128-byte randomly generated string. The volume was created before 1.19, and on a version I don't remember exactly which didn't warn me about it being truncated to 64 bytes. After some upgrade before or to 1.19, I started getting the warning about password getting truncated to 64 bytes, but I was lazy enough to live with it.

After manually truncating my password to 64-bytes, I was able to decrypt the volume in 1.24 Update 7. Guess it's time to reset the password so it actually use the full length. :-)

Thank you for providing detailed changelogs. Otherwise, it probably would take me a lot of time to bisect and even longer to figure out the issue.

[asiokk2uui]

Hi, I just wanted to add that I had the same problem and was able to solve it due to Junjie Wu's post, THANKS!
I didn't update veracrypt for at least two years and when i finally updated it last week, I wasn't able to decrypt my file container. After downgrading to version 1.23 I was able to decrypt the container, but got the warning that the password was truncated to 64 characters (the warning didn't appear in version 1.24).
With version 1.24 Update 7, I am now able to decrypt the container without problems, using my truncated password. However, unlike in the post above I had to shorten the password to 64 characters, not 64 bytes.
I hope this helps for anyone else having this problem.