- If Windows 10 can't map the network drive, this could have an extremely negative impact on your locally stored data.
- Chances are you’ve encountered the issue after updating your Windows from v1909 to v2004.
- An efficient solution to this annoying problem is to try running the 20H2 Windows version.
- You should also consider using the Local Group Policy Editor to solve this unpleasant situation.
Taking into consideration the variety of features that Windows 10 offers, we can mention mapping the network drive, which can be used with ease of access, consistency, and network setup efficiency.
However, most users reported that, after updating from v1909 to v2004, Windows 10 can’t map network drive anymore.
Thus, we can mention that error code 0x80070043 appears on users’ desktops when trying to connect the shares. This error occurs when a file is unable to map or when its name cannot be found.
Not being able to map the network drive can be very annoying. So, the present article will help you find a series of solutions that will surely support you in the best way regarding your issue.
What can I do if Windows 10 can’t map network drive?
1. Update to 20H2 version
- Open Settings.
- Click on Update & Security section.
- On the left side, select Windows Update, then click the Check for updates button.
- Look under View optional updates and click on Download and Install.
- Click on the Restart now button.
2. Add the ProviderFlags registry value
- Press the Windows + R keyboard shortcut.
- In the opened Run dialog box, type regedit and press Enter.
- Locate the following:
- Create a new DWORD (32-bit) value named ProviderFlags.
- Double click on the created value and in the Value data box, type 1.
- Repeat this action for each mapped network drive on the computer.
- Click OK, and exit Registry Editor.
- Restart Windows.
3. Use Local Group Policy Editor
- Press the Windows + R keys.
- In the opened Run dialog box, type gpedit.msc and press Enter.
- Once you’re inside the Local Group Policy Editor, select Local Computer Policy.
- Extend Computer Configuration, then click on Administrative Templates.
- Look at the right side and double-click on the System section from the shown list.
- Scroll down to Logon and double-click on it.
- Click on Exclude credential providers, then, on the left side, on policy settings.
- Checkmark the Enabled option.
- Click on Apply and then on Ok.
- Restart your computer, wait for the next startup to complete, and try to access it once again.
4. Use a Batch file
- Open Notepad.
- Copy the following lines and paste them in the opened Notepad window:
timeout /t 30and
net use z: "\\networkname\sharedfolder" /persistent:no
- Save the file as mapdrive.bat.
- Press Windows + R keys, type shell:startup in the Run dialog box and press Enter.
- Once you open the Startup folder, place the batch file mapdrive.bat or its shortcut in it.
5. Use Credential Manager
- Open Control Panel.
- Click on User Accounts.
- Select Manage your credentials.
- Click on Windows Credentials.
- Extend your Windows Credentials option, next to the name of the network computer.
- Click on Remove in order to delete the stored credentials from the particular computer or share.
- Click Yes when you’re asked if you are sure you want to permanently delete this Windows credential.
- Exit the Credential window, open This PC, right-click on the mapped drive, and then on Disconnect.
- Restart Windows and map the network drive again.
At the end of this article, we hope that at least one of our listed solutions will work for you in order to solve the Windows 10 map network drive issue.
Also, if you are interested in mapping shared resources, you can always check how to map network drives over VPN on Windows 10.
In case any of these options was useful for you, please don’t hesitate to let us know which one and comment on the section below.