大网数据广告活动
服务器运维问答

EnableLinkedConnections isn't working on some Windows 10 machines

· 52CE 我爱测

I have been using the "EnableLinkedConnections" registry setting below for years with no trouble. But lately with Windows 8.1 and Windows 10, sometimes it doesn't work. I need to run some programs with administrative privileges b…

问题原文

原帖链接 · JimDel · CC BY-SA 3.0

I have been using the "EnableLinkedConnections" registry setting below for years with no trouble. But lately with Windows 8.1 and Windows 10, sometimes it doesn't work. I need to run some programs with administrative privileges but they cant see drives mapped as a standard user when this is the case. Does anyone know why this no longer works? Or if there is a work around? Disabling UAC is not an option. Thanks

Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Create a new parameter (DWORD type) with the name EnableLinkedConnections and the value 1

已采纳解答

原帖链接 · StayOnTarget · CC BY-SA 4.0

TLDR: Microsoft has acknowledged a case where EnableLinkedConnections will fail to work. This will occur if UAC requires a password before running an elevated program (ie running as admin).


https://support.microsoft.com/en-us/help/3035277/mapped-drives-are-not-available-from-an-elevated-prompt-when-uac-is-co

Symptoms

This issue occurs when the following conditions are true:

  • You use Group Policy Preference (GPP) or logon scripts to map network drives during logon.

  • User Account Control (UAC) is enabled.

  • The following UAC Group Policy setting is configured to Prompt for credentials:

    • User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode
  • The EnableLinkedConnections registry entry is configured. See the detail to configure the registry entry.

Under these conditions, you experience the following situation:

  • When you log on, mapped drives are available as expected. When you run an elevated command prompt as administrator, the mapped drives are unavailable in the elevated command prompt.

Note This issue also affects other applications that run in an elevated context (run as administrator) and use drive letters to access mapped drives.

Cause

When UAC is enabled, the system creates two logon sessions at user logon. Both logon sessions are linked to one another. One session represents the user during an elevated session, and the other session where you run under least user rights.

When drive mappings are created, the system creates symbolic link objects ("DosDevices") that associate the drive letters to the UNC paths. These objects are specific for a logon session and are not shared between logon sessions.

Note The EnableLinkedConnections registry entry forces the symbolic links to be written to both linked logon sessions that are created, when UAC is enabled.

When the UAC policy is configured to Prompt for credentials, a new logon session is created in addition to the existing two linked logon sessions. Previously created symbolic links that represent the drive mappings will be unavailable in the new logon session.

Workaround

To work around this issue, follow the steps in one of the following methods:

Method 1

  1. In Local Group Policy Editor, locate the following Group Policy path: Local Computer Policy\Windows Settings\Security Settings\Local Policies\Security Options

  2. Configure the following policy to Prompt for consent: User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode

Method 2

Map the required drives again in the elevated session, for example, by using a .bat script file.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


A link to a similar bulletin was provided in a comment above, but didn't seem to be for English language users; the link in this answer should be for English locale.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-06-02)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0 / CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。