ERROR_BAD_NETPATH 0x80070035

Error code 53 · HRESULT 0x80070035

WINDOWS

The network path was not found.

Also searched as: 0x80070035, error 53, the network path was not found, network error 0x80070035

Windows troubleshooting diagram: Device Manager warning and a system file scan
Windows errors: check drivers, system files and Event Viewer, in that order.

What it means

Error 53 / 0x80070035 "The network path was not found" appears when opening a shared folder or mapped drive by name or IP. Windows could not locate the computer or the SMB service on the other side. It is one of the most common home-network file-sharing errors.

Applies to: Windows 10, Windows 11

How to fix ERROR_BAD_NETPATH

  1. Check the path syntax: \\COMPUTERNAME\ShareName or \\IP-address\ShareName
  2. Ping the target by name and by IP; if only the IP works, the issue is name resolution
  3. On both PCs, set the network to Private and turn on Network discovery and File and printer sharing in Settings > Network & internet > Advanced network settings > Advanced sharing settings
  4. Make sure the Server service runs on the host and the Workstation service on the client (services.msc)
  5. Allow File and Printer Sharing in Windows Defender Firewall on the host
  6. Confirm the share still exists on the host under Computer Management > Shared Folders > Shares

Why it happens

The host is offline, name resolution fails, the network profile is Public so discovery is off, the firewall blocks SMB ports, or the share was renamed. Older NAS devices that only support SMB1 can also be unreachable from current Windows versions.

FAQ

Should I enable SMB1 to fix error 0x80070035?

Avoid it. SMB1 is insecure; update the NAS firmware to support SMB2 or SMB3 instead.

Why can I access the share by IP but not by name?

Name resolution is failing; check DNS, NetBIOS settings or add a hosts entry.

Related errors

Source: Microsoft WinError.h · fixes written and reviewed by the editors (see our editorial policy)

Last updated: