🌐 Network Sharing Error

Fix Error 0x80070035 Network Path Not Found

📅 Updated: Jan 12, 2026 ⏱️ 10-30 min to fix ✅ 93% Success Rate

🚀 Quick Fix Summary

Problem Type: Windows Network Error 0x80070035

Common Symptoms: "Windows cannot access \\computer\share", "The network path was not found", shared folders won't open, network drives disconnect randomly, "Check the spelling of the name" error

Primary Causes: Network discovery disabled (32%), firewall blocking SMB (28%), incorrect network profile (18%), NetBIOS over TCP/IP disabled (12%), outdated network drivers (10%)

Time to Fix: 10-30 minutes

Difficulty: Easy to Moderate

Success Rate: 93% with network discovery and firewall configuration

Windows network error 0x80070035 with system message "The network path was not found" or "Windows cannot access \\[ComputerName]\[ShareName]" is a network connectivity and file sharing error that prevents Windows 10, Windows 11, Windows 8, and Windows 7 systems from accessing shared folders, network drives, or network-attached storage (NAS) devices on local area networks (LAN) when attempting to browse network resources through File Explorer's Network section, map network drives using UNC paths (\\server\share), or access shared printers and files on other computers, manifesting when users type network paths like \\DESKTOP-PC\SharedFolder in File Explorer's address bar receiving immediate "The network path was not found - Error code: 0x80070035" messages even though target computer is powered on and connected to same network, attempt to access previously working network shares finding them suddenly inaccessible with "Check the spelling of the name. Otherwise, there might be a problem with your network" error messages despite correct spelling and working network connection, try mapping network drives through "Map network drive" wizard which fails at final step with 0x80070035 preventing permanent drive letter assignments to frequently accessed network locations, or experience intermittent network share access where connections work briefly after computer restarts but fail again within minutes or hours with recurring 0x80070035 errors requiring constant troubleshooting, affecting home users unable to access shared media libraries, documents, or backup folders stored on other household computers or NAS devices, small business employees experiencing productivity loss when network file servers become inaccessible preventing access to critical business documents and shared resources, IT administrators troubleshooting widespread 0x80070035 errors across corporate networks after Windows Updates or Group Policy changes, remote workers connecting through VPN unable to access company file shares with persistent network path errors, and users with mixed Windows versions (Windows 7, 10, 11) on same network encountering compatibility issues where newer Windows 11 systems cannot access older Windows 7 shares due to SMB protocol version mismatches and security policy conflicts causing 0x80070035 errors that require careful network configuration and protocol adjustments to resolve.

Error 0x80070035 (ERROR_BAD_NETPATH in Windows Error Codes) originates from multiple network configuration and Windows file sharing service failures with disabled network discovery being the most common cause (32% of cases)—where Windows' network discovery feature responsible for detecting and displaying other computers on local network is turned off in Network and Sharing Center settings, preventing Windows from broadcasting its presence via SSDP (Simple Service Discovery Protocol) and WS-Discovery protocols and from detecting other computers' broadcasts, causing File Explorer's Network section to appear empty and direct UNC path access attempts to fail with 0x80070035 as Windows cannot resolve computer names to IP addresses without network discovery's name resolution services—followed by Windows Firewall or third-party firewall blocking SMB (Server Message Block) protocol used for Windows file sharing where firewall rules block TCP ports 445 (SMB), 139 (NetBIOS Session), and 137-138 (NetBIOS Name Service) preventing file sharing traffic from reaching destination computers even though network connectivity exists for other services like web browsing and email (28%), incorrect network profile configuration where Windows network is set to "Public" profile instead of "Private" profile causing Windows to apply restrictive security policies that disable file and printer sharing features, prevent network discovery, and block incoming SMB connections as security measure for untrusted public networks like coffee shop WiFi (18%), NetBIOS over TCP/IP disabled in network adapter settings where NetBIOS name resolution service required for resolving computer names to IP addresses in workgroup environments is turned off preventing Windows from translating \\COMPUTERNAME paths to actual IP addresses causing "network path not found" errors even though IP-based access (\\192.168.1.100) may still work (12%), and outdated or corrupted network adapter drivers where buggy network card drivers cause intermittent packet loss, protocol negotiation failures, or SMB handshake problems preventing reliable network share connections (10%). This comprehensive guide provides 6 proven methods to fix Windows error 0x80070035: enabling network discovery and file sharing in Network and Sharing Center, configuring Windows Firewall to allow File and Printer Sharing, changing network profile from Public to Private, enabling NetBIOS over TCP/IP in network adapter settings, updating network adapter drivers, and resetting network settings to defaults—ensuring you can successfully access network shares and mapped drives, restore connectivity to NAS devices and file servers, resolve intermittent network path errors, enable seamless file sharing between Windows computers on home and office networks, and maintain stable network resource access without recurring 0x80070035 failures.

