Fix: Error 0x80070035 ‘the network path was not found’

This error 0x80070035 comes up when you cannot access the network resources. This is a sort of confusing error, because you may still be able to ping the resource which means, the resource is online and RDP into it, which means there is some access. But before you begin, let’s make sure that you can ping the resource to ensure that is online. After you have pinged the resource, and it is found to online follow the listed methods below and stop at the one which fixes the issue for you.

Usually, the most common reasons for this error revolve around Firewall, Anti-virus or DNS.

Method 1: Disable Firewall

Disable firewall and also disable the antivirus temporarily. After it has been disabled, go back to the Network & Sharing Center and check if you can access the resource, if not delete the share and re-add it and test. If it works, issue is your firewall which needs to be configured, if it doesn’t let the firewall stay disabled and move on to Method 2:

Method 2: Check Network Discovery

Make sure network discovery is turned on on the computer trying to access the resource.

Method 3: Reinstall Network Adapter Drivers

First, try to update your network drivers and see if that solves the issue for you, if not, then uninstall and reinstall the drivers for your network adapter. You can do so, by following the steps below.

1. Press “Windows” + “R” to open the run prompt.
2. Type in “devmgmt.msc” and press “Enter”.
3. Double click on the “Network Adapters” dropdown and right-click on your drivers.
4. Click on the “Uninstall Device” option and wait for the driver to be uninstalled from your computer.
5. Now you can either download the drivers again manually from your manufacturers’ website or click on the “Scan for Hardware Changes” option on the top to automatically reinstall these drivers.

Method 4: Check Device Manager

1. Go to Device Manager and expand Network Adapters.

2. Click view from top and select show hidden devices.

3. Look at the adapters, if you see a long list of 6to4 Adapter, right click on them and delete all of them except 1.

4. Once you have only 1 of these adapters left, reboot PC and test.

Method 5: Enable NetBIOS over TCP/IP

1. Hold Windows Key and Press R. Type ncpa.cpl and Click OK

2. Right-Click on the connection and choose Properties.

3. Click “Internet Protocol (TCP/IP) Version 4” in the list.

4. Click Properties, and then click Advanced.

5. On the Advanced TCP/IP settings windows, go to “WINS” tab.

6. Under NetBIOS setting, click “Enable NetBIOS over TCP/IP”, and then click OK.

Method 6: Using Correct IP Address Command

In some cases, if you are trying to connect to a specific IP address across the computer or are trying to connect using the hostname, you need to be sure that you are using the correct command. Make sure that you use the following command format to ensure there aren’t any miscommunications.

\\(IP  Address)\i

Method 7: Sharing Folder

It is possible that the “network path not found” error is being triggered because the network path that you are trying to access hasn’t been shared. Therefore, in this step, we will be checking the path properties to see if it has been shared on the network. For that:

1. Open the File Explorer and navigate to the location of the folder.
2. Right-click on the folder and select “Properties”.
3. Click on the “Sharing” tab and select the “Advanced Sharing” button.
4. In the advanced sharing window, check the “Share this Folder” option.
5. Now the folder will be shared and its shared network path will be displayed in the sharing tab.
6. Use this to connect to the folder and check to see if the issue persists.

Method 8: Enabling Service

There are some services that make the sharing of files on a network possible by helping the two computers communicate with each other. If these services are disabled, the network path might not be detected. Therefore, in this step, we will be enabling these services. For that:

1. Press “Windows’ + “R” to open the Run prompt.
2. Type in “Services.msc” and press “enter”.
3. Scroll down until you find the “TCP/IP Net Bios Helper” service.
4. Right-click on it and select “Properties”.
5. Set its “Startup Type” to “Automatic” and then click on the “Start” button.
6. Apply and save your changes.
7. Check to see if the issue still persists.

Method 9: Deleting Registry Folder

It is very important that you backup your registry before proceeding with this step. This step is necessary because in some cases the registry folder that we are going to be deleting is filled with incorrect or outdated configurations that prevent the network path from being found. In order to do so:

1. Press “windows’ + “R’ to open the run prompt.
2. Type in “Regedit” and press “enter”.
3. In the registry editor, navigate to the following location.

   Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

4. Right-click on the “Hardware IDs” folder on the expanded MSLicensing Hierarchy and select “Delete Folder”.
5. Confirm any prompts and then check to see if the issue persists.

Method 10: Changing Security Policies

In certain situations, the local security policies might be preventing your computer from functioning properly. Therefore, in this step, we will be opening the policy manager and then define a policy for our local security. For that:

1. Press “Windows’ + “R” to open the Run prompt.
2. Type in “Secpol.msc” and press “Enter”.
3. Select “Local Policies” from the left side and then click on the “Security Options” dropdown.
4. In the right pane, scroll down and in the last couple of rows, you should see the “Network Security: LAN Manager Authentication Level” entry.
5. Double click on this entry and then click on the next dropdown.
6. Select the “Send LM and NTLM – use NTLMv2 session security if negotiated” option from the list and click on “Apply”.
7. Check to see if the issue still exists.

Method 11: Editing Hosts File

In certain cases, you will need to edit your host file to resolve the hostnames of your machine. This host file can be found in the system 32 folder and is used by the Operating system as an instruction manual to resolve the hostnames. In order to edit the hosts file.1

1. Open the File Explorer and go to the following location.

   C:\Windows\System32\drivers\etc.

2. In this folder, right-click on the hosts file and select “Open With”.
3. Select “Notepad” from the list and then type in the “IP Address of the domain that you want to connect to followed by the domain name”.
4. Press “Ctrl” + “S” to save your changes.
5. Check to see if the issue persists.

Note: If you are trying to access the network on a Virtual Machine, try using an older boot image and check if that fixes things.

Method 12: Use SMB1

In some cases, the SMB3 protocol might be the reason behind the occurrence of this error on Windows Server. Therefore, in this step, we will be enabling the use of SMB1. For that:

1. Press “Windows’ + “R’ to open the Run prompt.
2. Type in “Powershell” and press “Shift” + “Ctrl” + “Enter” to provide administrative privileges.
3. Type in the following commands in the PowerShell to enable SMB1 and disable SMB3.

   FOR Windows Server:
   Get-WindowsFeature FS-SMB1
   Set-SmbServerConfiguration -EnableSMB2Protocol $false
   For Windows 10,8:
   Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol
   Set-SmbServerConfiguration –EnableSMB2Protocol $false
   

4. Check to see if the issue persists after executing these commands.

Method 13: Flush DNS

If all else fails, flush your DNS and go to “ncpa.cpl” in Run prompt and disable and enable your network adapter. This should fix the issue as a last resort.

1. Press Windows key once
2. Type command prompt in the search bar
3. Right-click Command Prompt from the search results and select run as administrator

   ipconfig /flushdns
   ipconfig /release 
   ipconfig /renew
   exit

4. Check to see if the issue persists.
5. If it does, press “Windows’ + “R” to open Run and type in “ncpa.cpl”.
6. Right-click on your internet adapter and select “Disable”.
7. Select “Enable” after some time and check again if the issue persists.