No network drives after Windows update

0
(0)

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

Symptom

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.

Cause

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

Solution

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:

regedit_providerflags
Illustration: Registry Key ProviderFlags

The network drive (i) is mapped here to the share info on SERVER01 which uses the network protocol SMBv1. The Key ProviderFlags is only required for network drives running SMBv1. 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.

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 and the SMBv1 network protocol.

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Leave a Reply

Your email address will not be published. Required fields are marked *