Montgomery_Minds

I did some more research on elevated and non-elevated drive mappings. The KB referenced above by @sarchs explains it, but there's more here: Mapped drives (incl net use) missing from elevated processes eg UAC cmd run as administrator | Montgomery Minds Including a link to a technet article which is IMHO better and has some hi quality comments that add: Some Programs Cannot Access Network Locations When UAC Is Enabled Now the KB says this will fix it net use \\\ /user: I just tried this and it did not make the \\COMPUTERNAME\SHARENAME appear in the other net use listing. Now it's possible that even tho it did not appear in the net use listing, it did log me in in both prived and non-prived. I did not test this, cuz i i was already logged in in both and so it requires logging out to test and i cant do that right now for other reasons.

4 year old post, but... I just had this problem today, and tried the priv tip twice, and it worked. It is consistent--at least on my system at this time. Which is windows 7 sp1. details: elevated cmd prompt net use x: \\nodename\c can only be seen in elevated cmd prompt. not in non-elevated cmd prompt. not in explorer. (oddly, not even elevated explorer, ) non-elevated cmd prompt net use x: \\nodename\c can be seen in non-elevated cmd prompt. and for some reason i can not fathom, can NOT be seen in elevated cmd prompt. What is the possible rationale that an elevated cmd prompt cant use a non-elevated mapped drive? That you'll accidentally do something privileged on it? smh. And it can also be viewed in explorer elevated, and non-elevated. similarly, map network driver in explorer CAN be seen in non-elevated cmd prompt net use can NOT be seen in elevated cmd prompt net use Which is maddeningly frustrating cuz i need that often...