Hi, admin! After upgrading Windows 10 to 1803 (April Update), my computer can’t access shared folders on Seagate NAS (Network Attached Storage). In addition, the list of public folders on a computer running Windows 7 is also not displayed. When I try to access any shared folder, I get an error:
Windows cannot access \\sharedNAS
Check the spelling of the name. Otherwise, there might be a problem with your network. To try identify and resolve network problems, click Diagnose.
Error code: 0x80070035.
The network path was not found.
At the same time, I can access the same shared folders from a phone or other computers running Windows 10 (not yet updated to 1803). All computers are connected to the same network through one Ethernet switch, there is also a Wi-FI access point for connection to the LAN from smartphones / tablets. The problem is clearly not connected to the network.
I’ve tried many methods described in the Internet, but nothing helps. When I try to access shared folders on a Windows 7 computer or the NAS device, I always get an error “0x80070035 Network path not found”. I can, of course, roll back Windows 10 1803 and return to the previous Windows build, but I think, sooner or later it will be necessary to update. Can you advise something?
I don’t have a ready solution to your problem. Judging by the description, you use a network based on the workgroup, rather than the Active Directory domain network. I’ll try to describe the basic steps that need to be checked to fix the error 0x80070035.
First of all, you need to understand whether the problem is related to the fact that in Windows 10 1803 / 1709 the unsafe SMB v1.0 protocol is disabled by default (this protocol is widely used to access shared files and folders). If you try to access from Windows 10 1803 your NAS file storage or computer with an older Windows version (Windows XP / Windows Server 2003), which only allow access to shared files using the SMBv1 protocol, your simply doesn’t see such share.
To check if you have enabled the SMBv1 protocol in Windows 10, use the following PowerShell command:
Dism /online /Get-Features /format:table | find "SMB1Protocol"
As you can see, in this case the SMB1Protocol-Client feature is disabled.
You can enable the legacy SMB client to access network devices using SMBv1 protocol via the Control Panel (Control Panel -> Programs and Features -> Turn Windows features on or off -> SMB 1.0 / CIFS File Sharing Suport-> SMB 1.0 / CIFS Client). You can access the features installation window by running the
You can also install this component using the command:
Dism /online /Enable-Feature /FeatureName:"SMB1Protocol-Client"
After installing the SMBv1 client, you must restart the computer.
If you use anonymous access to connect NAS storage or other computers, you must enable Insecure Guest Logon policy in Windows 1803/1709. By default in these versions unauthenticated guest access to shared folders is blocked.
If your computers are in a workgroup, I strongly advise you to follow the recommendations from the article Network computers not showing in Windows 10.
In the Network and Sharing Center section of the Control Panel, verify that the private profile is used as the current profile (Private (Current profile)). Make sure that the following options are selected:
- Turn on network discovery + Turn on automatic setup of network connected devices;
- Turn on file and printer sharing.
In the All Networks section, enable the following options:
- Turn off password Protect Sharing;
- Turn on sharing.
On both computers, reset the DNS cache:
And reboot both computers.
What else is worth checking out:
- In the properties of the shared folder (at both the NTFS file system permissions level and the network share level), verify that the Everyone group has the permissions to read the contents of the folder.
- Check if the network storage is accessed by IP address. To do this, in the File Explorer, enter \\192.168.1.100 and press Enter (replace with the IP address of your network storage).
- Verify that the following services are running on your computer (open the services.msc console). Try to start these services and change startup type to the Automatic Delayed Start:
- Function Discovery Provider Host – fdPHost
- Function Discovery Resource Publication – FDResPub
- SSDP Discovery – SSDPSRV
- UPnP Device Host – upnphost
- DNS Client (dnscache)
- Try to temporarily disable the antivirus and firewall and check if the problem persists.
- Try to change (rename) the computer name in the System properties and after the reboot, check access to the resources on the network storage.
- Try disabling the IPv6 protocol in the properties of your network adapter in the Control Panel.
- Try to reset the TCP/IP network stack with commands:
netsh winsock reset
netsh int ip reset
If the problem occurs only when accessing the NAS network storage (usually Linux is used as the OS), you can save passwords for connecting to NAS in the Credential Manager (Control Panel\All Control Panel Items\Credential Manager\Add a generic credential) and in the Advanced sharing settings enable the option Use user accounts and passwords to connect to other computers.
I hope my answer will be useful, and you will restore access to your shared folders on your network.