Method 1: Enable Network Discovery and File Sharing

Network discovery disabled prevents computer detection. Enabling allows network share access. Primary fix.

Enabling network discovery and file sharing
  1. Press Windows + R, type control, press Enter
  2. Control Panel opens
  3. View by: Large icons
  4. Click Network and Sharing Center
  5. In left sidebar: Click Change advanced sharing settings
  6. Advanced Sharing Settings opens
  7. For Private Network Profile:
  8. Expand Private (current profile) section
  9. Network Discovery:
    • Select Turn on network discovery
    • Check Turn on automatic setup of network connected devices
  10. File and Printer Sharing:
    • Select Turn on file and printer sharing
  11. For Guest or Public Network Profile:
  12. Expand Guest or Public section
  13. Repeat same settings:
    • Turn on network discovery
    • Turn on file and printer sharing
  14. All Networks Section:
  15. Scroll down to All Networks
  16. Public folder sharing:
    • Select Turn on sharing so anyone with network access can read and write files in the Public folders
  17. Password protected sharing:
    • For home networks: Select Turn off password protected sharing
    • For office networks: Keep Turn on password protected sharing
  18. Click Save changes at bottom
  19. Close Network and Sharing Center
  20. Restart Required Services:
  21. Press Windows + R, type services.msc, press Enter
  22. Find and restart these services:
    • Function Discovery Resource Publication → Right-click → Restart
    • SSDP Discovery → Right-click → Restart
    • UPnP Device Host → Right-click → Restart
  23. Close Services window
  24. Try accessing network share

Method 2: Configure Windows Firewall for File Sharing

Firewall blocks SMB traffic. Adding exception allows network share connections.

