"Could not reconnect all network drives" error after you deploy a policy that contains a mapped drive in Windows Server 2012 R2 or Windows Server 2012

Applies to: Windows 8.1 EnterpriseWindows 8.1Windows 8.1 Pro

Symptoms


Consider the following scenario:
  • You use the Group Policy Management Console (gpmc.msc) to configure your Group Policy preferences and to configure a mapped drive in the domain. Specifically, you click User Configuration, click Preferences, click Windows Settings, click Drive Maps, click New, and then click Mapped Drive.
  • You select the Reconnect check box for the mapped drive.
  • In a client that's running Windows 8.1 or Windows 8, User Account Control (UAC) is enabled as the default setting.
  • You log on through an administrator account, and then you verify that the drive is mapped during the first logon.
  • You log off and then log on again through the same user account.

In this scenario, you may receive the following message on the taskbar:

Could not reconnect all network drives.

Note This message is incorrect, as the drive is actually mapped successfully.

Cause


This problem occurs because the UAC setting makes the administrator account use split tokens, and this causes the disconnect operation to fail.

Resolution


To resolve this issue in Windows 8.1 or Windows Server 2012 R2, install update 2955164. For more information about update 2955164, click the following article number to view the article in the Microsoft Knowledge Base:
2955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014
To resolve this issue in Windows 8 or Windows Server 2012, install the hotfix that is described in this article.

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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 have Windows 8 or Windows Server 2012 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Status


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

References


Learn about the terminology that Microsoft uses to describe software updates.