What are the dangers of force-dismounting a volume with open directories? I can imagine the many bad things that can happen to an open file, but directories?
The reason I am asking this is because very often on Windows [auto-]dismount prompts me that files or folders are being used by applications, and then checking with Sysinternals' handles command I see that for some reason explorer.exe keeps open handles to directories even though there are no more open windows for the drive.
If there are no seruious dangers for these "open" directories, maybe it would make sense for VeraCrypt to disregard them, or maybe separate the "force" option into one for files and one for directories?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm always a bit wary of using the Force Dismount option as it sounds so drastic. However, I recently installed SpiderOak cloud backup and, for some reason, it prevents any VeraCrypt volume being dismounted normally, even if not included in the backup set. So I'd like to know if Force Dismount is safe to use.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the past I have used forced dismount without noticing anything untoward, but it does leave room for doubt. Now I simply restart Windows if I cannot dismount a VeraCrypt volume, which seems to me the safer option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are the dangers of force-dismounting a volume with open directories? I can imagine the many bad things that can happen to an open file, but directories?
The reason I am asking this is because very often on Windows [auto-]dismount prompts me that files or folders are being used by applications, and then checking with Sysinternals' handles command I see that for some reason explorer.exe keeps open handles to directories even though there are no more open windows for the drive.
If there are no seruious dangers for these "open" directories, maybe it would make sense for VeraCrypt to disregard them, or maybe separate the "force" option into one for files and one for directories?
I'm always a bit wary of using the Force Dismount option as it sounds so drastic. However, I recently installed SpiderOak cloud backup and, for some reason, it prevents any VeraCrypt volume being dismounted normally, even if not included in the backup set. So I'd like to know if Force Dismount is safe to use.
In the past I have used forced dismount without noticing anything untoward, but it does leave room for doubt. Now I simply restart Windows if I cannot dismount a VeraCrypt volume, which seems to me the safer option.