Drive mapping maps two different folders for elevated and non-elevated programs

I have a Windows 2012 Domain with a couple of Windows 8 x64 Enterprise members. I want to use Group Policies to map a drive X: to a folder on a file server. The drive X: should be available on the Windows 8 machines for elevated and non-elevated programs. I have configured group policies to create the mapped drive (x:\ mapped to \\filer\stuff\user1\machine1). And - because i know of the elevated/non-elevated problem - group policies set the EnableLinkedConnections key in the registry on the Clients.

So far, so good, i log in with my account on a windows 8 machine (Domain User / Local Admin), open a non-elevated commad prompt, look for X:\ and find it properly mapped to \\filer\stuff\user1\machine1. Next, i open an elevated command prompt, i also have an X:\ there so the "EnableLinkedConnections" setting works but - and that drives me crazy - X:\ is not mapped to the expected location here. In the elevated context, it is mapped to \\filer\stuff. Can anyone explain the reason for that? Both mappings are based on the same configuration in group policies so i really expect them to be the same.

The first idea was that it could be a rights problem but even in the elevated command prompt, i can navigate to the expected target folder without a problem. An idea anyone?

This is a bug that was fixed in a Windows update released in February 2013. Please refer to KB2795944 (archived here).

This update package resolves the following issues:

• Network Drive mappings that are created by using Group Policy Preferences Mapped Drive items do not connect for administrative users. This occurs when the Mapped Drive item is configured to use the Reconnect option.

The update itself can be downloaded manually here.