VC containers on mapped network drives

[Sebastian S.]

Hello,

I have a Issue i can't solve or don't what I do wrong.
Version: 1.24-Update 6, Windows 10 Pro 64bit latest updates

I have data on a range of network drives, which I map to certain drive letters, like M or Q
so its always M:\data\ or O:\images which works well in auto mount scripts

I also want to add encrypted containers containing sensible material
In veracrypt, I tried to open M: or O: by "select file" and go the path, but M: or O: are not available.

If I use the direct network mapping eg: \servername\path\data(containername) this works, but this would break the scripts, since the servers sometimes vanish\change location

I have searched all the wiki/forums/github, but can't find any settings like ("show mapped network drives") to solve this. Or this something Windows 10 changed? Thanks for help.

[Adrian Kentleton]

The most likely cause of this, is that you have mapped the network drives, or run your auto-mount scripts, 'as administrator', which is unlikely to be necessary. (NB this has nothing to do with your having an 'Administrator' account.)

[Sebastian S.]

Hi Adrian,

thanks for this pointer. It was spot on.

For everybody having the same issue, Windows 10 has different "contexts" for users.
Drives mapped by regular users can't be seen by others, even not by an elevated admin.

For security reasons, my drives are mapped by a regular user doing work on that drives.
You would "expect" that VeraCrypt running in an administrator context can see "everything" but in this case it doesn't. It seems that is an bug/error on Microsofts side.

This KB article explains solutions: https://support.microsoft.com/kb/3035277/
I used the registry version, since I don't want to play around with windows policies

Thanks again. Windows 10 keeps being a tricky thing.