today I accidently crashed an I/O-intense job when I closed the lid of a notebook, not knowing it would standby/hibernate. The the VC Volumes that have been mounted from external drives wer force-dismounted. I experienced this before and it would be nice to fix this, as probably the VC driver just did not wait long enough for the external drives bein available again.
However the more interesting part was, that all the drive letter which have been used before where no longer available to mount to (again) in VC. I was able to mount other volumes to those drive letters, however there was a warning by windows when doing so.
I read that veracrypt driver actually uses a service - I wonder why this services is not in the services list?! however I trieted to
net stop veracrypt
which failed and I was no longer able to use VC at all. trying to stop it (again) or start it resulted in an error that the service was "about to start or about to terminate".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey there,
today I accidently crashed an I/O-intense job when I closed the lid of a notebook, not knowing it would standby/hibernate. The the VC Volumes that have been mounted from external drives wer force-dismounted. I experienced this before and it would be nice to fix this, as probably the VC driver just did not wait long enough for the external drives bein available again.
However the more interesting part was, that all the drive letter which have been used before where no longer available to mount to (again) in VC. I was able to mount other volumes to those drive letters, however there was a warning by windows when doing so.
I read that veracrypt driver actually uses a service - I wonder why this services is not in the services list?! however I trieted to
net stop veracrypt
which failed and I was no longer able to use VC at all. trying to stop it (again) or start it resulted in an error that the service was "about to start or about to terminate".