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.
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.
- 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.
- Now, right-click on Function Discovery Resource Publication & then select Properties.
- Then change the dropdown of startup type to Automatic & click on the Apply/OK buttons.
- Repeat the same process to Function Discovery Provider Host and then check if the issue is resolved.
- 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.
- Click on the Windows button and type Services. Now, right-click Services (in the results shown) and then select Run as Administrator.
- Now, right-click on the DNS Client service and select Properties.
- Then open the startup type dropdown and select Automatic.
- Now, click on the Apply/OK buttons and check if you can access network shares.
- If you cannot change the startup type at step 3, then back up your system’s registry.
- 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.
- In the Registry Editor, navigate to the following:
- Now, in the right pane of the window, right-click on the Start registry key and then select Modify.
- Then, change the value to 2 and click on OK.
- Now, exit the Registry Editor and reboot your system.
- Upon reboot, check if the network shares issue is resolved.
Solution 3: 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.
- 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.
- Now open User Accounts and then select the Credential Manager.
- Then switch to Windows Credentials and click on Back Up Credentials (then follow the prompts on your screen to save the credentials).
- Now delete the problematic (or all) credentials and then restart your system.
- Upon restart, add back the credentials (do not use the backed-up credentials) and check if the issue is resolved.
- 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 4: 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.
- Press Windows + Q keys to open Windows Search and type Control Panel. Now, in the results, select Control Panel.
- Now, open Network & Internet and then select Network and Sharing Center.
- Then click on Change Adapter Settings (in the left pane of the window) and in the Network Connections windows, right-click on your adapter.
- 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.
- Then click on the Advanced button and navigate to the WINS tab.
- Now, check the option of Enable NetBIOS over TCP/IP and then click the Apply/OK buttons.
- Then restart your system and check if the network shares are working fine.
Solution 5: 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.
- Click on the Windows button and then select Settings (the gear icon).
- Then, select Network & Internet and click on Network Reset (near the end of the screen).
- Now click on Reset Now button and then, after completion of reset, check if the network share issue is resolved.
Solution 6: Enable/Disable SMB 2.0 on Your System
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.
- 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.
- Then execute the following command:
Set-SmbServerConfiguration –EnableSMB2Protocol $true
- Now, restart your system and upon restart, check if you can access the network shares.
- If not, then repeat step 1 to open elevated Command Prompt and execute the following:
- After the success message, execute the following:
sc.exe config mrxsmb20 start=disabled
- Now, check if the network shares are working fine.
Solution 7: 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.
- Remove the network shares from the host systems and restart your system.
- 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.
- Now execute the following:
net config server /autodisconnect:-1
- Then restart your system and upon restart, share a folder over the network and then check if the network share issue is resolved.
Solution 8: 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.
- Create a new user account and share a folder with the network from that account.
- 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 9: 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.
- Press the Windows key and select Settings (the Gear icon).
- Now, select Update & Security, and then in the left pane of the window, select Recovery.
- Then, under the option of Go Back to the Previous Version of Windows 10, click on Get Started.
- Now, follow the prompts on your screen to revert to the older version of Windows 10.
- 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.