Could Not Reconnect All Network Drives Error on Windows 10 – Here’s a Fix!

Technician using cable tester while fixing server

Windows 10 is a great Operating System, but it has its quirks.

One of the most common issues people have been reporting is the “Fix – Could Not Reconnect All Network Drives Error” message. This can be a real pain if you rely on your network drives to store files and access them regularly. Fortunately, there are a few things you can do to try and fix the problem. In this article, we’ll walk you through some of the most common fixes for this error.

Let Windows wait for the network

If you have a computer that’s connected to a network, you may want to change its settings so that Windows waits for the network to be available on startup. This can be helpful if you have a lot of devices connected to your network and they’re all trying to connect at the same time. By making Windows wait for the network, you can ensure that all of your devices can connect and that they have the best possible connection. Here’s how to do it.

1. Open the Start Menu and search for “Control Panel.”

2. Click on “Network and Sharing Center.”

3. Click on “Change advanced sharing settings.”

4. Expand the “Private” section.

5. Under “Network discovery,” select “Turn on network discovery.”

6. Under “File and printer sharing,” select “Turn on file and printer sharing.”

7. Click “Save changes.”

8. Close the Control Panel window.

9. Right-click on the Start Menu and select “Command Prompt (Admin).”

10. Type in the following command and hit Enter:

netsh interface set interface “Ethernet” admin=enabled 

11. Close the Command Prompt window.

12. Reboot your computer.

Disconnect the network drive and reconnect it again

To disconnect a network drive:

1. Open File Explorer and click on This PC in the left sidebar.

2. Right-click on the network drive you want to disconnect and select Disconnect from the drop-down menu.

3. You will see a confirmation message asking if you are sure you want to proceed. Click Yes to confirm.

4. The network drive will now be disconnected from your computer.

To reconnect a network drive:

1. Open File Explorer and click on This PC in the left sidebar.

2. Click on Map Network Drive from the top toolbar.

3. A new window will open with several options for connecting to a network drive. In the Folder field, type in the path of the network drive you want to connect to.

4. Select Reconnect at Sign-in if you want Windows to automatically connect to this network drive every time you log in.

5. Click Finish once you have made your selection and the network drive will now be reconnected to your computer.

Use CMD to map the drives needed

Method 1: Net Use Command Script

The first method is to use the net use command. This command is used to connect or disconnect a computer from a shared network resource. To map a network drive using the net use command, you would use a command similar to the following:

net use * \\server\sharename /user:domainname\username password

Replace ‘server’ with the name of the server hosting the shared resource, ‘sharename’ with the name of the shared resource, ‘domainname’ with the domain of the user account you’re using to access the resource, and username with the username of that user account. You would also need to replace the password with the password for that user account.

Method 2: WSHNet_MapDrive Command Script

The second method is to use the WSHNet_MapDrive command script. This script is part of the Windows Script Host networking library and allows you to map network drives using VBScript or Jscript. The syntax for this command is as follows:

WshNetwork.MapNetworkDrive strLocalName, strRemoteShare [, bUpdateProfile] [, strUser] [, strPassword]

strLocalName is the name assigned to the local drive letter being mapped. strRemoteShare is the path of the remote share being mapped (e.g., \\server\sharename). ‘bUpdateProfile’ specifies whether or not you want Windows to update your login script (1 = yes; 0 = no). ‘strUser’ and ‘strPassword’ are optional parameters that allow you to specify a different user account for accessing the remote share. If these parameters are not specified, your current Windows credentials will be used. 

Method 3: Use Group Policy Preferences Instead of Command Scripts

The third method is to use Group Policy Preferences instead of command scripts. Group Policy Preferences offer many benefits over Group Policy Objects (GPOs), including easier management and increased flexibility. One downside, however, is that they’re not available in all versions of Windows (e.g., they’re not available in Windows Server 2003).

To use Group Policy Preferences to map network drives, you would need to edit an existing GPO or create a new one. Once you’ve done that, navigate to User Configuration -> Preferences -> Windows Settings -> Drive Maps and add a new mapping entry.

Specify whether you want this mapping entry applied when users log on or off and specify which users or groups you want it applied to. Next, specify which action you want (e.g., Update or Create), specify which local drive letter you want to be used for mapping purposes, specify which UNC path should be used for this mapping entry (e.g., \\server\sharename), select any other options as desired (e.g., Reconnect at Logon), and click OK.

Use Task Schedule to map drives during startup

You can use Task Scheduler to automatically map network drives when you log on or start Windows. This can be particularly useful if you have a laptop that you take off-site regularly, as it will ensure that all your important drives are connected and available as soon as you need them. In this article, we’ll show you how to set up this task.

1. Open Task Scheduler from the Start menu.

2. In the left-hand pane, expand the Task Scheduler Library folder and select Microsoft > Windows > Network drive mapping.

3. In the main pane, click the Create task link.

4. In the General tab, enter a name for the task and an optional description. Under Security Options, choose who will run the task and whether they will run it with or without administrative privileges. Then, click the Triggers tab.

5. Click the New button to create a new trigger for the task. In the resulting window, you can choose when to start the task: whether at startup, when a specific event occurs, on a schedule, or whether it will recur daily, weekly, or monthly. For our purposes, select “At startup” and click OK.  You can also add additional triggers if required; for example, if you wanted the task to run every time one of your network drives was disconnected for more than five minutes. When you’re done configuring triggers, click OK to return to the main Task Scheduler window.

6. On the Actions tab, click New… to configure what action will be taken when the trigger fires. From the Action drop-down menu, select Start a program and click Browse… Navigate to and select File Explorer from your list of programs (usually found under C:\Windows\System32). In the Add arguments field, type /e followed by the drive letter and path of your network share (for example, /e Z:\Marketing\Docs). Make sure that both checkboxes are selected under Start in: before clicking OK twice to return to the Task Scheduler window; this will ensure that File Explorer opens at your network share’s location when it starts up so that you can easily access your files.

If you need to map multiple network shares during startup, simply repeat this process for each share. When you’re done configuring actions, click OK to return to the main Task Scheduler window.   Finally, on the Conditions tab, make sure that all three options are unchecked before clicking OK again; otherwise, the task may not run.  And that’s it! Now, whenever you start Windows, your network drives will be mapped automatically.

If the above steps do not fix the issue – no worries, our Windows 10 repair geeks are just a phone call away!

I am a computer engineer holding a bachelor's degree in Computer Science, complemented by a Master's in Business Administration from University of Strathclyde, Scotland. I currently work as a Senior IT Consultant in Melbourne, Australia. With over 15 years of...