Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Mapped drives are not available from an elevated prompt: UAC "Prompt for credentials" and EnableLinkedConnections

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A user signs in, their mapped drives work in File Explorer, and then a program started with Run as administrator cannot see those drive letters. Microsoft's page "Mapped drives are not available from an elevated prompt when UAC is configured to Prompt for credentials" explains it as a result of how Windows creates logon sessions, and offers two workarounds: change one User Account Control (UAC) policy to Prompt for consent, or map the drives again inside the elevated session.

Prove which conditions apply first. The registry entry EnableLinkedConnections is part of this story, but on Microsoft's page it is one of the conditions of the fault, not the fix, so read its current state before changing anything.

What the error means

Microsoft's page applies to Windows 7 Service Pack 1 and Windows Server 2012 R2, is labelled for supported versions of Windows Client, and is dated 2026-02-12. It states the symptom this way: "When you sign in to the client, mapped drives are available as expected." and "When you run an elevated command prompt as administrator, the mapped drives are unavailable in the elevated command prompt." It adds that the issue "also affects other applications that run in an elevated context (run as administrator) and use drive letters to access mapped drives."

The page lists four conditions that are all true when the issue occurs:

  • You use Group Policy Preference (GPP) or logon scripts to map network drives during logon.
  • UAC is enabled.
  • The Group Policy setting "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" is set to Prompt for credentials.
  • The EnableLinkedConnections registry entry is configured.

The cause, in Microsoft's words: when UAC is enabled, "the system creates two logon sessions at user logon", one elevated and one running with least user rights, linked to each other. Drive mappings are symbolic link objects that tie drive letters to UNC paths, and they are "specific for a logon session and are not shared between logon sessions." EnableLinkedConnections forces the links to be written to both linked sessions. When the policy is Prompt for credentials, a new logon session is created in addition to the two linked ones, and the links made earlier are unavailable in it.

Likely causes

Cause What you see How to confirm
UAC policy is Prompt for credentials and drives were mapped at sign-in Drives work in File Explorer, not in the elevated prompt or a Run as administrator program Read the policy in Local Group Policy Editor under Security Options
EnableLinkedConnections is configured (a condition on Microsoft's page) Same symptom while the entry is present reg query of the value, below

Microsoft's page gives the configuration steps for the entry but does not say it resolves the case where the policy is Prompt for credentials. It names that combination as the problem.

Prove the cause before changing anything

All of this only reads. On the affected computer, open an elevated Command Prompt and record the registry state:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLinkedConnections

The reg query page documents /v <valuename> for a single value. Write down whether the value exists, its type and its data.

Then, in Local Group Policy Editor, go to Local Computer Policy\Windows Settings\Security Settings\Local Policies\Security Options and read "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode". Write down its current setting. Microsoft's page describes the local policy only. It does not say how a domain Group Policy object interacts with it, so if the computer is managed by a domain policy, ask whoever owns that policy before changing anything.

Example (illustrative): at contoso.com.au, a support technician on app01 maps S: to \\fs01\shared through a logon script. In File Explorer S: is present. In an elevated Command Prompt, S: is not found. reg query reports EnableLinkedConnections as REG_DWORD 0x1, and the policy reads Prompt for credentials. That is the exact combination Microsoft's page describes.

Fix

Choose one workaround. The two Microsoft methods are in the order the page gives them.

Method 1: change the UAC policy to Prompt for consent

Before you change it, make sure you have written down the current policy setting from the check above. There is no file to save for this step; the written setting is the saved copy, and the back-out is setting the policy back to that value.

Risk: the next steps change what administrators on this computer see when a program asks for elevation, not only in the mapped-drive case.

  1. In Local Group Policy Editor, go to Local Computer Policy\Windows Settings\Security Settings\Local Policies\Security Options.
  2. Open "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode".
  3. Select Prompt for consent and save.

Microsoft's page does not say whether a sign-out or restart is needed for the policy to apply. Test from a freshly started elevated prompt, and if the drive is still missing, sign out and back in before you test again.

To undo it: open the same policy and set it back to the value you wrote down, which in this example is Prompt for credentials.

Method 2: map the drives again in the elevated session

Microsoft's second workaround is to "Map the required drives again in the elevated session, for example, by using a .bat script file." The page gives no script and no command, so use the mapping method your logon script already uses.

Nothing needs saving before this step, because it adds mappings and replaces nothing. Write down which drive letters you map.

Risk: the next step adds drive mappings inside the elevated session on this computer.

Start your mapping method from an elevated session and map the drive letters the program needs.

To undo it, remove the drive letters you wrote down, using the removal function of the tool or script that created them. Microsoft's page names no command for mapping, so it names none for removing. If your tool or script has no removal function, there is no documented way back.

What Microsoft says about EnableLinkedConnections

Microsoft lists the EnableLinkedConnections registry entry as one of the four conditions of the fault, not as a fix. The page says the entry "forces the symbolic links to be written to both linked logon sessions that are created, when UAC is enabled", and that when the policy is Prompt for credentials a new logon session is created in addition to the two linked ones, so links made earlier are unavailable in it. Under "Detail to configure the EnableLinkedConnections registry entry", the page describes the entry as a DWORD (32-bit) value named EnableLinkedConnections with value data 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System, followed by a restart of the computer.

The page does not say that setting the value resolves the Prompt for credentials case, and it offers Method 1 and Method 2 above as the workarounds. The read-only reg query earlier shows whether it is already present on your computer; if it is, the Prompt for credentials condition is the one to change, by Method 1 or Method 2. If the value is not found, the page does not say what the symptom means; the two workarounds are still Microsoft's methods for the Prompt for credentials condition.

Confirm the fix

  • Sign in again, start an elevated Command Prompt or the program that failed, and reach the drive letter that was missing.
  • Run the reg query command again and compare the result with the state you wrote down; Method 1 and Method 2 do not change it.
  • Test with a second user on the same computer to see whether the result differs.

What to watch afterwards

  • A later change to the UAC policy, locally or by domain policy, which can put Prompt for credentials back.
  • New drive mappings added to the logon script or GPP, which Microsoft's page says are the way the mappings are created in the affected case.
  • Any program that runs elevated and relies on a drive letter. A UNC path (\\server\share) does not depend on a drive letter, but Microsoft's page does not discuss it.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's page names Windows 7 SP1 and Windows Server 2012 R2 and gives no later version range. It does not explain what each UAC setting does beyond the logon-session effect and does not say whether a domain policy overrides the local one. A drive that fails to reconnect at sign-in is a different fault. Changing the UAC prompt behaviour is a security decision for the computer's owner.

Sources