Drive is unexpectedly mapped to the root of a nested share in Windows

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 8 or Windows Server 2012.
  • You configure the value of the EnableLinkedConnections registry entry to 1 to enable elevated processes to access network shares.
  • You try to map a drive to a nested share by using an elevated token on the computer. For example, you try to map a drive to the following share path:
    \\computername\share\myshare\user
In this scenario, the drive is unexpectedly mapped to the root of the nested share. For example, the drive is unexpectedly mapped to the following path:
\\computername\share

Cause

This issue occurs because the code that is used to create the symbolic link does not append the prefixed name of the target to the name of the linked target during the link target name construction process.

Resolution

Windows 8.1 and Windows Server 2012 R2 update information

To resolve this issue in Windows 8.1 and Windows Server 2012 R2, install update rollup 2919394. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
2919394 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: February 2014

Windows 8 and Windows Server 2012 hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 8.1, Windows Server 2012 R2, Windows 8 or Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information


Status

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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Properties

Article ID: 2878604 - Last Review: Feb 13, 2014 - Revision: 1

Feedback