‘The Local Device Name is Already in Use’ error relates to network drive mapping. It is quite a common occurrence among people who work with network-based systems on a daily basis.

Here at Bobcares, our Experienced Server Admins assist our clients in resolving this error.

What is error, ‘The Local Device Name is Already in Use’?

When we try to access a network drive, we may receive this error.

The Restoring Network Connections error message states:

‘The Local Device Name is Already in Use’ – Causes

• Drive mapping gone wrong:

The process of network drive mapping can sometimes produce problems like this one when it comes to drive letters.

• Unassigned drive letters:

Some drives may have incorrect or even missing drive letters which causes this error to appear.

• File and Printer Sharing is disabled:

Networking becomes difficult and full of errors if this option is disabled in the firewall we use.

• No space on the server:

Our support team found that we have to free up at least a couple of gigabytes on the root drive of the network’s server to get rid of the problem.

• Registry Key:

The nuclear option – removing the associated registry key to the mapped drive and reloading the configuration can cause this error.

Solutions for ‘The Local Device Name is Already in Use’

Look below for a few steps our Support Engineers employ to potentially correct this error message:

• Remap the Drive Using Command Prompt

Remapping the network drive is the official solution recommended by Microsoft for users facing this problem. It has worked for many users and is one of the most used methods.

1. We search for “Command Prompt”, Right-click and select the “Run as administrator” option.
2. Users who are using an older version of Windows can use the Windows Logo Key + R key combination in order to bring up the Run dialog box.
3. Type in “cmd” in the box and use the Ctrl + Shift + Enter key combination in order to run Command Prompt as an administrator.
4. We give the bellow command and click Enter:

   net use * /delete

5. After we see that the operation is a success, we run the following command:

   net use Z: \\server\share /user:username password

6. We make sure to replace the username and password placeholders with the correct username and password.

• Delete a Key in Registry

If the method above has failed to work, we have to try deleting a certain registry key which might cause the problem. Users who struggle with certain CD/DVD and virtual drives were able to resolve the problem with this method.

1. Since we are going to delete a registry key, we recommend to safely backup the registry to prevent other problems.
   Still, nothing wrong will occur if we follow the steps carefully and correctly.
2. Open the Registry Editor window by typing “regedit” in either the search bar, the Start menu, or the Run dialog box which can be accessed with the Windows Key + R key combination.
3. Navigate to the following key in your registry by navigating at the left panel:

   HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer

4. Click on this key and try to locate a key named MountPoints2 inside the Explorer key.
5. Right-click on it, and choose the Delete option from the context menu.
6. Confirm any dialog boxes which may show up.
7. We check to see if the error message still appears after restarting computer.

• Assign Drive Letters Properly

We’ve clients who have seen a drive with no assigned drive letter in Disk Management which was mapped as the problematic drive letter during the networking process.

Also, if the drive in Disk Management has a different assigned letter than the one in network mapping, we should change it to something else.

We follow the steps below in order to do that:

1. First of all, we need to make sure that no files from the storage devices we want to edit are in use or open in any other way
2. Next, we make sure not to copy or move anything from or to the disk before proceeding
3. After that, we either use the Windows Key + X key combination or right-click on the Start menu and choose the Disk Management option in order to open its console
4. Right-click the volume with the drive letter we want to change and choose the ‘Change Drive Letter’ and ‘Paths’
5. After that, click on ‘Change’ and choose from a list of available drive letters
6. We advise not to choose letters A or B because they are reserved for floppy drives on older operating systems
7. Click on Apply and confirm any dialog boxes which may appear before closing the tool.

• Enable File and Printer Sharing in Firewall

When File and Printer Sharing is disabled in any firewall we use, problems occur with shared drives. If we are using a third-party firewall, we will have to locate the option manually.

However, the Windows Defender Firewall is turned on by default if there are no other firewalls installed. The step we follow is given below:

1. Start Control Panel by searching for the utility in the Start button or by clicking the Search button or the Cortana button at the left part of taskbar
2. Once open, change the view to Large or Small icons and navigate to the bottom in order to open the Windows Defender Firewall
3. Click on Windows Defender Firewall and click on the ‘Allow an app’ or ‘feature through Windows Firewall’ option from the left side list of options
4. A list of installed apps should open. We make sure to click the Change settings button at the top right part of the window and provide administrator permissions if needed
5. Navigate to the File and Printer Sharing option and check the box right next to it before clicking OK and applying the changes
6. Click OK and restart computer before retrying to see if the error still appears.

• Make Sure There is Enough Space on the Server

This problem also occurs if there is no enough space on the server computer of the network we are a part of. We make sure to free enough space on the root drive of the server by deleting everything unnecessary.

There is no exact amount that needs to be freed, but we make sure to leave at least a couple of gigabytes available before checking if the problem is resolved.

• Changing the value of ProtectionMode in Registry

If none of the above methods work, we will attempt at changing the value of ‘ProtectionMode’ through the registry for Windows 10.

The ProtectionMode workaround is officially recognized by Microsoft itself and this error usually occurs in non-administrative users who are upgrading from an earlier version of Windows.

1. Press Windows + R, type “regedit” in the dialogue box, and press Enter.
2. Once in the registry editor, navigate to the following path:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\

3. Search for the following key: ProtectionMode
4. Now, change the key from 0 to 1.
5. Save changes and exit.
6. Restart computer and see if the issue is resolved for good.

If this workaround does not work, we manually try to delete the mappings by using the following command in a command prompt:

net use * /del /y (sub the * for an actual drive letter.)

• Reinitializing Computer Browser

In some cases, we observed that the computer’s browser causes conflicts with certain elements of the operating system. In that case, we need to restart the Computer Browser.

[Need help with the fix? We are are here for you.]

Conclusion

To conclude, ‘The Local Device Name is Already in Use’ error occurs when attempting to access a network drive, generally a mapped drive,

Today we saw a few resolutions suggested by our Support Engineers.