8 Ways To Fix The Local Device Name Is Already In Use Error In Windows

Usually this is a problem for people trying to connect to a network, and can be caused by a number of variables. However, it’s usually due to a conflict between the connection type you selected when you created the network driver and the network you’re trying to access. Fortunately, there are some proven solutions that we’ll discuss in this article.

What Causes “The Local Device Name is Already in Use” Error in Windows?

Before diving into how to fix “The local device name is already in use” error, you should know what causes this error so that you can easily prevent it.

You are using a different type of connection than the one you use to create the network drive: There should not be a conflict between the connection type used to create a network drive and the one you are using to access it, so if you created the network drive using a local area network (LAN) and are attempting to connect to the file server using a Remote Access Service (RAS), this error will undoubtedly occur. A problem with file and printer sharing settings: If file and printer sharing is disabled in Windows Firewall, connecting to network drives will often result in errors like this. Unassigned drive letter: This error is displayed when the drive letter used conflicts. Network server with full disk space: Insufficient disk space is another possible reason for this error, as some users who experienced this error were able to resolve it by freeing up disk space on their network server.

In addition to all these factors, network mapping issues created by corrupted files and other issues can also lead to this error. But based on all these cases, we’ll examine various solutions to fix the error below.

Fix The Local Device Name is Already in Use Error on Windows 11/10

When you try to access a network drive, you may receive the error “the local device name is already in use”. Keep in mind that the above reasons for this error lead to different solutions, so you may have to try a few before you find the solution that fixes the problem.

Fix 1. Disconnect the Existing Network Drive and Remap it with Command Prompt

The first thing you should do is disconnect and remap the drive using the command prompt. This will rule out the possibility that network mapping problems caused the error.

Press Windows + S to open the Windows search bar and type command prompt.
In the menus that appear, tap Run as administrator to open Command Prompt as administrator.
Copy and paste the command below into the Command Prompt and press Enter. net use F /delete

Make sure you replace “F” with the drive you want to delete 4. When you see that the drive has been successfully deleted, copy the following command to the Command Prompt and press Enter. net use F: \server\share /user:username password

Make sure that you change “F” to the desired drive letter. Also, replace the “username” and “password” part of the command with your network username and password. After that, you can check the mapped network drive and see if the issue has been fixed. Please note that Microsoft’s official resolution for the Restoring Network Connections error is to remap the drive.

Fix 2. Restart Computer Browser

Another method to fix this error is to restart the computer browser service, because a failure of this service can cause the error “the local device name is already in use”.

Press Windows + S, type cmd in the search box, and select Run as administrator.
Tap Yes at the prompt that appears.
After the command prompt opens, type the following command and press Enter. net stop “Computer Browser”.
After the command is executed, type the command below and press Enter. net start “Computer Browser”. You should check if the problem is solved after this solution.

Fix 3. Change or Assign a New Driver Letter

A drive with no letter or a drive letter that is different from the one in the network mapping in Windows Disk Management are two other possible causes of this problem. In this case, you should assign the drive letters correctly or change the drive letter by following the steps below:

Press Windows + R to open the Run command box.
Type diskmgmt.msc in the box and press Enter to open Disk Management.
Right-click the disk you want to make changes to and select Change Drive Letters and Paths from the drop-down menu that appears.
Click Add to assign a new drive letter, or tap Change to change the drive letter for a drive that has a different letter than the one in the network mapping.
Now choose from the list of available drive letters, but make sure you do not choose A or B.
Click Apply and confirm any prompts that appear on the screen before closing the dialog.

You must enable the file and printer sharing setting in your firewall for your computer’s shared drives to work properly. To do this:

Press the Windows + R key combination, type Control Panel in the Run box, and press Enter.
In Control Panel make sure that the “Show by” option in the upper-right corner of the window is set to “Large icons“, then navigate to Windows Defender Firewall and open it.
Click Allow an app or feature through Windows Defender Firewall.
Then tap Change settings in the upper-right corner of the page.
Go to the File and Printer Sharing option and check the box under the Private section.
Click OK to save the changes and restart your PC afterward.

Fix 5. Delete MountPoints2 Key in Windows Registry

If the above solutions didn’t resolve the “The local device name is already in use” message, deleting the MountPoints2 key is another solution you should try.

Press Windows + R to open the Run Command box.
Type regedit in the field and press Enter.
Navigate to the Explorer key using the following path: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer
Under the Explorer key, right-click MountPoints2 and select Delete.

Fix 6. Change ProtectionMode Value in Windows Registry

Using the Windows registry, you can fix this problem by changing the value of ProtectionMode.

Press Windows + R to open the Run Command box.
Type regedit in the field and press Enter.
In the Registry Editor window, navigate to the Session Manager key by following the path below: http://hkey_local_machine/System/CurrentControlSet/Control/SessionManager/
In the right window, locate the ProtectionMode option, right-click on it and select Modify.
Change the value to ‘1’ and tap OK to save the changes.

After this solution, restart your computer and check if the error has disappeared.

Fix 7. Update Windows

If you are using an outdated version of Microsoft Windows (be it Windows 10 or Windows 11) on your computer, there may be a problem with the version that leads to this error. Therefore, it is recommended that you update Windows on your computer by following these steps:

Press Windows + I to open the settings on your computer.
Select Windows Update from the left pane and click Check for Updates.
If updates are available, click Install Now. After Windows Update, restart your computer and test your network drive if the problem is resolved.

Fix 8. Create Enough Space on the Network Server

Some Microsoft Windows users who experienced this error were able to fix it by creating enough free space on the root drive of their network server. So if you are running low on disk space, you should free it up to see if that fixes the error.

The Local Device Name is Already in Use Error: Final Words

Fixing the “the local device name is already in use’ error is quite easy with the above solutions. In most cases, this error can be fixed by disconnecting and remapping the network drive. Also, make sure that you access the network drive with the same connection type that was used to create it to fix this issue.