I asked this question a couple months ago, but I want to try again.
An odd variation on an old theme. VeraCrypt assigns a user-selected drive letter to a file (or something) when mounting an encrypted "VeraCrypt container". It has a function to automatically dismount the drive when the signs off, issues a "Lock", or when the computer goes to sleep, but this function stopped working for me a couple years ago. To compensate, I defined a task that issues a VeraCrypt Dismount command under those conditions. (I barely know anything about defining task triggers so I very well may be doing it wrong.) Anyway, my task almost works. When I log back in VeraCrypt no longer has the drive mounted ... according to VeraCrypt. However, Windows still has the drive letter in use. If I click on the drive letter in File Explorer I get a popup saying "M:\ is unavailable".
I could just give up on M: and have VereCrypt assign a different drive letter, but I've got scripts expecting M: to be the drive in question.
The drive does not show in a Subst display - whether or not VeraCrypt has the drive allocated - so I can't use Subst to free it.
The previous advice I got was to wait until I can reboot, but this is happening often enough that I'd rather have a less disruptive technique. Is there one?
An odd variation on an old theme. VeraCrypt assigns a user-selected drive letter to a file (or something) when mounting an encrypted "VeraCrypt container". It has a function to automatically dismount the drive when the signs off, issues a "Lock", or when the computer goes to sleep, but this function stopped working for me a couple years ago. To compensate, I defined a task that issues a VeraCrypt Dismount command under those conditions. (I barely know anything about defining task triggers so I very well may be doing it wrong.) Anyway, my task almost works. When I log back in VeraCrypt no longer has the drive mounted ... according to VeraCrypt. However, Windows still has the drive letter in use. If I click on the drive letter in File Explorer I get a popup saying "M:\ is unavailable".
I could just give up on M: and have VereCrypt assign a different drive letter, but I've got scripts expecting M: to be the drive in question.
The drive does not show in a Subst display - whether or not VeraCrypt has the drive allocated - so I can't use Subst to free it.
The previous advice I got was to wait until I can reboot, but this is happening often enough that I'd rather have a less disruptive technique. Is there one?
- Windows Build/Version
- Win 11 Pro x64 22000.978
My Computer
System One
-
- OS
- Windows 11
- Computer type
- PC/Desktop
- Manufacturer/Model
- Microsoft
- CPU
- Intel Core i5-8400
- Motherboard
- ASUS PRIME H370-PLUS
- Memory
- 16GB
- Graphics Card(s)
- Intel UHD Graphics 630
- Sound Card
- On board
- Monitor(s) Displays
- Samsung SyncMaster 2043BWX
- Screen Resolution
- 1680 x 1050
- Hard Drives
- Samsung SSD 850 256GB
WDC 1TB NVMe
WD 3TB external USB drive
- PSU
- I don't remember
- Case
- Fractal Design R4
- Cooling
- Air CPU + 2 case fans
- Keyboard
- DAS S Pro (Cherry Brown)
- Mouse
- Logitech USB of some sort