Windows allows you to map network drives to skip entering the address every time you want to use it. And there are times when you get the error message “Local device name is already in use”. Most of the time, the problem occurs when there are problems with file and printer sharing settings and unassigned drive letters. Fortunately, there are a few ways you can fix the problem.
There are several causes for the error. The most common are:
- Unassigned or incorrect drive letters.
- File and printer sharing options disabled.
- Not enough space on the network server.
- Problems during the mapping process.
We have put together solutions to fix the “Local device name is already in use” error on Windows 10.
1. Assign or change the drive letter
A missing or incorrect drive letter can cause the error “Local device name is already in use” under Windows. Follow these steps to assign or change the drive letter.
Step 1: Right click the Windows start button, find Disk Management and click on it.
Step 2: When the Disk Management window opens, find the partition whose letter you want to change and right-click it.
Step 3: Choose, change drive letters and paths.
Step 4: In the next window click on Add.
Step 5: Select Assign the following drive letter and choose a preferred drive from the drop-down menu. Press OK to update the changes.
2. Re-map the network drive
The Windows system assigns specific letters to your computer drives. However, in the network mapping, the drive letters can be mixed up or assigned drive letters may be missing for the mapping. In such cases, you will need to remap the network drive to resolve the problem. Here’s how you can do it.
Step 1: Enter cmd in the Windows search bar and select the Run command option on the left.
Step 2: On the right side, click Run as administrator.
Step 3: Copy and paste this command and press Enter.
net use Z /delete
Remember to replace ‘Z’ with the partition you want to delete.
Step 4: After deleting the device name, change it by running this command.
net use Z: servershare /user:username password
Remember to use the same drive letter ‘Z’ that you want to map the drive with. Also, enter a relevant username and password for the drive you want to change.
Step 5: Restart your device and confirm that the mapping problem has been resolved.
3. Enable file and printer sharing
The error can also occur if the file and printer sharing options are disabled. To fix the error, enable the settings through the Windows Defender firewall. Here’s how you can do it.
Step 1: Enter control panel in the Windows search bar and press Enter.
Step 2: Click on System and Security.
Step 3: In the Allowed Apps window, find Windows Defender Firewall and tap the option to Allow an app or feature through Windows Firewall.
Step 4: Tap Change Settings and, if administrator permissions are required, allow them.
Step 5: Navigate to the File & Share option and check the boxes.
Complete the process by pressing OK and restarting your computer.
4. Change the value of the protection mode
Changing the value of the protection mode can also resolve the problem. You can do this with the registry editor.
Step 1: Press Windows + R keys, type regedit in the text box and press Enter to open the registry editor.
Step 2: Find this path in the next window.
Step 3: In the right pane, find ProtectionMode and double click on it.
Step 4: Change the value to ‘1’ and click OK to save.
Restart your device and confirm if the error is resolved.
5. Delete the MountPoints2 key
Deleting some registry keys could fix the mapping problems in your system. This is how you can delete the MountPoints2 key.
Step 1: Press Windows + R keys to launch the Run dialog box, type regedit and press Enter to open the registry editor.
Step 2: Find this path in the next window.
Step 3: Right click on MountPoints2 and choose Delete. Confirm the dialog boxes that may appear and restart your system.
Correct the local device name
These solutions should help you resolve the “Local device name is already in use” error on Windows 10. Keep in mind that insufficient disk space on the server can also lead to this error. To fix memory problems, add additional memory or free up space on the server. Remember that updating your system is also another easy way to fix the error.