ErrorFindly
0x80070035SystemMedium

Error 0x80070035 — Bad Network Path (ERROR_BAD_NETPATH) | Windows System Error Fix

Windows 11Windows 10Windows Server 2022Windows 8.1

What Does 0x80070035 Mean?

The network path was not found. The computer cannot locate the specified network resource.

Real-World Causes

  1. 1Target computer is turned off or not on the network
  2. 2Network discovery is disabled
  3. 3SMB/CIFS service is not running on the target
  4. 4Firewall blocking file sharing ports (445, 139)
  5. 5DNS or NetBIOS name resolution failure

Symptoms

  • ⚠Cannot access \\computername\share
  • ⚠Network shares disappear from File Explorer
  • ⚠Error 0x80070035 when mapping a network drive
  • ⚠Network browsing shows no computers

DIY Fix

Beginner-friendly steps you can try at home

  1. 1Verify the target computer is on and connected to the same network
  2. 2Enable Network Discovery in Network and Sharing Center
  3. 3Ping the target by IP address to verify connectivity
  4. 4Enable SMBv1 if connecting to old devices (Control Panel > Programs > Turn Windows features on/off)

Advanced Fix

For experienced users and IT professionals

  1. 1Check if TCP port 445 is open: 'Test-NetConnection -ComputerName target -Port 445' in PowerShell
  2. 2Ensure the 'Function Discovery Resource Publication' and 'Server' services are running on the target

Frequently Asked Questions

Why can I ping the computer but not access its shares?
Ping uses ICMP protocol while file sharing uses SMB on port 445. The target's firewall may allow ping but block SMB. Ensure 'File and Printer Sharing' is allowed in the target's Windows Firewall settings.
Should I enable SMBv1?
SMBv1 has known security vulnerabilities and is disabled by default in newer Windows. Only enable it if you must connect to very old devices (like old NAS units). Upgrade the target device if possible.

Related Error Codes

0x80070043Bad Network Name (ERROR_BAD_NET_NAME)0x80070039Unexpected Network Error (ERROR_UNEXP_NET_ERR)

About the Author

Windows Troubleshooting Team

Verified against official Microsoft documentation and real-world diagnostic data. Error behavior confirmed across Windows 10, Windows 11, and Windows Server.