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

This error 0x80070035 occurs when you cannot access network resources. It is a somewhat confusing error because you may still be able to ping the resource, indicating that it is online, and establish a remote desktop connection, suggesting there is some access. However, before you proceed, make sure you can ping the resource to ensure that it is online. Once you have confirmed that the resource is online, follow the methods listed below and stop at the one that resolves the issue for you.

Usually, the most common reasons for this error revolve around firewalls, anti-virus software, or DNS.

error0x80070035

Method 1: Disabling the Firewall.

Disable the firewall and also temporarily disable the antivirus. Once they have been disabled, return to the Network & Sharing Center and check if you can access the resource. If not, delete the share, re-add it, and test. If it works, the issue is with your firewall, which needs configuration; if it doesn’t, keep the firewall disabled and proceed to Method 2.

Method 2: Checking Network Discovery

Ensure that network discovery is enabled on the computer attempting to access the resource.

Method 3: Reinstalling 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 “devmgmt.msc” and press “Enter.
    Type devmgmt.msc and Press Enter to Open Device Manager
  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 removed from your computer.
  5. Now you can either download the drivers manually from the manufacturers’ website, or click on the ‘Scan for Hardware Changes‘ option at the top to automatically reinstall these drivers.
    Scan for hardware changes

Method 4: Check the Device Manager.

1. Go to the Device Manager and expand the Network Adapters.

2. Click ‘View from Top’ and select ‘Show Hidden Devices‘.

Show Hidden Devices

3. Examine the adapters; if you notice a long list of 6to4 Adapters, right-click on them and delete all except for one.

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

Method 5: Enable NetBIOS over TCP/IP.

1. Hold the Windows key and press R. Type ‘ncpa.cpl‘ and click ‘OK‘.

Opening Networking Settings in Control Panel

2. Right-click on the connection, and choose Properties.

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

IPv4 Properties

4. Click “Properties,” and then click “Advanced

5. On the Advanced TCP/IP Settings window, go to the “WINS” tab.

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

Method 6: Using the Correct IP Address Command.

In some cases, if you are trying to connect to a specific IP address on the computer or are attempting to connect using the hostname, you need to be certain that you are using the correct command. Make sure to use the following command format to prevent any miscommunications.

\\(IP  Address)\i

Method 7: Sharing a Folder

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

  1. Open the File Explorer and navigate to the location of the folder.
  2. Right-click on the folder and select “Properties.
    Click on Properties in the context menu
  3. Click on the “Sharing” tab and select the “Advanced Sharing” button.
    Clicking on the “Advanced Sharing” screen
  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 if the issue persists.

Method 8: Enabling the Service

There are some services that enable file sharing on a network by facilitating communication between two computers. If these services are disabled, the network path might not be detected. Therefore, in this step, we will enable these services. To do so:

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

Method 9: Deleting the Registry Folder

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

  1. Press “Windows” + “R” to open the run prompt.
  2. Type in “Regedit” and press “Enter.
    regedit.exe
  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 within 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, local security policies may prevent your computer from functioning properly. Therefore, in this step, we will open the policy manager and define a policy for our local security. To do so:

  1. Press “Windows” + “R” to open the Run prompt.
  2. Type in “Secpol.msc” and press “Enter.
    Entering “Secpol.msc”
  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.
    Selecting the entry
  5. Double-click on this entry, and then click on the next dropdown menu.
  6. Select the “Send LM and NTLM – use NTLMv2 session security if negotiated” option from the list, and click on “Apply.
    Selecting the option
  7. Check to see if the issue still exists

Method 11: Editing the 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 System32 folder and is used by the operating system as an instruction manual to resolve hostnames. In order to edit the hosts file, follow these steps:

  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 you want to connect to, followed by the domain name.
    Opening with Notepad
  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 see if that resolves the issue.

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 enable the use of SMB1. To do so:

  1. Press “Windows” + “R” to open the Run prompt.
  2. Type in “Powershell” and press “Shift” + “Ctrl” + “Enter” to grant administrative privileges.
  3. Type the following commands into 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 the DNS.

