[Fix] Mapped Network Drives don’t work in Windows 10 v2004 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 (eg., 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.@/CIFS File Sharing support in 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. Restoring Network Connections x [An ertor occurred while reconnecting z: to \\desttop-skitaSa\lnvestment Tips Microsoft Windows Network: The local device name is already 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 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. Open Folder x 8 ypeainenyshuel is not accessible, You might not have permission to use this network resource. Contact the administrator ofthis server to find outif you have access permissions. Mutkiple connectionsto 2 server or shared resource by the seme user, using morethan one user name, are not allowed. Disconnect all previous connections to theserver or shared resource and try again, * When you try to connect to the network share using \\servername\share_name or \\IP_Address\share_name using the correct domain\username and password, you may get the error code @x80070043 - 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.RELATED: Windows 10 forgets stored credentials or passwords in Outlook, Edge, Chrome, ete Fix: Mapped Network Drives Don’t work in Windows 10 v2004 There are several fixes or workarounds for this issue. On my systems, | had to remove the Windows credentials for the target computer using the Credential Manager. Then, | remapped the drives, typed in the username and password for the network share. That did the trick on my Windows 10 v2004 systems. Reset the stored credentials using Credential ManagerRemoving the stored username & password for the network share, and then remapping the network drive helps in some cases. 1. Open Control Panel + User Accounts + Credential Manager 2. Select Windows Credentials 3. Under Windows Credentials, click the chevron next to the name of the network computer (or NAS) that hosts the share.Control Panel > Use Accounts > Credential Manager - Manage your credentials View and delete your saved lagon information for websites, connected applications and networks Qype Bi vrinctntn Back up Credentials. Restore Credentials Windows Credentials Adda Windows credential DESKTOP-iKMG5Q Modified: 4/22/2019 Internet or network address: DESKTOP-IKJ4G5Q Use name: BackupUser Password: Persistence: Enterprise dit Remove Cetificate-Based Credentials Add a cetifcate-based credential No cettificates, 4, Click Remove to delete the stored credentials of that particular computer or share. 5, When the Delete Windows Credential dialog appears asking, “Are you sure you want to permanently delete this Windows credential?”, click Yes to continue 6. Exit the Credential Manager window. 7. Open This PC and disconnect the mapped drive.osc) Local Disk (0:) a Rae 116 G8 free of 14968 = re) 1 ¥ Network locations (1) Investment Tips — + N\desktop-hi4oSq) 2) Open 3S Openin new window Pinto Quick access Ey Scan with Microsoft Defender. Restore previous versions Inchice in ibrary > Pinto Start Copy Create shortcut Rename Properties 8 Restart Windows. 9. Map the network drive again, with the Reconnect at sign-in option enabled. 10. Restart Windows to check if the drive mapping works. That should fix the problem. If not, follow the next procedure. Add the “ProviderFlags” registry value Adding the ProviderFlags (DWORD 32-bit) registry value and set its data to 1 helps some users, especially if your mapped network drive points to an old SMBV1 share. Follow these steps: 1. Right-click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey:HKEY_CURRENT_USER\Network\[drive letter] Note: The [drive letter] placeholder represents the mapped drive. 3. Create a new DWORD (32-bit) value named ProviderFlags 4, Double-click ProviderFlags value. In the Value data box, type 1 BE Registry Estar File Edit View Favorites Help Computer HKEY, CURRENT. USER\WetwerkZ TH Computer AT] Name Type Data Gy Hkey_cLasses ROOT at] (Default) [Link] (value not set) va eee B8)ConnectFlage REG WORD 000000000 (0) sane moo cemee Cooetl es Defer REG DWORD _0,00)00004 Environment B)ProviderNeme [Link] Microsoft Windows Network eupc 2 Kapboseiiajoit 8 Providerlype —REG_DWORD 0x00020000 (131072) Microsoft ab)RemotePath —-[Link] \ \desktop-jkde5c\lnvestment Tips Network s)UseOptions _REG,BINARY 44.65 66 43 7 00 0 00 040077400 00 00 02 C0 03 00 atjUserName ——REG.SZ_——_VOSTRO-3470\BackupUser Printers 5, Repeat the above procedure for each mapped network drive on the computer. 6. Click OK, and exit Registry Editor. 7. Restart Windows. See if the mapped network drive persists across reboot. Credits to user LeeB 1430 for the above fix.