You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Great scripts - thanks for making these available!
I'm using them successfully with WSL Debian on Windows 10 when using an external USB disk.
I'd also like to use them for the following scenario:
VeraCrypt-encrypted file container located on an internal Windows disk partition.
Manually mount that container on Windows side using VeraCrypt.exe
-- It is assigned a drive letter, e.g. let's say "F".
-- WSL knows about the new drive letter, but cannot see the files/directories within the container unitl / unless I manually mount "F" on WSL.
I was hoping wsl_automount.sh could automount "F" on the WSL side in the above scenario, but it doesn't get triggered. It seems Windows 10 fails to report arrival/departure of the VeraCrypt "F" volume.
Reviewing wsl_automount.ps1, presumably the problem is that Windows doesn't consider the VeraCrypt.exe-initiated mount/unmount to constitute a win32_VolumeChangeEvent, even though the Drive letter "F" appears/disappears. Is it possible to support this use case ... is there some other event that could be used to enable auto-mount/dismount of Veracrypt container files?
Thanks for considering this.
The text was updated successfully, but these errors were encountered:
Hi,
Great scripts - thanks for making these available!
I'm using them successfully with WSL Debian on Windows 10 when using an external USB disk.
I'd also like to use them for the following scenario:
-- It is assigned a drive letter, e.g. let's say "F".
-- WSL knows about the new drive letter, but cannot see the files/directories within the container unitl / unless I manually mount "F" on WSL.
I was hoping wsl_automount.sh could automount "F" on the WSL side in the above scenario, but it doesn't get triggered. It seems Windows 10 fails to report arrival/departure of the VeraCrypt "F" volume.
Reviewing wsl_automount.ps1, presumably the problem is that Windows doesn't consider the VeraCrypt.exe-initiated mount/unmount to constitute a win32_VolumeChangeEvent, even though the Drive letter "F" appears/disappears. Is it possible to support this use case ... is there some other event that could be used to enable auto-mount/dismount of Veracrypt container files?
Thanks for considering this.
The text was updated successfully, but these errors were encountered: