Fix: Unable to Access Network Shares After Upgrading to 2004

Your network sharing might not work if the Function Discovery Resource Publication and Function Discovery Provider Host Services are disabled by the update. Moreover, corrupt Windows credentials or corrupt Windows installation may also cause the error under discussion.

The issue arises when the user could not access his network shares/mapped drives after the Windows Update 2004. The issue is reported on the domain as well as on a simple home/office network.

Unable to Access Network Shares After Upgrading to 2004

Before proceeding with the solutions to fix the network error, make sure “Turn on network discovery” and “Turn on file and printer sharing” are enabled. Also, check if permission for the shares is set to Everyone. Make sure the date & time of both (host and guest) systems is correct.

Furthermore, check if your network cable is not damaged. Additionally, uninstall any VPN (disabling will not work). Also, make sure the network type on both systems (host/guest) is set to private. Moreover, try to enable/disable your network adapter to rule out any temporary glitch.

Moreover, check if enabling NFS client support (in Turn Windows Features On/Off) solves the problem. Try to disable offline access if using DFS shares. Also, check if restarting the Workstation service solves the issue. Additionally, make sure if the password-protected sharing is disabled for both systems (host & guest). Last but not least have a detailed look at our article on cannot access network share after update 1709 (the methods there are still relevant like enabling insecure guest logons, enable SMB 1.0, etc.).

Solution 1: Enable the Function Discovery Resource Publication and Provider Host Services

The Function Discovery Resource Publication is the networking service responsible for the discovery of devices in a local computer network and publishing of the computer and its attached resources to the network, whereas the Function Discovery Provider Host service is the host process for Function Discovery providers. You may fail to use the network shares if the said services are disabled. In this case, enabling these services may solve the problem.

  1. Press the Windows key and in the Windows Search bar, type Services. Now, right-click on Services (in the list of results shown) and then select Run as Administrator.
    Open Services as Administrator
  2. Now, right-click on Function Discovery Resource Publication & then select Properties.
    Open Properties of Function Discovery Resource Publication
  3. Then change the dropdown of startup type to Automatic & click on the Apply/OK buttons.
    Change Start Up Type of Function Discovery Resource Publication to Automatic
  4. Repeat the same process to Function Discovery Provider Host and then check if the issue is resolved.
  5. If not, enable SMB 1.0 in the Windows feature and check if the network shares are functioning normally.

Solution 2: Enable the DNS Cache of Your System

The Windows OS stores cache files (like web browsers), called Domain Name System (DNS) cache, that contains information about all visited IP addresses, websites, hostnames, and resource records. You may fail to access network shares if the DNS Cache service (described as DNS Client) is disabled (as the system will not able to handle the DNS requests). In this case, enabling the DNS client (DNS cache) service may solve the problem.

  1. Click on the Windows button and type Services. Now, right-click Services (in the results shown) and then select Run as Administrator.
  2. Now, right-click on the DNS Client service and select Properties.
    Open Properties of the DNS Client Service
  3. Then open the startup type dropdown and select Automatic.
    Change Start Up Type of the DNS Client Service to Automatic
  4. Now, click on the Apply/OK buttons and check if you can access network shares.
  5. If you cannot change the startup type at step 3, then back up your system’s registry.
  6. Then press the Windows key and in the Windows Search bar, type Registry Editor. Now, in the results’ list, right-click on Registry Editor and select Run as Administrator.
    Open Registry Editor as Administrator
  7. In the Registry Editor, navigate to the following:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache
  8. Now, in the right pane of the window, right-click on the Start registry key and then select Modify.
    Modify the Start Registry Key of DNSCache
  9. Then, change the value to 2 and click on OK.
    Change the Start Registry Key Value to 2
  10. Now, exit the Registry Editor and reboot your system.
  11. Upon reboot, check if the network shares issue is resolved.

Solution 3: Restart the Workstation Service

  1. Launch the Services window and right-click on the Workstation service.
  2. Now choose Start or Restart (click Yes if asked to restart the dependent services) and check if the sharing is working fine. If the issue reappears after the system’s restart, repeat the same.
    Restart the Workstation Service

You can also do the same by executing the following in an elevated Command Prompt:

net stop workstation /y
net start workstation

Solution 4: Add the Credentials of the Host System to the Credential Manager

The SMB sharing issue may arise if the Credential Manager is missing the credential to access the problematic network share. In this context, adding the network-share credentials to the Credential Manager may solve the problem.

  1. Press the Windows key and in the search box, type: Credential Manager. Now select Credential Manager.
    Open Credential Manager
  2. Now steer to the Windows Credentials tab and check if the credentials of the problematic network share are shown (if not, head to step 4).
  3. If so, remove those credentials and reboot your PC.
  4. Upon reboot, steer to the Windows Credential tab of the Credential Manager (steps 1 to 2) and click on Add A Windows Credential.
    Remove and Re-Add the Network Credentials in Credential Manager
  5. Then add the credentials and check if the issue is resolved.
  6. If the issue persists, check if adding the credentials in the following format solves the problem:
    \\Your_Host_Name\Your_Shared_Folder_Name

    (along with the username and password)

If the issue is still there, you may use GPO to map the shared drive but during this process, use Create but make sure to uncheck the Reconnect option (you may use the FQDN path).  Also, check if enabling the NTLM authentication in the GPO solves the problem.

Solution 5: Delete the Credentials Stored in Windows Credential Manager and Add Back

You may fail to access the network shares if the credentials stored in the Windows Credential Manager are not wrong or corrupt (after a Windows update). In this case, removing the current credentials and then adding them back may solve the problem.

  1. Press Windows + Q keys and then in the Windows Search bar, type Control Panel. Now, in the results shown by the Windows Search, select Control Panel.
  2. Now open User Accounts and then select the Credential Manager.
    Control Panel
  3. Then switch to Windows Credentials and click on Back Up Credentials (then follow the prompts on your screen to save the credentials).
    Backup Credentials in Credentials Manager
  4. Now delete the problematic (or all) credentials and then restart your system.
  5. Upon restart, add back the credentials (do not use the backed-up credentials) and check if the issue is resolved.
  6. If not, then check if another Windows 10 system can access the problematic network shares. If so, then import the credentials from that PC to the affected PC and check if the issue is resolved.

Solution 6: Enable NetBIOS on the Windows 10 Host System

NetBIOS over TCP/IP is the networking protocol to allow legacy computer applications (that are dependent on NetBIOS API) to communicate over the modern TCP/IP networks. If your older systems (XP or Windows 7 machines) could not access the Windows 10 system, then enabling the NetBIOS over TCP/IP may solve the problem.

  1. Press Windows + Q keys to open Windows Search and type Control Panel. Now, in the results, select Control Panel.
  2. Now, open Network & Internet and then select Network and Sharing Center.
  3. Then click on Change Adapter Settings (in the left pane of the window) and in the Network Connections windows, right-click on your adapter.
    Change Adapter Settings in Control Panel
  4. Now, in the menu, click on Properties and then in the Properties window, select Internet Protocol Version 4 (TCP/IPv4) and then click on the Properties button.
    Internet Protocol Version 4 – Properties
  5. Then click on the Advanced button and navigate to the WINS tab.
  6. Now, check the option of Enable NetBIOS over TCP/IP and then click the Apply/OK buttons.
    Enable NetBIOS Over TCP IP
  7. Then restart your system and check if the network shares are working fine.

Solution 7: Reset Network to the Defaults

Any customization to your network settings/adapters or their corruption may stop the network share from working. In this context, resetting the network (which will reinstall your network adapters and set their components back to the default values) may solve the problem.

  1. Click on the Windows button and then select Settings (the gear icon).
  2. Then, select Network & Internet and click on Network Reset (near the end of the screen).
    Network Reset – Windows 10 Network Settings
  3. Now click on Reset Now button and then, after completion of reset, check if the network share issue is resolved.
    Performing a network reset

Solution 8: Re-Enable the SMB Protocols

The issue may arise if the SMB protocol is disabled on your system or your system needs a different protocol version of SMB. In this case, enabling the SMB protocol may solve the problem.

