After updating to Windows 10 v20H2, cannot map network drives

Anonymous
2020-06-20T16:01:30+00:00

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. :)

Windows for home | Windows 10 | Internet and connectivity

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
2020-07-30T17:31:26+00:00

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

Was this answer helpful?

100+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2020-07-27T13:43:35+00:00

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.

Was this answer helpful?

10+ people found this answer helpful.
0 comments
Answer accepted by question author
Monkey57 3,535 Reputation points
2020-11-03T02:22:34+00:00

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.

Was this answer helpful?

7 people found this answer helpful.
0 comments

242 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-21T17:39:03+00:00

    I'm afraid that the W10 update goes a little deeper than just the mapping. I have a gut feeling it did something to the DNS lookup. I have Server 2016 servers that maintain the mapping just fine. My W10 clients that are running the older version of 10 are fine. But when this thing breaks, it also denies access to an IP address connection as well as a name connection.

    AT ANY RATE - Here is what I have been doing as a work around.

    ON THE DOMAIN CONTROLLER - Go to Server Manager and click on Tools and then Group Policy Management. Expand the forrest, expand domains and expand the domain name. Right click on "Default Domain Policy" and edit. Go to User Configuration/Preferences/Windows Settings/Drive Maps. In the right hand side, right mouse click and set up "New". Set up a pre-defined drive map for all users in the Domain with the following settings:

    Action: Replace

    Location: \computer hosting the share\shared folder

    Check Mark "Reconnect"

    Under Drive Letter Click on "Use" and then enter the drive letter you wish to map to. 

    Click OK. 

    ON THE WINDOWS 10 PC - I used your instructions on cleaning out the old mapped drives in the Registry. I then rebooted the PC and went back into the Registry and added the ProviderFlags.

    SO FAR - Seems to work. Still having issues on A FEW computers where the operators don't shut down the computer at night. BUT - A lot less problems than before.

    This is just a work around and NOT a solution to the problem. 

    Good Luck

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-17T17:32:58+00:00

    How I fixed the shared drives on V2004 Problem.

    This worked for me – it may not work for you.

    Description of Issue: I have 5 PC’s connected to a home network – all 5 were running Win 10 Pro V2004 or Home V2004.  1 PC (we will call the Host) had my media on it, shared to the other PCs. Prior to V2004 being installed, the other PCs each had 5 mapped drives from the Host (1 for audio, 1 for video etc.). All drives were similarly configured having sharing enabled and full control enabled. Shortly after the Host was upgraded to V2004 – all the other PCs could not connect to all the Host drives – except for one. I was told I did not have permission to access the Host drives/PC.

    Then one day the Host PC snafued my start menu. This resulted in me reinstalling Win 10 V2004 (another long story). After this I was unable to access the Host drives on any of the other PC’s. Prior to this all the PCs had local user accounts as opposed to the V2004 email-based account (ie my account was *** Email address is removed for privacy ***)

    I tried a variety of fixes I found on the internet – none of them worked.

    Solution:

    I did a clean install of V1909 on the Host. Went through the setup where I could only create an email-based account. After which, the other (V2004) PC’s could connect only to that 1 Host drive as before. What I then did was go on the Host PC and change my account to a local user account with just a signal name (e.g. Joe). After that I found that I could log into the Host PC from the other computers by choosing a different account from the logon screen and typed in just Joe and the password for the Host. After this I could was able to link to the Host PC and all the steps. I am afraid to install the V2004 upgrade on the Host PC as it is working now. I do not know if you can skip the reinstall, stay with V2004 and just change the user account to a local user account with just a signal name.

    Steps:

    1)  I searched for Win 10 V1909 64 bit iso file on the MS site – you would think they would have one – but they don’t! I ended up downloading the iso from here.

    2)  I installed the Win 10 V1909 64 bit iso file using an application called Rufus to put it on a USB drive.

    3)  Directions for creating a bootable USB Win 10 file with Rufus maybe found here. Pay attention if your PC is older and has MBR and CSM versus GPT and UEFI on newer PCs.

    4)  Install windows 10 V1909 with email-based user account.

    5)  After installation change the user account to a local user account:

    a.       Go to Settings (cog on left side of start menu)

    b.       Click on Accounts

    c. Click on Your info

    d.       Type your current Microsoft account password

    e.       Click the Next button

    f.        Type a new name for your account (e.g. Joe)

    g.       Create a new password (I used my old one)

    h.       Type a hint that will help you to remember your password

    i.         Click the Next button

    j.         click the Sign out and finish button.

    k.       Sign back into your account.

    6)  After this reboot your Host PC.

    7)  After this I was able to gain access to all the drives on the Host PC. On all the other PCs I created a shortcut to the Host PC and logged in with another User account and entered Joe and the password for the Host PC.

    a.       On the desktop, right click and select new > shortcut

    b.       Enter the \”Host PCs name”

    c.       Click Next

    d.       Click Finish

    e.       Click on this new shortcut

    f.        You will get a screen entitled “Windows Security” with the old Host PC email-based account prefilled in (i.e. *** Email address is removed for privacy ***) and no ability to change this field and prompting you for the Host PC password.  At the bottom of this Windows Security Screen in red is “The user name or password is incorrect” Click of this.

    g.       Enter the single name local user account (i.e. Joe)

    h.       Enter the password for Joe

    i.         Click OK

    j.         I had access to all the Host PC drives.

    I hope this helps somebody.

    Was this answer helpful?

    0 comments