# After updating to Windows 10 v2004, cannot map network drives

Hi,

How can I solve this problem after updating to windows 10 v2004 from v1909, i cannot map network drives/shares anymore, everything was working fine before the update, the shares are located in a windows server v1809.

When i try to connect the shares on map a network drive either using \\server_name\share_name or \\IP_of_the_Server\share_name using the correct domain\username and password i get a error code 0x80070043, the windows server is a domain controller and the windows 10 is a laptop that is not joined in the domain.

Thanks.

[Moderator Edit: Answers marked in this post reflect work arounds to this problem]

SUCCESS! I fixed the problem.

Using regedit I searched for my mapped XP drive, \\drive name, and deleted the 4 registry entries found after exporting them just in case.

Rebooted the PC and all is well, File Explorer works and the XP drive is gone.

Re-mapped the XP drive and I can now get to it without problems and all works as it should.

My best guess is some update screwed things up because the drive was mapped and connected when the update installed.

What was the exact keys you modified and is the fix still working?

Yes, it's still working for me.

Computer\HKEY_CURRENT_USER\Network\Z   or your drive letter, I deleted Z.

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU   and delete the entry, (a, b, etc), for your drive.

Then add the following after remapping your drive or else it will fail to connect after a reboot or shutdown.

[HKEY_CURRENT_USER\Network\Z]

"ProviderFlags"=dword:00000001

51 people were helped by this reply

·

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

SUCCESS! I fixed the problem.

Using regedit I searched for my mapped XP drive, \\drive name, and deleted the 4 registry entries found after exporting them just in case.

Rebooted the PC and all is well, File Explorer works and the XP drive is gone.

Re-mapped the XP drive and I can now get to it without problems and all works as it should.

My best guess is some update screwed things up because the drive was mapped and connected when the update installed.

18 people were helped by this reply

·

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?