Re-Enable the SMBv1 Protocol in the Windows Features

  1. Click on the start menu/Windows button & in the Windows search bar, type: Control Panel. Then open the Control Panel.
  2. Now select Programs and click on Turn Windows Features on or off.
    Open Turn Windows Features On or Off
  3. Then uncheck the options of SMB 1.0/CIFS File Sharing Support and SMB Direct.
    Uncheck SMB 1.0/CIFS File Sharing Support and SMB Direct
  4. Now apply your changes and reboot your PC.
  5. Upon reboot, enable the SMB options (disabled at step 3) and reboot your PC. If you want to keep automatic removal of the SMB 1 protocol disabled, keep the “SMB 1.0/CIFS Automatic Removal” option unchecked.
  6. Upon reboot, check if SMB sharing is working fine.

Re-Enable SMBv1 Protocol Through the PowerShell

  1. Launch the Quick Access menu (right-click the Start menu/Windows button) and choose Windows PowerShell (Admin).
  2. Now execute the following one by one:
    Get-WindowsOptionalFeature -Online -FeatureName smb1protocol
    
    Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol
    Install SMB 1 Protocol Through the PowerShell
  3. Now reboot your PC and execute the following:
    Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol
  4. Then reboot your PC and check if the SMB sharing is working fine.

Enable the SMBv2 Protocol

  1. Launch the administrator PowerShell (as discussed above) and execute the following:
    Set-SmbServerConfiguration –EnableSMB2Protocol $true
    Enable SMB 2 Protocol Through the Command Prompt
  2. Now check if the sharing issue is resolved, otherwise reboot your system to check if sharing is working fine.
  3. If not, you may have to enable the SMBv2 protocol on the server/host-side e.g., for a Synology, navigate to the following in the Synology DiskStation Manager (DSM):
    Control Panel>> File Services
  4. Now open Advanced Settings (under SMB) and set the value of Maximum SMB Protocol to SMB2.
  5. Then set the value of Minimum SMB to SMB1 and check if the issue is resolved. If the SMBv1 is not enabled in the system’s Windows, you may set the value of Minimum SMB Protocol to SMB2 as well (make sure to enable SMB2 on the guest system).
    Set Maximum SMB to 2 and Minimum SMB to 1 in the Synology Advanced Settings

Moreover, check if disabling NFS and enabling SMB/CIFS on the host resolves the problem. You can also try Windows Discovery on a Linux server.

Re-enable SMB 2.0 (if already enabled)

You may fail to access the network shares if the SMB client on your system is not configured properly. In this case, enabling (or disabling) the SMB 2.0 client may solve the problem.

  1. Click in the Windows Search bar and type Command Prompt. Now, right-click on the Command Prompt (in the results shown) and select Run as Administrator.
  2. Then execute the following command:
    Set-SmbServerConfiguration –EnableSMB2Protocol $true
    Enable SMB 2 Protocol Through the Command Prompt
  3. Now, restart your system and upon restart, check if you can access the network shares.
  4. If not, then repeat step 1 to open elevated Command Prompt and execute the following:
    lanmanworkstation depend=bowser/mrxsmb10/nsi
  5. After the success message, execute the following:
    sc.exe config mrxsmb20 start=disabled
    Disable SMB 2.0 Protocol
  6. Now, check if the network shares are working fine.

Solution 9: Disable AutoDisconnect of the Host System

You may fail to use the network share if the host system (either Windows 10 or another version of Windows) is force disconnecting the guest connections. In this case, disabling the AutoDisconnect feature of the host system may solve the problem.

  1. Remove the network shares from the host systems and restart your system.
  2. Upon restart, click on the Windows button and then type Command Prompt. Now, in the results shown by the Windows Search, right-click on Command Prompt and select Run as Administrator.
  3. Now execute the following:
    net config server /autodisconnect:-1
    Disable Autodisconnect of the Host System
  4. Then restart your system and upon restart, share a folder over the network and then check if the network share issue is resolved.

Solution 10: Edit the System’s Registry

If the sharing issue is still there, then you may edit the system’s registry to allow the SMB sharing to work.

Warning: Advance at your own risk and with extreme care as editing the registry of your system is a proficient task and if not done properly, you may cause undying damage to your OS/PC/data.

Before proceeding, make sure to back up your system’s registry. Now press the Windows key and search for: Registry Editor. Then, right-click on the result of the Registry Editor, and in the menu shown, open Run as Administrator. Now apply the following edits and check if that resolves the issue.

Open Registry Editor as Administrator

