Fixes / Windows · Checked September 30, 2026

Windows error 0x80070035 "network path was not found": fix it

Short answer

Error 0x80070035 means your PC could not reach the shared folder over SMB, the file sharing protocol, on TCP port 445. The name may not resolve, the host may not be sharing, or Windows may be blocking the connection. First, open the share by IP address, for example \\192.168.1.20\Share. If that also fails, turn on File and printer sharing on the PC that hosts the folder.

What this message means

Windows returns 0x80070035 when it tries to open a UNC path such as \\PCNAME\Share and cannot set up an SMB session with that device. The folder may exist and the device may be switched on. The code only says Windows could not use that path. The usual reasons are a name that does not resolve, a host PC with sharing turned off or port 445 blocked by a firewall, or a security default in newer Windows versions. For example, Windows 11 24H2 Pro, Enterprise and Education require SMB signing by default, and older NAS drives or routers that allow only guest access fail with exactly this error.

Common causes

Cause	How to tell
The computer name does not resolve, or the path is typed wrong	\\PCNAME\Share fails but \\192.168.x.x\Share works, or running ping PCNAME in Command Prompt says "could not find host".
File and printer sharing is off on the PC that hosts the folder, or its network is set to Public	Every other PC fails to connect to this one host. On the host, Settings shows the network profile as Public, or Advanced sharing settings shows File and printer sharing turned off.
A firewall or security suite on the host is blocking TCP port 445	Test-NetConnection -ComputerName HOST -Port 445 in PowerShell returns TcpTestSucceeded : False even though ping by IP works.
A NAS, router USB drive or Samba device that allows only guest access, blocked by the SMB signing or insecure guest logon defaults	The error appeared after moving to Windows 11 24H2 or a new PC, the target is not a Windows PC, and Windows PCs on the same network can still reach each other. Event Viewer may show event 31017 under Applications and Services Logs\Microsoft\Windows\SMBClient\Security.
A required Windows service is stopped	In services.msc, the Server service is stopped on the host, or the Workstation service is stopped on your PC.
The target device supports only SMB1, which newer Windows versions do not install	The device is old (an older NAS, media player or printer), and Event Viewer shows event 32000 ("SMB1 negotiate response received from remote device when SMB1 cannot be negotiated").

How to fix it

1. Check the path and try the IP address instead of the name

Make sure the path uses backslashes and the share name, not just the drive letter or local folder path: \\COMPUTERNAME\ShareName.
On the host PC, open Command Prompt, run ipconfig, and note the IPv4 Address.
On your PC, press Win + R, type \\IP-ADDRESS\ShareName (for example \\192.168.1.20\Documents), and press Enter.
If the IP works but the name does not, it is a name resolution problem. Use the IP address, or run ipconfig /flushdns and restart both PCs.
To confirm the share name exists, run net share on the host PC. It lists every shared folder by its exact name.

2. Turn on network discovery and file sharing on the host PC

Windows 11 22H2 and later: Settings path. Windows 10: Control Panel path.

On the PC that shares the folder, set the network to Private. On Windows 11 go to Settings > Network & internet > Wi-Fi or Ethernet > your network > Network profile type > Private. On Windows 10 go to Settings > Network & Internet > Status > Properties > Private.
Windows 11: go to Settings > Network & internet > Advanced network settings > Advanced sharing settings and turn on Network discovery and File and printer sharing under Private networks.
Windows 10: go to Control Panel > Network and Sharing Center > Change advanced sharing settings, expand Private, and select Turn on network discovery and Turn on file and printer sharing. Then click Save changes.
Right-click the folder, choose Properties > Sharing > Advanced Sharing, and confirm Share this folder is checked.
Try the path from the other PC again.

3. Check that port 445 is reachable and the SMB services are running

