Schedar

Automounting D: drive as System Favourite Volume has failed after 9.08.2023 Windows 10 Update. System loaded properly but D: drive was missing. Trying to mount it manually resulted in error "The device is not ready Source: MountVolume:9128" However after that there was another informational popup that stated: Your system is not configured to auto-mount new volumes. It may be impossible to mount device-hosted VeraCrypt volumes. Auto-mounting can be enabled by executing the following command and restarting...

Thanks! I have prepared the latest rescue disk. I have decrypted D drive. Now will attempt to decrypt system drive. Decryption of C went well. Everything is back to normal.

Thanks! I have prepared the latest rescue disk. I have decrypted D drive. Now will attempt to decrypt system drive.

Hi, I have updated VeraCrypt from 2.19 to 2.24Upd7. I had encrypted system drive with preboot authentication that asks for password before loading system. After updating VeraCrypt I can no longer boot the system after entering correct password. The password prompt prints information that entered password is correct and then freezes. The only way I can boot system is to go to F12 UEFI menu and select one of two devices with boot partitions available on system drive. Then the password prompt appears...

Thanks - that seem to work - now I've changed volume type to VeraCrypt and can decrypt it.

Hi, I have encrypted system volume as C: and system favourite volume mounted as D: so both partition auto-mount at boot time. The C: volume was encrypted by VeraCrypt and D: volume was encrypted in TrueCrypt so "True Crypt mode" needs to be used mount D:. Althought I can mount both volumes just fine unfortunately I'm not able to decrypt the D volume, because of error: Operation failed due to one or more of the following: - Incorrect password. - Incorrect Volume PIM number. - Incorrect PRF (hash)....