Share via

Error code 0x80070035, "The network path was not found"

Hamilton 0 Reputation points
2026-05-16T23:29:22.9566667+00:00

Have 2 computers with Window Pro, a laptop and a desktop. The laptop locked up and wanted a bitlocker number which I could not find so had new windows Pro put on. Now I cannot network them as the error message comes up from both sides.

Error code 0x80070035, "The network path was not found"

Have tried everything but changing the registry : Networking Windows 11 Pro via a router involves: Both Computers

  1. connecting both to the same local area network (LAN)
  2. enabling SMB file sharing (Network discovery and File and printer sharing.)
  3. ensuring they are set to a Private network profile.
  4. Use the same user credentials on both machines for easy access, ensuring File and Printer Sharing is enabled in the Control Panel.

5.      make workgroups the same -Open APPs and Type “workgroup”-

6.      Make sure you are admin To tell if you are an administrator on Windows 10/11, check the Settings > Accounts > Your info page. If "Administrator" is listed under your username, you have access. You can also verify this by checking for the word "Administrator" in the Control Panel > User Accounts section. [1, 2, 3] Initial Setup (Both Machines)

7.      Connect to Network: Ensure both computers are connected to the same router via Ethernet or Wi-Fi and check names in router https://192.168.1.1

__8.      Set Network to Private (__Private Network relaxes firewall)-Go to Under Windows Square: Settings > Network & internet > Ethernet/Wi-Fi and select Private network.

9.      Enable Discovery: Open Control Panel > Network and Sharing Center > (View network status) Change advanced sharing settings. Under Private, turn on Network discovery and File and printer sharing.

10. Enable NetBIOS over TCP/IP: Go to Control Panel > Network and Internet Connections > (Network Connections.) Right-click your Local Area Connection, select Properties, then Internet Protocol (TCP/IP) > Properties > Advanced > WINS tab. Enable NetBIOS over TCP/IP and confirm [2].

11. enable SMB features (apps search box: turn windows on or off)

12. disabling antivirus software on private network

There is clearly something amiss-what is it?

Windows for home | Windows 11 | Internet and connectivity

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hendrix-V 15,345 Reputation points Microsoft External Staff Moderator
    2026-05-17T04:22:20.04+00:00

    Hi Hamilton,

    Thank you for sharing the details. Based on what you’ve described, this behavior is typically related to how the system or application is currently handling the configuration or connection after recent changes. While this can be unexpected, there are a few targeted workarounds you can try to restore normal functionality:

    1. Restart the affected app/service - close it completely (including background processes via Task Manager if needed), then reopen.
    2. Verify current settings again - revisit the relevant configuration page and reapply the setting to ensure it is properly registered.
    3. Test with a new profile or environment to confirm if the issue is profile-specific (e.g., create a new user/profile or test on another device).
    4. Check for pending updates - ensure both the system and the affected app are fully up to date, as newer builds may include fixes.

    If available, use a similar feature or access the function through a different interface (e.g., web vs. desktop) while the issue persists. If the issue continues after trying the steps above, it may require deeper investigation on the service side.

    Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

    At that point, I’d recommend contacting the official Microsoft support so the behavior can be reviewed further.

    I understand how frustrating it can be when something stops working as expected, especially after you’ve already tried multiple fixes. Hopefully one of the steps above helps get things back on track quickly.

    Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

  2. AI answer

    2026-05-16T23:29:44.6733333+00:00

    Error 0x80070035 indicates that Windows cannot reach the other PC over the network path. After a reinstall, some core sharing and discovery components are often disabled or misconfigured. Use these targeted checks and fixes that are supported by the context.

    1. Confirm basic access to the share by command

    On each PC, try to access the other by UNC path using net use:

    net use * \\OtherPCName\Sharename

    Replace OtherPCName with the exact computer name and Sharename with an existing share (for example, \DESKTOP\Users or a custom share). If this fails, it confirms a connectivity or sharing configuration issue rather than File Explorer only.

    For more details on net use, see Net use.

    1. Ensure SMB and discovery services are enabled

    On both PCs:

    1. Turn on SMB 1.0 client (only if needed for older devices):
      • Open Control Panel.
      • Select Programs > Programs and Features > Turn Windows features on or off.
      • Enable SMB 1.0/CIFS File Sharing Support > SMB 1.0/CIFS Client.
    2. Turn on Network Discovery and File and Printer Sharing:
      • Open Control Panel.
      • Go to Network and Internet > Network and Sharing Center > Advanced sharing settings.
      • Under Private, select Turn on network discovery.
      • Select Turn on file and printer sharing.
      • Select Save changes.
    3. Make the PCs visible on the network by enabling required services:
      • Select Start, type Services, and press Enter.
      • For each of these services, set Startup type to Automatic, then start the service if it is stopped:
        • Function Discovery Provider Host
        • Function Discovery Resource Publication
        • SSDP Discovery
        • UPnP Device Host
      • Restart the PC after changing these.
    4. Verify network profile and TCP/IP basics

    On both PCs:

    1. Confirm the network is Private:
      • Open Settings > Network & internet.
      • For Wi‑Fi: select Wi‑Fi, then the connected network.
      • For Ethernet: select Ethernet.
      • Under Network profile type, ensure Private is selected.
    2. Confirm IP configuration is valid (DHCP recommended):
      • In Settings > Network & internet, select the active Wi‑Fi or Ethernet connection.
      • Next to IP assignment, select Edit.
      • Use Automatic (DHCP) unless there is a specific need for static IPs.
    3. Use Network Reset if configuration is corrupted

    If the above settings are correct and 0x80070035 persists from both sides, reset the network stack on each PC (one at a time). This is more drastic but specifically helps when shared drives cannot be reached:

    1. Select Start, type settings, then open Settings > Network & internet.
    2. On Windows 11, select Advanced network settings > Network reset.
    3. Select Reset now > Yes.
    4. After restart, re‑connect to the network, set the profile back to Private, and re‑enable Network discovery and File and printer sharing as above.

    Note: After network reset, VPN clients or virtual switches may need to be reinstalled or reconfigured, and known networks may default to Public again.

    1. Re‑test access

    After completing the steps on both PCs:

    1. Confirm each PC can ping the other by name and IP.
    2. Use net use again to connect to the share.
    3. Then try browsing via File Explorer using \\OtherPCName in the address bar.

    If net use and UNC access start working after enabling the services and/or performing Network Reset, the original issue was a disabled discovery/sharing component or corrupted network configuration introduced during or after the reinstall.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.