Configuring Windows Firewall for file sharing
  1. Press Windows + R, type firewall.cpl, press Enter
  2. Windows Defender Firewall opens
  3. Click Allow an app or feature through Windows Defender Firewall
  4. Allowed apps window opens
  5. Click Change settings button (top)
  6. Scroll through list to find File and Printer Sharing
  7. Check BOTH boxes for File and Printer Sharing:
    • ✓ Private
    • ✓ Public (if you use public networks)
  8. Also enable Network Discovery:
    • ✓ Private
    • ✓ Public
  9. Click OK
  10. Advanced Firewall Configuration (If Above Doesn't Work):
  11. Press Windows + R, type wf.msc, press Enter
  12. Windows Defender Firewall with Advanced Security opens
  13. Click Inbound Rules in left pane
  14. Look for rules named "File and Printer Sharing"
  15. Ensure these rules are Enabled (green checkmark icon):
    • File and Printer Sharing (Echo Request - ICMPv4-In)
    • File and Printer Sharing (NB-Session-In)
    • File and Printer Sharing (SMB-In)
    • File and Printer Sharing (NB-Name-In)
    • File and Printer Sharing (NB-Datagram-In)
  16. If any disabled: Right-click → Enable Rule
  17. Close Firewall window
  18. Try accessing network share

Method 3: Change Network Profile from Public to Private

Public network profile disables sharing. Private profile enables full network features.

Changing network profile to Private
  1. Windows 10/11 Method:
  2. Press Windows + I to open Settings
  3. Click Network & Internet
  4. For Wi-Fi:
    • Click Wi-Fi in left sidebar
    • Click your connected network name
    • Under "Network profile type":
    • Select Private
  5. For Ethernet:
    • Click Ethernet in left sidebar
    • Click your connection name
    • Under "Network profile type":
    • Select Private
  6. Alternative Method (Registry - Advanced):
  7. Press Windows + R, type regedit, press Enter
  8. Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
  9. Expand Profiles key
  10. Multiple subkeys with GUID names appear
  11. Click each subkey and check ProfileName value
  12. Find your network name
  13. In that subkey: Double-click Category
  14. Change value:
    • 0 = Public
    • 1 = Private
    • 2 = Domain
  15. Set to 1 (Private)
  16. Click OK
  17. Close Registry Editor
  18. Restart computer
  19. Try accessing network share

Method 4: Enable NetBIOS over TCP/IP

NetBIOS disabled prevents computer name resolution. Enabling restores name-based network access.

Enabling NetBIOS over TCP/IP
  1. Press Windows + R, type ncpa.cpl, press Enter
  2. Network Connections window opens
  3. Right-click your active network adapter (Wi-Fi or Ethernet)
  4. Select Properties
  5. Find and select Internet Protocol Version 4 (TCP/IPv4)
  6. Click Properties button
  7. Click Advanced button
  8. Go to WINS tab
  9. NetBIOS setting:
    • Current setting likely: "Disable NetBIOS over TCP/IP"
    • Change to: Enable NetBIOS over TCP/IP
    • Or: Default (uses DHCP server setting)
  10. Click OK on all windows
  11. Restart Network Adapter:
  12. Right-click network adapter → Disable
  13. Wait 5 seconds
  14. Right-click again → Enable
  15. Verify NetBIOS Services Running:
  16. Press Windows + R, type services.msc, press Enter
  17. Find TCP/IP NetBIOS Helper
  18. Status should be Running
  19. Startup type should be Automatic
  20. If stopped: Right-click → Start
  21. If startup type Manual: Right-click → Properties → Startup type: Automatic → OK
  22. Close Services
  23. Try accessing network share using computer name

Method 5: Update Network Adapter Drivers

Outdated drivers cause connection instability. Updating restores reliable network share access.

Updating network adapter drivers
  1. Press Windows + X → Device Manager
  2. Expand Network adapters
  3. Update Wi-Fi Adapter (if using Wi-Fi):
  4. Right-click your Wi-Fi adapter
  5. Select Update driver
  6. Choose Search automatically for drivers
  7. Windows searches and installs latest driver
  8. If "Best drivers already installed": Try manual update
  9. Manual Driver Update (More Reliable):
  10. Note your network adapter model name
  11. Visit manufacturer website:
    • Intel: intel.com/support → Network adapters
    • Realtek: realtek.com/downloads
    • Qualcomm/Atheros: qualcomm.com/support
    • Broadcom: broadcom.com/support
    • Laptop: Manufacturer support (Dell, HP, Lenovo, ASUS)
  12. Download latest driver for your adapter and Windows version
  13. Run installer
  14. Follow installation wizard
  15. Update Ethernet Adapter (if using Ethernet):
  16. Repeat same process for Ethernet adapter
  17. Restart computer after driver updates
  18. Try accessing network share

Method 6: Reset Network Settings

Corrupted network configuration causes persistent errors. Reset restores defaults.

Resetting network settings
  1. Windows 10/11 Network Reset:
  2. Press Windows + I → Network & Internet
  3. Scroll down to Advanced network settings
  4. Click Network reset
  5. ⚠️ Warning: This will:
    • Remove and reinstall all network adapters
    • Reset networking components to defaults
    • Forget all Wi-Fi networks (need to reconnect)
    • Reset VPN connections
  6. Click Reset now
  7. Confirmation: Click Yes
  8. Computer restarts automatically
  9. After Restart:
  10. Reconnect to Wi-Fi network
  11. Reconfigure network settings (Methods 1-4)
  12. Command Line Network Reset (Alternative):
  13. Open Command Prompt as Administrator
  14. Run these commands in order:
    netsh winsock reset
    netsh int ip reset
    ipconfig /release
    ipconfig /renew
    ipconfig /flushdns
  15. Each command shows success message
  16. Restart computer
  17. Try accessing network share

💡 Pro Tip: Prevent Future 0x80070035 Errors

Use IP addresses instead of computer names for critical shares: Map network drives using \\192.168.1.100\share instead of \\COMPUTERNAME\share—bypasses NetBIOS name resolution issues. Keep network profile consistent: Always set home/office networks to "Private" immediately after connecting—prevents Windows from applying restrictive Public profile policies. Create static IP addresses for file servers: In router DHCP settings, assign permanent IP addresses to computers hosting shared folders—prevents IP changes breaking mapped drives. Document network credentials: For password-protected shares, use Credential Manager (Control Panel → Credential Manager → Windows Credentials) to save credentials permanently—prevents repeated login prompts. Disable IPv6 if not used: Network adapter properties → uncheck "Internet Protocol Version 6 (TCP/IPv6)"—IPv6 can interfere with NetBIOS name resolution on pure IPv4 networks. Enable SMB 1.0 only if necessary: Windows 10/11 disable SMB 1.0 by default for security—only enable (Control Panel → Programs → Turn Windows features on/off → SMB 1.0/CIFS File Sharing Support) if accessing very old NAS or Windows XP shares. Use DNS names in domain environments: In Active Directory domains, use FQDN (\\server.domain.local\share) instead of NetBIOS names—more reliable and bypasses WINS dependencies. Monitor Windows Updates: Some Windows Updates reset network discovery settings—verify network discovery still enabled after major updates. For persistent issues: Create batch script to enable network discovery and restart services—run after every Windows Update or when 0x80070035 appears.

Frequently Asked Questions

Q: I can ping the computer but still get 0x80070035 when accessing shares. Why?

A: Ping uses ICMP, file sharing uses SMB—different protocols. Successful ping proves: (1) Network connectivity exists (cables/Wi-Fi working), (2) IP routing functional, (3) Target computer powered on and network-connected. But ping doesn't test: (1) SMB protocol (TCP port 445) which file sharing requires, (2) Firewall rules for file sharing—firewall may allow ICMP (ping) but block SMB, (3) File sharing services running on target computer, (4) Network discovery and sharing settings. Troubleshooting steps: (1) Test SMB port: Command Prompt: telnet [IP] 445 (if telnet not installed: Control Panel → Programs → Turn Windows features on/off → Telnet Client). If connection refused: SMB blocked by firewall or service not running. (2) Check File Sharing services on target: On computer hosting share: services.msc → verify "Server" service running (this is Windows File Sharing service despite generic name). (3) Verify firewall: On target computer: Windows Firewall → Allow an app → ensure "File and Printer Sharing" enabled for Private networks. (4) Try IP-based access: Use \\192.168.1.100\share instead of \\COMPUTERNAME\share—if IP works but name doesn't, NetBIOS name resolution problem (enable NetBIOS over TCP/IP). Ping success + share failure = SMB-specific configuration issue, not general network problem.

Q: Network shares work immediately after restart but fail after few hours. What causes this?

A: Intermittent failures indicate service/connection timeout issues. Common causes: (1) Network adapter power saving: Windows puts network adapter to sleep to save power, adapter doesn't wake properly for network requests. Fix: Device Manager → Network adapters → right-click adapter → Properties → Power Management tab → uncheck "Allow the computer to turn off this device to save power". (2) SMB session timeout: Windows SMB client closes idle connections after timeout (default 15 minutes), reconnection fails due to cached credentials or stale sessions. Fix: Restart "Workstation" service (services.msc) or reboot. Prevention: Keep shares actively accessed or use persistent mapped drives. (3) DNS/NetBIOS cache expiration: Computer name to IP mapping cached temporarily, expires after hours, re-resolution fails. Fix: Command Prompt: nbtstat -R (clears NetBIOS cache), ipconfig /flushdns (clears DNS cache). Prevention: Use static IP addresses for file servers in router DHCP settings. (4) Network discovery service stops: "Function Discovery Resource Publication" service crashes or stops after running for hours. Fix: services.msc → Function Discovery Resource Publication → Properties → Startup type: Automatic → Recovery tab → configure "Restart the Service" for first/second/subsequent failures. (5) Wi-Fi instability: Wireless connection drops packets or disconnects briefly, SMB sessions don't recover. Fix: Update Wi-Fi drivers, move closer to router, or use Ethernet for critical file sharing. Diagnostic: Event Viewer → Windows Logs → System → filter for "Server" source around failure time—shows SMB service errors.

Q: Can access shares from Windows 10 but Windows 11 gives 0x80070035. Why?

A: Windows 11 has stricter SMB security requirements. Differences: (1) SMB 1.0 disabled by default: Windows 11 completely disables SMB 1.0 protocol for security (vulnerable to WannaCry-style attacks). If file server only supports SMB 1.0 (old NAS, Windows XP/Vista), Windows 11 cannot connect. Check SMB version: On file server: PowerShell: Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol. If only SMB1 enabled: upgrade server to support SMB 2.0+ or enable SMB 1.0 on Windows 11 (not recommended): Control Panel → Programs → Turn Windows features on/off → check "SMB 1.0/CIFS File Sharing Support" → restart. (2) Guest access disabled: Windows 11 blocks guest access to SMB shares by default (security hardening). If share allows anonymous/guest access without password, Windows 11 refuses connection. Fix: Enable guest access (reduces security): Registry Editor → HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters → New DWORD: AllowInsecureGuestAuth → Value: 1 → restart. Or better: configure share with proper username/password authentication. (3) Encryption requirements: Windows 11 prefers SMB encryption, some old servers don't support it causing negotiation failures. Fix: On Windows 11: PowerShell (Admin): Set-SmbClientConfiguration -RequireSecuritySignature $false (disables mandatory signing). (4) Network profile defaults: Windows 11 more aggressive about setting networks to "Public" profile—check network profile (Method 3), ensure "Private". Best solution: Update file server to Windows 10/11 or modern NAS firmware supporting SMB 2.0+ with encryption—maintains security while ensuring compatibility.

Q: Error 0x80070035 only occurs with specific shared folder, others work fine. What's wrong?

A: Folder-specific issue indicates permissions or share configuration problem. Troubleshooting: (1) Check share permissions: On computer hosting share: right-click folder → Properties → Sharing tab → Advanced Sharing → Permissions. Ensure "Everyone" or specific users have at least "Read" permission. Common mistake: NTFS permissions correct but share permissions restrictive. (2) Verify NTFS permissions: Properties → Security tab → ensure your user account or "Everyone" has permissions. Both share AND NTFS permissions must allow access—most restrictive wins. (3) Check share name: Advanced Sharing → Share name field—ensure no special characters, spaces, or excessive length (max 80 characters). Rename share if problematic. (4) Path length limit: Windows has 260-character path limit. If \\server\share\folder\subfolder\file.txt exceeds 260 characters total, access fails. Fix: Shorten folder names or enable long path support: Registry → HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem → DWORD LongPathsEnabled → Value: 1. (5) Folder corruption: Specific folder's metadata corrupted. Test: Create new share of different folder—if works, original folder has issues. Fix: Run CHKDSK on drive hosting share: chkdsk D: /f /r (replace D: with actual drive). (6) Antivirus blocking: Security software may quarantine or block specific folder. Check antivirus logs, add folder to exclusions. (7) Hidden/system folder: If folder has Hidden or System attributes, some Windows versions restrict network access. Fix: Remove attributes: attrib -h -s "C:\SharedFolder".

Q: Should I disable Windows Firewall to fix 0x80070035? Is it safe?

A: Never disable firewall—configure it properly instead. (1) Why disabling is dangerous: Firewall protects against network attacks (ransomware, worms, port scans). Disabling exposes computer to threats, especially on public Wi-Fi or internet-connected networks. Even on "trusted" home networks, IoT devices (smart TVs, cameras) can be compromised and attack other devices. (2) Proper approach: Enable specific firewall rules for File and Printer Sharing (Method 2)—allows necessary SMB traffic while blocking everything else. Windows Firewall has granular controls: allow file sharing only on Private networks, block on Public networks. (3) Testing firewall as cause: If you must test, disable firewall temporarily (5 minutes), test network share, immediately re-enable. If share works with firewall off: firewall is cause but don't leave disabled—configure rules instead. (4) Third-party firewalls: Norton, McAfee, ZoneAlarm often more restrictive than Windows Firewall. Check third-party firewall settings, add exceptions for SMB (TCP 445, 139, UDP 137-138). Or temporarily disable third-party firewall, rely on Windows Firewall (which has better Windows integration). (5) Corporate environments: If on company network with centralized firewall (hardware firewall/router), local Windows Firewall less critical but still recommended as defense-in-depth. Consult IT before disabling. (6) Alternative: If firewall configuration too complex, use VPN software (like Hamachi, ZeroTier) to create virtual LAN—bypasses firewall issues by tunneling traffic, maintains security. Bottom line: Properly configured firewall allows file sharing AND maintains security—never sacrifice security for convenience.