Network drive not showing in elevated apps

Hi everybody,

I am using W10 Home and I have just done a clean install and I am in the process of customizing the system to my needs.

The problem I step into is this:
I connected a new network drive from within Windows Explorer and if I open:
- Command prompt window: Drive exist and it is listed by NET USE
- Admin command prompt window: Drive DOESN'T exist and it is NOT listed by NET USE

I also use FreeCommander. When I launch it the UAC asks for my confirmation and the network drive doesn't show either.

I know it sounds stupid but I can't figure out what happens...

Thanks!

Does anybody had the opportunity to test this in their machines? Is it only happening to me?

It happens to me (and I think everyone). If you do net use from an admin command prompt to map a network drive you'll not see the drive in file explorer (as explorer.exe runs as normal user by default).

Similarly if you map a network drive through explorer (or net use from a non-elevated command prompt) you'll not be able to use it from a program you run as admin.

For programs I need to run as admin that also need a mapped network drive (only one program actually for me ) I map one from an admin command prompt first.

This is I think completely normal - when you run as administrator then you are running as administrator not your normal profile.

See here - I know it is old link but it works the same for me on 10...Mapped Drives Unavailable via Escalated Command Prompt?

Hi Halasz!
I really appretiate your comments. At least now I know that it wasn't my problem!

However I don't think I agree with you about this being "completely normal": if you are an administrator you should be able to control the whole local machine not at "session" level!
Anyway, it's my opinion and I can't do nothing about it... The ways of Microsoft are inscrutable!!!

So your workaround is map the drive twice?
I tried to map it on the admin command prompt with NET USE and the "Persistent" modifier but the mapping does not persist between reboots... Is this also "normal"?

Thanks for your comments.

Frn747 said:

So your workaround is map the drive twice?
I tried to map it on the admin command prompt with NET USE and the "Persistent" modifier but the mapping does not persist between reboots... Is this also "normal"?

I just tested the /p:yes switch. You are right - it persists over re-boot if you map a drive in normal cmd prompt but not if you map it in administrator cmd prompt. I don't know if this is "normal" but it is what happens to me too...

I guess you could set up a scheduled task to run at log on to do it. For me I did it manually. I didn't notice it didn't persist until you mentioned it as I only ran my program that needed it once...