Ever since the upgrade, it seems that VeraCrypt is caching the password for the system drive, even though I specifically have this disabled.
On a fresh boot into Windows, when I go to mount another volume, it starts the long process of trying to mount it as if I entered a password, and then after it fails it asks for the actual password. This is very annoying.
There is a "Wipe Cache" button that I can press, which "fixes" it for the entire session. It will no longer automatically try any passwords. However, as soon as I reboot the computer, a password is put back into Cache again.
I went in to the settings and "enabled" then "disabled" the password cache for the system encryption just to be sure; however, sure enough after a reboot the system encryption password was cached again.
Last edit: Russ Kubes 2018-05-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On a fresh boot into Windows, when I go to mount another volume, it starts the long process of trying to mount it as if I entered a password, and then after it fails it asks for the actual password. This is very annoying.
Do you have "Mount all devices-hosted VeraCrypt volumes" enabled in Settings > Preferences?
Did you enable "Start VeraCrypt Background Task"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately after rebooting with Hibernate disabled, it still thinks there's a password cached at boot.
Edit:
I was able to figure out the issue. I started digging through all of the configuration pages.
There was a setting in "System Favorite Volumes" to mount system favorites when Windows starts. Somehow this setting was enabled, even though I never use this feature.
When I clicked the checkbox to disable the feature, VeraCrypt gave me an error message. It was to the effect of a certain service that was not running or not available. I wish I took a screenshot of it, because now toggling that setting back and forth I'm unable to reproduce the error.
Anyway, with that setting disabled, and a fresh reboot, VeraCrypt no longer thinks there's a password in the cache.
I have Windows 10 with system drive encryption, on a BIOS boot. VeraCrypt is version 1.22
I also have different volumes that I mount after booting into Windows that have a separate password.
Typically, when I would try to mount the other volumes, it would immediately ask me for the password - as expected.
However, I've upgraded to Windows 10 version 1803, using this method: https://github.com/th-wilde/veracrypt-w10-patcher
Ever since the upgrade, it seems that VeraCrypt is caching the password for the system drive, even though I specifically have this disabled.
On a fresh boot into Windows, when I go to mount another volume, it starts the long process of trying to mount it as if I entered a password, and then after it fails it asks for the actual password. This is very annoying.
There is a "Wipe Cache" button that I can press, which "fixes" it for the entire session. It will no longer automatically try any passwords. However, as soon as I reboot the computer, a password is put back into Cache again.
I went in to the settings and "enabled" then "disabled" the password cache for the system encryption just to be sure; however, sure enough after a reboot the system encryption password was cached again.
Last edit: Russ Kubes 2018-05-25
Ensure that Windows Fast Startup is still disabled after the upgrade.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
Then reboot PC.
I should have noted I also already turned that off - otherwise booting takes about 20 minutes.
Do you have "Mount all devices-hosted VeraCrypt volumes" enabled in Settings > Preferences?
Did you enable "Start VeraCrypt Background Task"?
"Start VereCrypt Background Task" is on; but "Mount all devices-hosted VeraCrypt volumes" is off.
For testing purposes, disable Windows hibernate in your power profile (Fastboot.png) and reboot your computer.
Unfortunately after rebooting with Hibernate disabled, it still thinks there's a password cached at boot.
Edit:
I was able to figure out the issue. I started digging through all of the configuration pages.
There was a setting in "System Favorite Volumes" to mount system favorites when Windows starts. Somehow this setting was enabled, even though I never use this feature.
When I clicked the checkbox to disable the feature, VeraCrypt gave me an error message. It was to the effect of a certain service that was not running or not available. I wish I took a screenshot of it, because now toggling that setting back and forth I'm unable to reproduce the error.
Anyway, with that setting disabled, and a fresh reboot, VeraCrypt no longer thinks there's a password in the cache.
Last edit: Russ Kubes 2018-05-26