Why isn't a mapped drive available under an elevated cmd prompt but is under a regular cmd prompt? [duplicate]

With Windows 8, why isn't a mapped drive available under an elevated cmd prompt but is under a regular cmd prompt? I can run a net use and get it to be available but I still find this odd.

When using UAC with an administrative user, at login, Windows creates two tokens. One token (the elevated one) is unfiltered, and has the Administrators group enabled. The other token has the Administrators group (and some other details, like the Power Users group) filtered out.

Since these two tokens have separate security contexts, network connections in one aren't available in the other, even if it's really the same user.

So if you map a drive using Explorer, an elevated Command Prompt (or any other elevated process) won't be able to see it.

You can map the same network resource (using the same drive letter, even) in your elevated Command Prompt using the NET USE command. After that, any elevated process will also be able to see it.

William's answer explains why this happens and provides one workaround. But I want to add there is actually a registry fix from Vista that works in Windows 7 to adjust this behavior. Just add this to your registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001

After a reboot mapped drives should be accessible through the elevated command prompt.