Create a ProviderFlags Key

  1. Navigate to the following path:
    Computer\HKEY_CURRENT_USER\Network
    Delete the Mapped Drive Sub-Key under the Network Key
  2. Now delete the key pointing to the problematic share (e.g., Y) and reboot your PC after exiting the editor.
  3. Then remap the share and in the Registry Editor, navigate to the path mentioned in step 1.
  4. Now right-click on the drive letter pointing to the SMB share (e.g., Y) and choose New>> Dword (32-bit) Value.
  5. Then name the key as ProviderFlags and double-click it.
  6. Now set its value to 1 and close the editor.
    Add the ProvideFlags Key
  7. Then reboot your PC and check if the SMB sharing issue is resolved. If the issue persists, check if restarting the Workstation service (as discussed in solution 4) sorts out the problem.

Edit the Properties of the LanmanWorkStartion Service

  1. Navigate to the following path:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  2. Now, in the left pane, right-click on Parameters and choose New>>Dword (32-bit) Value.
  3. Then name it as AllowInsecureGuestAuth and double-click it.
  4. Now set its value to 1 and exit the editor.
    Create an AllowInsecureGuestAuth Registry Key
  5. Then reboot your PC and check if the SMB sharing is working fine.

If that did not do the trick, you may try the following:

  1. Press the Windows key and search for: CMD. Now, right-click on the result of the Command Prompt, and in the resulting menu, choose Run as Administrator.
    Open Command Prompt as Administrator
  2. Now execute the following:
    sc.exe config lanmanworkstation depend=bowser/mrxsmb10/nsi 
    
    sc.exe config mrxsmb20 start=disabled
  3. Then close the editor and reboot your PC to check if the SMB sharing is working normally.

If the issue persists, check if adding the affected user to a local admin group of the PC solves the problem.

Solution 11: Create a Local User Account

The network shares may not work if your user account is corrupt or you are using a Microsoft/Office 365 account (that can create some type of security issues on the shared files). In this scenario, creating a local user account and sharing (or accessing the network share) through that account may solve the problem.

  1. Create a new user account and share a folder with the network from that account.
  2. Now, check if the network shares are operating normally. If you are encountering the issue in a domain network, then try to make the domain user a member of the local administrator group and check if the issue is resolved.

Solution 12: Revert Your System to the older Windows 10 Version

If the issue persists even after trying the above solutions, then reverting your system to the older Windows 10 version when the network shares were working fine may solve the problem. This method can only be applied if you are within 10 days after applying the latest update. You may have to hide the update in the Windows update settings till the issue is resolved. If the issue started to occur after a particular Windows update, then uninstall that update.

  1. Press the Windows key and select Settings (the Gear icon).
  2. Now, select Update & Security, and then in the left pane of the window, select Recovery.
  3. Then, under the option of Go Back to the Previous Version of Windows 10, click on Get Started.
    Click on Get Started in Go back to the Previous Version of Windows 10
  4. Now, follow the prompts on your screen to revert to the older version of Windows 10.
  5. Then check if the network shares are working fine.

If none of the solutions was able to solve the issue, try to re-add the system/server to the domain (if the issue is occurring in a domain network). Moreover, keep on checking if Microsoft has issued a hotfix for the issue. Furthermore, check if you can use the IP address or FQDN in the Run command (like \\192.169.XX.XX) of the shared folder. Additionally, try to save your Samba server password (if the issue is on a Samba server) in the Windows system. Also, try to use Registry Editor to delete the mapped network (Computer\HKEY_CURRENT_USER\Network\Z where Z is your network share). Delete the entries (a, b, etc.) from the following key:

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU

Then remap the drive and add the Registry key of  [HKEY_CURRENT_USER\Network\F] “ProviderFlags”=dword:00000001 and check if the issue is resolved. Furthermore, check using DFS Share solves the issue. If the issue is still there, then try using the Net Use command (net use w: “\\network name\folder” /persistent:no).

If the issue is still there, then the issue could be a result of a corrupt Windows installation. In this case, resetting your system to the factory defaults and if the issue persists, then perform a clean install using version 2004 or higher of the Windows 10 as the bootable image, and hopefully, the network share issue is resolved.

Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.

Expert Tip

Fix: Unable to Access Network Shares After Upgrading to 2004

If the issue is with your Computer or a Laptop you should try using Restoro which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Restoro by clicking the Download button below.

Download Now

I'm not interested