On your PC, open PowerShell and run: Test-NetConnection -ComputerName HOST-IP -Port 445
If TcpTestSucceeded is False, go to the host PC and open Windows Security > Firewall & network protection > Allow an app through firewall. Make sure File and Printer Sharing is checked for Private.
If a third-party antivirus or firewall is installed on the host, allow File and Printer Sharing or port 445 in it, or pause it briefly to test.
Press Win + R, type services.msc and press Enter. On the host, the Server service must be Running. On your PC, the Workstation service must be Running. Set both to Automatic.
Also set Function Discovery Resource Publication to Automatic (Delayed Start) on the host so it shows up under Network in File Explorer.

4. Save the host's username and password in Credential Manager

Open Control Panel > Credential Manager > Windows Credentials.
Remove any old entry for the host name or IP address.
Click Add a Windows credential. Enter the host name (or IP), plus a username and password for an account on the host PC. For a Microsoft account, use its email address and password, not the PIN.
Alternatively, run in Command Prompt: net use \\HOST\ShareName /user:HOST\username. It prompts for the password and shows a more specific error if it fails.

5. For a NAS, router drive or Samba share: turn on a user account or SMB signing on the device

Windows 11 24H2 and later Pro, Enterprise and Education (SMB signing required by default). Insecure guest logons are blocked by default on Windows 11 Pro and Windows 10 Enterprise and Education.

Preferred fix: in the NAS or router admin page, create a user with a password, turn off guest or anonymous-only access, and turn on SMB2/SMB3 and SMB signing if offered. Update the device firmware.
Connect with that user (see the Credential Manager fix above).
Only if the device cannot do this: open gpedit.msc and go to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Set Microsoft network client: Digitally sign communications (always) to Disabled.
Then go to Computer Configuration > Administrative Templates > Network > Lanman Workstation and set Enable insecure guest logons to Enabled.
On Windows 11 Home (no gpedit), run in an admin PowerShell: Set-SmbClientConfiguration -RequireSecuritySignature $false and Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force. Microsoft advises against both because they expose you to spoofed servers, so use them only on a trusted home network.

6. Reset networking as a last resort

Windows 11: Settings > Network & internet > Advanced network settings. Windows 10: Settings > Network & Internet > Status.

Open Network reset from the path above and select Reset now, then Yes.
After the restart, set the network back to Private and turn on Network discovery and File and printer sharing again.
If the target is an old device that supports only SMB1, replace it or update its firmware. Re-enabling SMB 1.0/CIFS Client under Turn Windows features on or off works, but Microsoft strongly recommends against it.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

Run net use \\HOST\ShareName in Command Prompt and note the System error number, because it is often more specific than 0x80070035 (for example 53, 67 or 1326). Also look in Event Viewer under Applications and Services Logs > Microsoft > Windows > SMBClient > Security for events 31017, 32000 or signing errors. At work, Group Policy likely controls SMB signing and guest access, so give those details to your IT department rather than changing the policies yourself. For a NAS or router, the manufacturer's support can confirm whether the firmware supports SMB2/3 with signing.

Questions people ask

Why did 0x80070035 start after a Windows 11 update?

Windows 11 24H2 Pro, Enterprise and Education require SMB signing by default and block guest-only connections. NAS drives and router USB shares that rely on guest access then fail with 0x80070035. Setting up a username and password on the device is the safe fix.

I can ping the other PC, so why is the network path not found?

Ping only proves the PC is on the network. File sharing uses SMB on TCP port 445, which the firewall or disabled file sharing can block even when ping works. Test it with Test-NetConnection -ComputerName IP -Port 445.

Should I turn on SMB 1.0 to fix it?

Only if the target device supports nothing newer. SMB1 is not installed by default in Windows 11 and has known ransomware risks. Updating or replacing the device is the better fix.

Does it matter whether my network is Public or Private?

Yes. On a Public profile Windows turns off network discovery and file sharing, so the host PC refuses incoming connections. Set the host's network to Private.

Why does it work with the IP address but not the computer name?

Your PC cannot resolve the name to an address, which is common on home networks without a local DNS server. Use the IP address, or give the host a reserved IP in your router and map the drive to that.

Sources

Related errors