Hello.
Some strange happening, i have win 10 , veracrypt 1.24 update 6 I press the turn off button to reboot on the PC, but after windows back i went to veracrypt to open the encrypted container but it showing as mounted, i didn't belive my eyes, i tried again to reboot and on the next time it was dismounted. How it can be? i have all unmarked "cach password in the drivers memory" also "wipe cashed password on exit". But it seems it must be dismounted in any case after computer reboot? And it was a reboot not a hibernation mode.
I tried to simulate it again, i.e press turn off button on the PC, but on this time it alwas been dismounted.
I remember a long time ago, it seems i had similar problem, but i though that this is because i didn't have unmarked the "wipe cashed password on exit" but on this time i had it unmarked. I think this is very serious bug, if after reboot a container still opened. It s
Somebody had the same and maybe know how to fix it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, i am talking about not a whole system, but about a encrypted container file, when i opened a veracrypt after reboot , and try to open a container it just showed as opened already, so it not dismounted for some reason after system reboot. This is very strange.And i said it happened already in the past.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having Windows Fast Start enabled which is the Windows default has caused issues that you are reporting.
Per the link in my post above, disable Windows Fast Start.
You should manually dismount all VeraCrypt volumes before shutdown or reboot of your system or risk corruption of the VeraCrypt volume and/or the files/directories within the volume.
You can attempt to have VeraCrypt force dismount volumes which will lose any unsaved work.
See the link below to enable in your VeraCrypt > Settings > Preferences.
Ah ok, I see now.
Ну maybe it so.
I will test it and see if it will happen again, the problem that it was not every time even with Fast Start enabled, usually container was dismounted, but it seems sometimes it remain mounted. So i will test and let you know , if the problem appear again.
Thank you for you help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
Some strange happening, i have win 10 , veracrypt 1.24 update 6 I press the turn off button to reboot on the PC, but after windows back i went to veracrypt to open the encrypted container but it showing as mounted, i didn't belive my eyes, i tried again to reboot and on the next time it was dismounted. How it can be? i have all unmarked "cach password in the drivers memory" also "wipe cashed password on exit". But it seems it must be dismounted in any case after computer reboot? And it was a reboot not a hibernation mode.
I tried to simulate it again, i.e press turn off button on the PC, but on this time it alwas been dismounted.
I remember a long time ago, it seems i had similar problem, but i though that this is because i didn't have unmarked the "wipe cashed password on exit" but on this time i had it unmarked. I think this is very serious bug, if after reboot a container still opened. It s
Somebody had the same and maybe know how to fix it?
Is this the cause of your problem?
https://sourceforge.net/p/veracrypt/discussion/technical/thread/69a3161872/#3027
No, i am talking about not a whole system, but about a encrypted container file, when i opened a veracrypt after reboot , and try to open a container it just showed as opened already, so it not dismounted for some reason after system reboot. This is very strange.And i said it happened already in the past.
Having Windows Fast Start enabled which is the Windows default has caused issues that you are reporting.
Per the link in my post above, disable Windows Fast Start.
You should manually dismount all VeraCrypt volumes before shutdown or reboot of your system or risk corruption of the VeraCrypt volume and/or the files/directories within the volume.
You can attempt to have VeraCrypt force dismount volumes which will lose any unsaved work.
See the link below to enable in your VeraCrypt > Settings > Preferences.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/cb185223aa/#cff3
Ah ok, I see now.
Ну maybe it so.
I will test it and see if it will happen again, the problem that it was not every time even with Fast Start enabled, usually container was dismounted, but it seems sometimes it remain mounted. So i will test and let you know , if the problem appear again.
Thank you for you help!