How to Fix The network path was not found (0x80070035)
Error message
Windows cannot access \\<server>\<share>. The network path was not found. Error code: 0x80070035.
If you're seeing "The network path was not found (0x80070035)", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
Windows tried to reach an SMB file share and either couldn't resolve the name, couldn't reach the host, or the SMB service wasn't responding.
Why this happens
DNS or NetBIOS resolution failure, SMB ports blocked (TCP 445), the file share doesn't exist, or SMBv1 is disabled and the server only offers SMBv1.
Step-by-step fix
Confirm the server resolves to the right IP.
commandResolve-DnsName <server>Test SMB reachability.
commandTest-NetConnection -ComputerName <server> -Port 445List shares on the server to confirm the path exists.
commandnet view \\<server>Confirm SMB client features are enabled.
commandGet-WindowsOptionalFeature -Online -FeatureName SMB1Protocol Get-SmbClientConfiguration | Select-Object EnableSMB2Protocol
Affected products
Windows Admin
Still broken? Try these
- Temporarily try the share by IP instead of hostname (\\10.0.0.5\share) to isolate DNS.
- Check Windows Defender Firewall — File and Printer Sharing rules must be enabled on the network profile.
- If the server only offers SMBv1, modernize the server. Don't re-enable SMBv1 on clients except for short-term testing.
Related errors
Frequently asked questions
What does "The network path was not found (0x80070035)" mean?
Windows tried to reach an SMB file share and either couldn't resolve the name, couldn't reach the host, or the SMB service wasn't responding.
What causes "The network path was not found (0x80070035)"?
DNS or NetBIOS resolution failure, SMB ports blocked (TCP 445), the file share doesn't exist, or SMBv1 is disabled and the server only offers SMBv1.
How do I fix "The network path was not found (0x80070035)"?
1. Confirm the server resolves to the right IP. 2. Test SMB reachability. 3. List shares on the server to confirm the path exists. 4. Confirm SMB client features are enabled. Always test changes in a non-production environment first.
Browse more errors in Windows Admin: Fix Windows administration errors. Access denied, RPC server unavailable, trust relationship failures, Group Policy errors, and network path issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.