FIX: The local device name is already in use

Matthew Adams
by Matthew Adams
Windows & Software Expert
Last update:
Affiliate Disclosure

  • Drive mapping is an important feature that allows access to remotely hosted drives.
  • Unfortunately, errors can occur when the driver is hosted improperly.
  • For more guides like the one below, check out our Network Fix Hub.
  • For more similar troubleshooting guides, check out our Windows 10 Errors Hub.
The local device name is already in use
To fix various PC problems, we recommend DriverFix: This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
  1. Download DriverFix (verified download file).
  2. Click Start Scan to find all problematic drivers.
  3. Click Update Drivers to get new versions and avoid system malfunctionings.
  • DriverFix has been downloaded by 0 readers this month.

Some users utilize drive mapping in Windows 10 to access remotely hosted disk drives.

However, users who utilize network drive mapping can occasionally encounter a Restoring Network Connections error when trying to access mapped network drives.

The Restoring Network Connections error message states:

An error occurred while reconnecting <drive letter> to <file path> Microsoft Windows Network: The local device name is already in use.


How do I fix the device name already in use error?

1. Remap the drive

Microsoft’s official resolution for the Restoring Network Connections error is to remap the drive.

  1. To do so, open File Explorer by pressing the Windows key + E hotkey.
  2. Select This PC on the left of File Explorer.
  3. Click the Computer tab.
  4. Click the Map network drive button to open the window shown directly below.
    Map Network Drive window the local device name is already in use windows 10
  5. Then choose a drive for the connection on the Drive drop-down menu.
  6. Click Browse to select a location to map.
  7. Press the Finish button when done.

2. Enable File and Printer Sharing

The Restoring Network Connections error can be due to firewalls blocking File and Printer Sharing.

  1. To check if File and Printer Sharing is enabled for Windows Defender Firewall, click the Type here to search button.
  2. Enter the search keyword firewall in the text box.
  3. Click Windows Defender Firewall to open the Control Panel as shown directly below.
    Windows Defender Firewall applet the local device name is already in use windows 10
  4. Click the Allow an app or feature through the Windows Defender Firewall option on the left of that applet.
    allowed firewall app settings the local device name is already in use windows 10
  5. Press the Change settings button.
  6. Select all the check boxes for File and Printer Sharing if that isn’t enabled.
  7. Click OK to confirm the new settings.
  8. Restart Windows after enabling File and Printer Sharing.

3. Delete the MountPoints2 registry key

Some users have reputedly fixed the Restoring Network Connections error by deleting the MountPoints2 registry key.

  1. Press the Windows key + R at the same time to launch Run.
  2. Type regedit in the Open box and click OK to open the Registry Editor.
    Registry Editor the local device name is already in use windows 10
  3. Next, browse to this registry path: HKEY_CURRENT_USER > Software > Microsoft > Windows > CurrentVersion > Explorer.
  4. Select the Explorer key.
  5. Right-click MountPoint2 to select the Delete option.

4. Restart the Computer Browser service

  1. The Restoring Network Connections error can be due to a conflicting Computer Browser service. Open Run’s window.
  2. Input cmd in Run’s Open text box, and press Ctrl + Shift + Enter at the same time.
  3. Then input net stop “Computer Browser” in the Prompt, and press the Return key.net stop command the local device name is already in use windows 10
  4. Thereafter, type net start “Computer Browser” and press Enter to restart the service.

5. Check for missing drive letters

Some users might need to assign missing drive letters to fix the Restoring Network Connections error.

  1. Right-click the Start menu’s button to select Run.
  2. Input diskmgmt.msc and press Enter to open the window shown directly below.
    The Disk Management window the local device name is already in use windows 10
  3. If there’s a drive without a letter assigned, right-click it and select Change Drive Letter and Paths.
  4. Press the Add button.
  5. Select the Change option.
  6. Select the Assign the following drive letter option.
    Change Drive Letter window the local device name is already in use windows 10
  7. Choose a drive letter on the drop-down menu.
  8. Click OK to exit the window.

Those resolutions will probably fix the Restoring Network Connections error for the majority of users. Note that the issue can also arise when there’s insufficient drive storage space on the server for your network.

So, some users might need to free up root drive storage space on their network servers.

If you know of another method of fixing this issue, let us and everyone else know by leaving us a message in the comments section below.



This article covers:Topics:

Frequently Asked Questions

  • There are plenty of issues that you may encounter when drive mapping, the most common being a situation when you are facing a drive unmapping.

  • If you have issues using Synology for drive mapping, follow the detailed steps from this guide.

  • One quick way to fix this issue is to simply change the drive name.

There are no comments yet. Please leave a comment

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *