Fix Network path not found error 0x80070035 on Windows

You're sitting there, double-clicking a mapped drive or typing \\Server\Share into File Explorer, and boom — "Network path not found" with error code 0x80070035. This usually happens right after a Windows update, or when you try to connect to an older NAS or a Windows 7/8 machine from a Windows 10 or 11 PC. I've seen it dozens of times.

What's actually causing this?

The root cause is almost always one of three things:

SMB version mismatch — Microsoft disabled SMB1 by default starting in Windows 10 Fall Creators Update, and older devices (like a Synology NAS from 2012 or a Windows 7 box) still rely on it.
Network discovery or file sharing is off — Windows loves to "help" by turning these off after major updates.
Stale DNS or NetBIOS cache — Your PC remembers the wrong IP for the server.

Don't waste time messing with firewall rules or reinstalling network drivers — that's almost never the fix.

Step-by-step fix

Step 1: Enable SMB 1.0/CIFS File Sharing Support (if needed)

If the target device is older (pre-Windows 10 or a NAS from before 2015), you need SMB1. You don't need it permanently, but for the connection to establish first. Here's how:

Open Control Panel → Programs and Features → Turn Windows features on or off.
Scroll down, check SMB 1.0/CIFS File Sharing Support. Expand it and also check SMB 1.0/CIFS Automatic Removal (this lets Windows remove it later if it's not used).
Click OK, restart your PC.

One warning: SMB1 is a security risk if you expose it to the internet. Only enable it on internal, trusted networks. I had a client whose small office got hit by WannaCry because they left it on for years. Don't be that guy.

Step 2: Turn on network discovery and file sharing

Windows 10 and 11 have a nasty habit of disabling these after feature updates. Check this:

Open Settings → Network & Internet → Ethernet (or Wi-Fi).
Click your active network, set network profile to Private (not Public).
Go to Control Panel → Network and Sharing Center → Change advanced sharing settings.
Under Private, turn on Network discovery and File and printer sharing.

If you're using a workgroup (not domain), also check the All Networks section and turn off password-protected sharing if you don't need it. Half the time, this alone fixes the error.

Step 3: Flush DNS and reset NetBIOS cache

Stale entries cause the "path not found" error even when the server is alive. Run these commands as Administrator:

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int ip reset
netsh winsock reset

Restart after running them. The nbtstat -R command purges the NetBIOS name cache, which is often the culprit when you're using \\ServerName instead of \\IPAddress.

If it still fails

Try accessing the share by its IP address instead of hostname — \\192.168.1.100\Share. If that works, you've got a name resolution problem. Check your router's DHCP settings or hosts file (C:\Windows\System32\drivers\etc\hosts).

Also verify that the target device's firewall isn't blocking ports 445 (SMB) and 137-139 (NetBIOS). On a Windows server, run wf.msc and look for inbound rules that allow File and Printer Sharing.

Last thing: if you're connecting to a Linux Samba share (like on a Raspberry Pi or Ubuntu server), check that the Samba version is compatible. Modern Windows requires SMB2 or higher. On the Linux box, edit /etc/samba/smb.conf and set server min protocol = SMB2, then restart Samba.

Had a client last month whose entire print queue died because of this. Turns out their 2012-era NAS had SMB1 only, and a Windows update nuked the connection. Enabling SMB1 and flushing DNS got them back in business in 10 minutes.