Unable to mount, MountVolume:8299

[dry]

Hello, got this error while trying to mount my encrypted volume (is just a file I have in my documents):
Operaton failed due to one or more of the following:
-Incorrect password.
-Incorrect Volume PIM number.
-Incorrect PRF (hash).
-Not a valid volume.
MountVolume:8299

I have no PIM number, no idea what PRF means. Tried creating a new volume, and it works andmount, so it may be my volume is just corrupt or dmaage??
I mount it friday so I know it should work and the password I'm using is correct.
I use auto-detection, tried using "Use backup header emmbedded in volume if avaible, didn't work.

So I tried restoring the volume header embedded in volume (I don't have a backup, is been two years and this is the first time I can't mount this volume, did not know I can backup the header) but didn't work get almost same error:
Operaton failed due to one or more of the following:
-Incorrect password.
-Incorrect Volume PIM number.
-Incorrect PRF (hash).
-Not a valid volume.
Source: RestoreVolumeHeader:10540

Using Veracrypt 1.23-hotfix-2 (64 bits)

I updated windows to 1903 saturday, maybe something to do with that?

[dgasior]

Hey, I am getting these errors as well. Were you able to find a solution?

I also have updated recently to 1903, but I have multiple HDs that are enrypted but the rest continue to work.

For me, I went to dismount, and it said files or folders were in use, so I left it alone for 24 hours. Tried to dismount again and same thing, so I did a force dismount and then this happened. I tried to do the restore, but like you, same error.

Can anyone help?

[halogenrazors15]

Any updates about this? I've been experiencing the same error. I'm unable to mount my drive. I made sure that I'm inputting the correct password, but I keep on getting the same error.

Please, can somebody help?

[Junjie Wu]

I found this when I was searching, but I was able to figure it out. Linking it here just in case you happen to be having same problem: https://sourceforge.net/p/veracrypt/discussion/technical/thread/73eb83ff29/

This likely doesn't apply to OP, which posted before the change. It's for others that commented later on 1.24 and newer.

[Otto Schwanz]

I got the same message, after I changed in BIOS the Sata configuration mode from IDE to AHCI. Using most recent version of VC. In order to get it running again, I turned back to IDE mode.