After updating to Windows 10 v20H2, cannot map network drives

Anonymous

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**]**

Update (2/9/2021): Last year when I posted this problem the solution that i used was to rollback to v1909, so if you're having the same problem this is still the best solution, because it was working fine until today, when on my laptop appears a message box to update windows to a newer version and since i was on my way out and was going to live the laptop on, (i keep come back to read the post but never decided to update and since there was solutions each i now know are not related to my problem), i just click update my BAD, because instead of updating me to v20H2, it updated me to v20H1 and since I was on a roll, I decided to update to v20H2 to see if this was already fixed and no the problem still exist and now I'm stuck with windows v20H2 or v20H1, the windows server is still v1809 with all updates, it's using SMBv3, since Encrypted data is on (i also tried it with Encrypted data off/SMBv2v3 and with SMBv1 ON in both client and server and i get the same network name not found error), and the client is windows 10 v20H2 and it have no mapped network drives and i just can't map any network drive i always get the same error code 0x80070043, i can use RDP, i can access my personal website, i can use FTP each is the workaround that I'm using at the moment, but i just can't map the drives i think that the problem in my case is related to some kind of authentication or secure protocol communication error used in SMB., but keep in mind that when i was using v1909 or previous versions, i had no problem with mapped drives or accessing the server with net use and there are no modifications on the server or network side, the only change is updating the client (my laptop) to a newer windows version after v1909.

So if someone has a solution or some ways of troubleshooting this please share them with me.

Thanks.

Update (2/9/2021): Finally got a solution after having 3 windows installations on the same day, that makes everyone happy, reinstall windows but keep apps and files, voila everything is like it was before and working fine again. :)

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

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.

Version 2004 STILL has problems. Please fix it Microsoft if you follow your users problems.

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

0 comments

Answer accepted by question author

Anonymous

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.

Version 2004 STILL has problems. Please fix it Microsoft if you follow your users problems.

0 comments

Answer accepted by question author

Monkey57 3,535

Win10 20H2 fixes the issue.

Previously when 2004 broke smb1, I rolled back.

There was no registry change or any other modification made to the system. After Win10 20H2 upgrade was installed via Windows Updates; SMB1 worked as it did before the upgrade.

Thank you Microsoft.

0 comments

242 additional answers

Anonymous

2021-09-13T15:18:48+00:00

No; I tried those options too and they didn't work for me. The ONLY thing that worked is what I did in my post above (from September 03).

I also tried some other useful suggestions in here, but none that suggested lowering or removing the security of my system. Those simply weren't logical options.

Also, as noted, I did no less than 3 upgrades with subsequent rollbacks until this last one "took". In each of those cases, the build number increased slightly after the OS was rolled back implying some useful changes (security and/or updates) were left behind.

To further drive this point home: With the first upgrade, even logging out and back in caused the maps to become inaccessible (though visible, with red X of course). The last one, prior to the final above, resulted in the maps showing up as accessible, i.e., no red X, but not being so.

Would upgrading like I did to the version above solve anyone else's mapping issue? I have NO idea! Maybe it's not strictly an OS upgrade issue and could be a confluence of factors working to bring about a solution. Nevertheless, I still hold Microsoft responsible for this fiasco!

All I can offer is this: Ensure your device is fully updated otherwise before attempting the OS upgrade. This includes the all-important BIOS, which you do at your own risk, rational, skill-level, and comfort.

Good luck all!
Was this answer helpful?

0 comments No comments
Anonymous

2021-09-13T17:11:30+00:00

I have found lots of variables can affect any particular system and therefore require a different solution. Trial and error is often required to find what works for you.

On the bright side, it appears as Windows 11 does not have this problem, at least in my case.

I installed the leaked version I found on the internet some time ago on a new SSD. I could map my XP drive without a problem, Once I figured out how as things have changed. I've since updated numerous times and all is still working as of version Dev Build 22454.1000.
Was this answer helpful?

0 comments No comments