Question / Problem
We are experiencing difficulty with a mapped drive on one desktop that will not persist after a restart. We have five desktop computers that require a mapped drive to another desktop, However, the mapping on one desktop does not persist after a restart. The error received once rebooted.
The detailed error message is as below:
Restoring Network Connections
An error occurred while reconnecting X: to XXX
Microsoft Windows Network: The local device name is already in use.
This connection has not been restored.
We have attempted to resolve the issue by enabling File/Print Sharing in the firewall, yet this has not resolved the issue. Are there any other suggestions for how to resolve this issue?
Answer / Solution
Step 1: Go to Control Panel > Credential Manager.
Step 2: Delete saved credentials in Windows Credentials that might related to the server.
Step 3: Delete corresponding registry items from:
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2
- HKEY_CURRENT_USER\Network
Step 4: Open the command prompt with run as administrator option, execute the following command line:
net use H: /deleteStep 5: Restart and try mapping again.
The solution steps outlined above may be used to address the following issues:
- Windows mapped drive not reconnecting after restart
- How to fix mapped drive not reconnecting error in Windows
- Windows network drive not reconnecting on startup
- Mapped drive disconnects after Windows restart
- Fixing network drive mapping issues in Windows
- Windows mapped drive won’t reconnect on startup
- How to prevent mapped drive from disconnecting on restart
- Troubleshooting Windows mapped drive connection errors
- Restoring lost mapped drives in Windows after restart
- Reconnecting network drives automatically in Windows