Can't decrypt containers "MountVolume:9170" error

[bulk]

Today I have been unable to decrypt any of my encrypted containers.

When trying I am receiving the following error:
"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:9170"

I have most definitely entered the right password, I've tried slowly many times to confirm.
I have backups of the containers on another drive which were last updated a few days ago & I am experiencing the same issue with those too.

Does anyone know what I can possibly do?

I have VeraCrypt version 1.25.9 & I also encrypted the containers on the same version.
I'm using Windows 10, I'm not sure what other information is helpful to give.

I've checked security settings & nothing is blocking veracrypt in any way. I had no issues at all up until today & with all of my encrypted containers, I have different passwords for them except for the backups.

Any help would be greatly appreciated

[bulk]

This issue has resolved itself if anyone from the future comes here.
I made no changes that should have resolved it, I was in the process of setting up a linux VM to try decrypt the file through there but tried once more & it worked

I probably tried between 10-15 times in total, possibly more. It just worked eventually.
My password was the exact password I tried each time, I had a previous attempt still in an open notepad & had it typed beneath it & confirmed character by character.

I believe this is a bug either with Windows or the software.
From all my searching today it appears the results start from around March this year & one of those results the person advised it worked for them on the 17th attempt, I was unable to find that same page to provide it here as a reference. But their incident seems identical to mine.

Sorry I can't be of more help for anyone else that may come here looking for a solution, hopefully yours will just sort itself as mine did.

Just to re-iterate, my issue impacted 4 different encrypted containers all on the same day. Two of those were backups of the two main ones & resided on another device & hadn't been used for a few days, so it wasn't like they had been ungracefully closed without a dismount. This is what makes me believe it's a bug caused either by Windows or the software.

[Fight]

Running VeraCrypt 1.2.9 on Windows 10 Home. I tried encrypting a non-system partition, and I cannot unlock it with correct password and PIM.

In my case it looks like there was likely some unfortunate interplay between VeraCrypt and Windows Device Encryption.

I think I had the D: drive, non-system drive encrypted by Windows Device Encryption - which I didn't know. When I started encryption of non-system drive in VeraCrypt, it ran to 99.74% and then gave an error message. After rebooting the machine I'm unable to unlock this non-system drive using VeraCrypt with correct password and PIM. Windows shows this drive as unformatted, offers to format.

Running blkid on this partition reports TYPE="BitLocker". The first 512 bytes of the partition don't look like a VeraCrypt volume header - it looks like a like a BitLocker header (has the "-FVE-FS-" signature). The last 128 KB of the partition look like random data - but trying to unlock the partition in VeraCrypt using the backup header or trying to restore the primary header from the backup header embedded in partition also failed - again, using the correct password and PIM.

@idrassi - is VeraCrypt checking whether partitions are already encrypted by BitLocker or Device Encryption? If not, can you please implement such a check?

Also, can someone please advise me whether I have any recovery options? I did not save the VeraCrypt volume header externally.

[Enigma2Illusion]

is VeraCrypt checking whether partitions are already encrypted by BitLocker or Device Encryption?

Yes, but only for system encryption starting with VeraCrypt 1.24 Update 7 version.

[sunnyp]