I know this error makes you want to throw your router out the window.
You're trying to access a shared folder on another PC or an old NAS drive, and Windows just spits back “Network Path Not Found” with error code 0x80070035. It's one of the most frustrating errors on Windows 11, and it's almost never your network cable or Wi-Fi. It's a protocol mismatch or a permissions hiccup. Let's fix it.
The Fastest Fix: Enable SMB 1.0/CIFS File Sharing Support
This is the #1 culprit, especially if you're connecting to an older device like a Synology NAS set to SMB1 or a Windows 7 machine. Windows 11 disabled SMB1 by default for security reasons, but lots of legacy devices still use it. Here's how to turn it on:
- Press
Win + R, typeoptionalfeatures.exe, and hit Enter. - Scroll down to SMB 1.0/CIFS File Sharing Support and check the box.
- Click OK and restart your PC.
After the reboot, try accessing the network share again. For most people, this solves it instantly.
Why this works
Modern Windows defaults to SMB3 for security and speed. But if the device you're connecting to only speaks SMB1 (common on older NAS firmware or XP-era machines), your PC sends a handshake that the other side can't understand. It's like two people speaking different languages—no wonder the path “doesn't exist.” Enabling SMB1 lets your PC talk to those older devices.
If That Doesn't Work: Turn On Network Discovery and File Sharing
Sometimes the fix is even simpler—your network profile is set to “Public” and Windows is blocking discovery. Here's how to check:
- Open Settings > Network & Internet > Ethernet (or Wi-Fi).
- Click your connection and set the network profile to Private.
- Go to Control Panel > Network and Sharing Center > Advanced sharing settings.
- Turn on Network discovery and File and printer sharing for the current profile.
Try connecting again. This is a common stumble when you've recently reconnected to a new router.
Still Seeing the Error? Enable SMB Direct or Check Credentials
If you're on Windows 11 Pro or Enterprise, you might need to turn on SMB Direct (RDMA). Go to Settings > Apps > Optional features > Add a feature and search for SMB Direct. Install it. This is more of a performance feature, but it can reset the SMB stack.
Also, verify your login credentials. Windows caches old passwords—sometimes permanently. Go to Credential Manager (search “credential” in the Start menu) and under Windows Credentials, remove any entries for the target IP or computer name. Then try re-connecting and re-entering the password.
Less Common Variations and Their Fixes
1. The error appears only when using an IP address
Try using the computer name instead of the IP, or vice versa. DNS issues can cause the path to be unreachable even though the device is alive. For example, use \\SERVERNAME\share instead of \\192.168.1.50\share.
2. The error occurs on a mapped drive after a Windows update
Windows 11 recently tightened SMB signing requirements in some builds. If you've mapped a network drive that worked before, open PowerShell and run:
Set-SmbClientConfiguration -RequireSecuritySignature 0This disables mandatory signing, which can break older NAS drives.
3. The error happens only when accessing the device from a specific user account
Check if the target device has the account set to “Guest only.” On Windows 11, you can force guest access by going to Local Security Policy > Security Options > Network access: Sharing and security model for local accounts and setting it to “Guest only.” But that's a quick test, not a permanent solution.
4. The error is intermittent
This could be a firewall on the target machine blocking port 445 after a timeout. Check Windows Defender Firewall settings and make sure the “File and Printer Sharing” inbound rule is enabled. Also, make sure the target PC isn't going to sleep—check the power plan settings.
Preventing This From Happening Again
Here's the real lesson: keep your network stack clean. If you're connecting to modern gear, leave SMB1 off—it's a security risk. Instead, update the device firmware (NAS, router, etc.) to support SMB3. For Windows 10/11 machines, keep network discovery on and set your network profile to Private. And if you ever change passwords on the host PC, update the stored credentials on your client—Windows loves to cache stale ones.
One last tip: if this error suddenly appears after a Windows update, check the Windows Update history. Sometimes a patch re-enables SMB signing or resets network settings. Rolling back the update might be your fastest fix, but usually turning on SMB1 or adjusting the signing config as shown above does the trick.
You've got this. Go share a file.