Fix Windows 11 Error 0x80070035: Missing Network Path

Windows 11 error 0x80070035 (“The network path was not found”) appears when your PC cannot reach a shared folder or printer on another computer. The fix is usually to enable Network Discovery and File and Printer Sharing, verify the SMB 1.0/CIFS setting, or correct the IP address you are trying to reach. Below are the exact steps to resolve it, along with the background and related details you need.

What Causes Error 0x80070035?

This error is a Windows networking failure that occurs during the SMB (Server Message Block) session setup. The client sends a request to the server, but the server never responds with an acknowledgment. Common triggers include:

• Network Discovery is off – Windows can’t see other devices on the network.
• File and Printer Sharing is disabled – even if discovery is on, sharing won’t work.
• Incorrect IP address or hostname – you might be trying to reach a device that isn’t there or has a different address.
• SMB 1.0 is disabled – some older devices still require SMB 1.0, which Windows 11 disables by default for security.
• Firewall or antivirus blocking – third-party security software can block SMB ports 445 and 139.
• Network profile set to Public – public networks block file sharing by default.

Step-by-Step Fixes (Try in Order)

Start with the most common fix and work down the list. You’ll need administrator rights for most steps.

1. Turn on Network Discovery and File Sharing
   Go to Settings > Network & internet > Advanced network settings > Advanced sharing settings. For your current network profile (Private or Public), enable Network discovery and File and printer sharing. Also check the “All Networks” section and turn on Public folder sharing if needed.
2. Set the network profile to Private
   Go to Settings > Network & internet > Wi-Fi (or Ethernet), click your connection, and set “Network profile type” to Private. Public profiles block file sharing.
3. Use the IP address instead of the hostname
   Open Command Prompt and run ipconfig on the target PC to find its IPv4 address (e.g., 192.168.1.10). Then try accessing \\192.168.1.10\share in File Explorer. This bypasses name resolution issues.
4. Enable SMB 1.0 (only if needed)
   If the target device is old (e.g., a legacy NAS or Windows 7 machine), SMB 1.0 might be required. Go to Control Panel > Programs > Turn Windows features on or off, check SMB 1.0/CIFS File Sharing Support, and restart. Only do this if you trust the network, as SMB 1.0 has known vulnerabilities.
5. Check firewall rules
   In Windows Defender Firewall, ensure “File and Printer Sharing” is allowed for Private networks. If you use third-party antivirus, temporarily disable its firewall to test.
6. Restart the SMB service
   Open Services (Win+R, type services.msc), find “Server”, right-click and choose Restart. Also check that “Computer Browser” is running if you’re on an older network.
7. Map the drive with different credentials
   If the share requires a login, try Map network drive and check “Connect using different credentials”. Use the target PC’s username and password, not your Microsoft account.

Understanding SMB and Network Paths

SMB is the protocol Windows uses to share files and printers. When you type \\computer\share, Windows resolves the computer name to an IP address (via DNS or NetBIOS), then establishes an SMB session on port 445. Error 0x80070035 means the session failed—either the target didn’t respond, the port is blocked, or the share name is wrong.

A common misconception is that the error means the shared folder doesn’t exist. In many cases, the folder exists but the network path to it is unreachable. For example, if the target PC’s firewall blocks port 445, you’ll get this error even if the share is perfectly configured.

Common Mistakes That Cause This Error

• Using the wrong network profile – leaving it on Public when you’re on a home network.
• Typing the hostname incorrectly – Windows names are case-insensitive, but typos like “\user-pcolder” vs “\user-pcoldr” will fail.
• Forgetting to share the folder – right-click the folder > Properties > Sharing > Share, and add “Everyone” or a specific user.
• Disabling SMB 1.0 on a network with old devices – modern Windows 11 disables it, but some NAS drives from 2010 still need it.
• Using a Microsoft account instead of a local account – for network shares, you often need the local username and password.

When to Try Advanced Fixes

If the basic steps don’t work, you can try deeper troubleshooting:

• Check the hosts file – ensure there’s no stale entry mapping the hostname to an old IP. Edit C:\Windows\System32\drivers\etc\hosts as admin.
• Disable IPv6 temporarily – some networks have misconfigured IPv6, which can cause resolution failures. In Network Adapter settings, uncheck IPv6 and test.
• Use PowerShell to test the port – run Test-NetConnection 192.168.1.10 -Port 445 to see if the port is open. If it fails, the problem is likely firewall or the target PC is off.
• Reset the network stack – open Command Prompt as admin and run netsh int ip reset, then restart.

Alternatives to SMB Sharing

If you can’t get SMB to work, consider these alternatives:

• Use a cloud drive – OneDrive or Google Drive can sync files without a local network.
• Use FTP – enable the built-in IIS FTP server on Windows, but it’s less secure.
• Use a USB drive – for one-time transfers, it’s simpler.
• Use a third-party tool like TeamViewer or AnyDesk – these can transfer files over the internet, not just LAN.

Frequently Asked Questions

Why does error 0x80070035 happen on one PC but not another?

It usually comes down to per-PC settings: network profile type, firewall rules, or SMB version. A PC set to Public network will block sharing, while another on Private won’t. Also, if the target PC has a different firewall vendor, it might block SMB ports.

Can I fix this without admin rights?

Most fixes require admin rights because they change network settings, firewall rules, or Windows features. If you don’t have admin, you can try using the IP address instead of hostname, but that’s often not enough.

Is it safe to enable SMB 1.0?

No, SMB 1.0 is insecure and should only be enabled temporarily to access legacy devices. Microsoft recommends keeping it off. If you must enable it, do it on a trusted network and disable it after.

How do I know if the target PC is reachable?

Ping the IP address: ping 192.168.1.10. If it responds, the network path exists. Then test port 445 with Test-NetConnection. If the port is closed, the target’s firewall is blocking.

What does “network path was not found” mean exactly?

It means Windows couldn’t establish a connection to the shared resource. The path (\computerolder) is syntactically correct, but the computer or folder is unreachable. It’s different from “access denied,” which means you reached it but lack permissions.

Related

• Mirror Android to Chromebook: Full Guide
• iPhone Stuck on Control Center? Fix It
• iPhone WhatsApp Contacts Missing: Solved