After updating to Windows 10 version 2004, mapped network drives don’t reconnect after a restart. Here are some of the symptoms you may be experiencing:
- Mapped drives that link to your NAS (e.g., Synology, ReadyNAS, etc.) or Windows 2000/XP/2003 computers do not work after upgrading to Windows 10 v2004. Remapping the drive works only for the current session. Enabling the
SMB 1.0/CIFS File Sharing supportin Windows Features dialog also doesn’t help. - As soon as the computer restarts, a red X sign appears on the mapped drive, and the drive doesn’t reconnect. The following error appears when you attempt to access the mapped drive:
Restoring Network Connections
An error occurred while reconnecting z: to \\computername\share_name
Microsoft Windows Network: The local device name is already in use.
This connection has not been restored.

- The UNC paths to network shares work correctly, but only if you haven’t already mapped a drive letter to the share. If not, the following error occurs when you access the share using the UNC path: (e.g.,
\\computername\share_name)\\computername\share_name is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
- When you try to connect to the network share using
\\servername\share_nameor\\IP_Address\share_nameusing the correct domain\username and password, you may get the error code0x80070043 - The network name cannot be found.
Many users have rolled-back Windows 10 to version 1903 or v 1909 due to the above issues.
Let’s see how to fix this issue without having to rollback Windows 10 to v1909 or v1903.

