Network issues after update, no access to network drives
Windows 10 clients no longer display network drives correctly in Windows Explorer, and access to NAS and servers with SMBv1 shares are no longer possible after feature update for Windows 10 version 2004 is installed.
Release to NAS and server interrupted after 2004 feature update
Network drives to Windows shares are no longer accessible after the feature update May 2020 was downloaded. With the Windows Update 2004 Build 19041.508, access is no longer possible for standard users to share and network drives who use the SMB 1.0/CIFS network protocol.
Microsoft has changed the behavior for the SMB version 1 network protocol with the Windows 10 feature update 2004. The SMBv1 network protocol is no longer considered secure, and Microsoft’s recommendation is to stop using the outdated SMB 1.0/CIFS protocol. See also – Windows 10: Unable to access SMBv1 share
The Registry Key ProviderFlags controls the recovery of network shares they use Server Message Block (SMB) version 1 when they are stored in the registry. The registry DWORD Key ProviderFlags can be add in the registry key [HKEY_CURRENT_USER\Network\] with regedit, or run the next line in a opened command prompt:
REG ADD "HKCU\Network\i" /v "ProviderFlags" /t REG_DWORD /d "1" /f
The network drive (i) is mapped to the share info on SERVER01, which uses the SMBv1 network protocol. The Key ProviderFlags is required if network drives are used that use devices with SMBv1; all network drives in the HKCU\Network branch must then be registered with the REG_DWORD ProviderFlags. The change requires a restart.
Solution: net use persistent:no
Another solution is using the /persistent:no parameter, where the network drive mapping is executed from login scripts, as by batch files on the logon server, or on a network without ADS, through a local logon script on the client. The network drives are created in the logon script using net use /persistent:no.
net time \\SERVER01 /set /y
net use * /delete /y
net use i: \\SERVER01\info /persistent:no
net use j: \\SERVER01\data /persistent:no
This example deletes all network drives before they are created, but does not permanently store the network drives in the registry, so there is no further interruption that exists with the 2004 feature update for network drives that use network shares with use the SMBv1 network protocol.