If all else fails, flush your DNS and enter ‘ncpa.cpl’ in the Run prompt; then, disable and enable your network adapter. This should fix the issue as a last resort.

  1. Press the Windows key once.   
  2. Type “command prompt” in the search bar.
  3. Right-click the Command Prompt in the search results and select “Run as Administrator.
    Open Command Prompt 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.
    Run this in the Run dialog box
  6. Right-click on your internet adapter and select “Disable.
  7. Select “Enable” after some time, and check again if the issue persists.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

12
    RS
    Robert Souza Aug 16, 2015

    Tried all this.. still doesn’t work.. 3 Windows 10 boxes.. One lan desktop, two wireless laptops. Can see the other computers under Network.. cannot access them.

      KA
      Kama'aina Jun 21, 2016

      That’s Windows for you. I know your pain.

    MM
    Michel Merlin Apr 13, 2016

    Network gets worse at each Windows release. What was instant in Windows 3.1WG (i.e. W3.1 with the “Workgroups” extension), got often bugged in W95. In W2K it got fixed. WXP fortunately changed nothing to W2K, thus worked. Then Vista, 7, resumed and accelerated the downfall. And of course if you dare report the errors on forums you always and everywhere are “welcome” by a horde of young flat brains that all 1000 times repeat the same “help” that they obviously never tried and that never works. For instance they teach you what network and sharing are (yes, in 2016…), then they tell you to try all you have already tried dozens times, then to check your firewall etc… Totally useless.
    Versailles, Wed 13 Apr 2016 19:13:45 +0200

      KA
      K. Arrows Author Apr 13, 2016

      Thank you for the detailed analysis.

        MM
        Michel Merlin Jun 21, 2016

        Sarcasm doesn’t help in anything but recalling why, on this sort of subject exceptionally, I DON’T add analyses: they are bashed, without reading them, by self-appointed gurus and young flat brains so sure of themselves (said Darwin: “Ignorance more frequently begets confidence than does knowledge“).
        If you think my opinion is wrong, telling yours would be more useful than sarcasming others’.
        Versailles, Tue 21 Jun 2016 09:50:10 +0200

          KA
          K. Arrows Author Jun 21, 2016

          I am not charging anyone whose coming here to read the articles. Neither do i have access to any of your machines, where i can dig deep in to troubleshoot. I created this guide, with all the solutions i could find that has worked for some. If you’d like to improve this guide, i would suggest that instead of criticizing you come up with a solution and send it to me so i can amend this guide so it can help others.

      KA
      Kama'aina Jun 21, 2016

      Yes, I get this every time. Been building networks since the 90s and even to this day forums… I can empathize with you and the pitfalls of help online. Extremely useless.
      It’d help if there was reliable help out there, but the reliable help is usually met with dead-end answers.

      RA
      Rodolfo Alexandro Feb 7, 2018

      D’accord, you magnificent beast!

      MV
      Marco Vanelli Oct 28, 2022

      That’s exactly my experience with the scatterbrains at Micro$oft too.

    MG
    Mohammad Ghorbani Feb 25, 2018

    i have this problem too . but i cant resolve that . . .

    SW
    Shane Warren Author Sep 30, 2019

    Go into services.msc by typing it in run and pressing enter, Start the “Function Discovery Provider service” and set its startup to automatic. Then start the SSDP Discovery service and set its startup to automatic. Then start the TCP/IP NetBiosHelper service and set its startup to automatic as well. Do the same for UPNP Device Host. Go into search and type in turn windows features on or off. Open the first app that comes up and navigate down and check the “SMB 1.0/Cifs File Sharing Support” option and click on “OK”. Check to see if the issue persists.

    Reply
    DB
    damien brock May 14, 2020

    try Long Tool Path, This will works