Windows 11 24H2 blocks network share access with error 0x80070035 displaying “The network path was not found”. This error prevents access to NAS devices, network storage, and shared folders after upgrading to Windows 11 version 24H2. Two security changes cause the network path was not found error: mandatory SMB signing and disabled guest authentication.

Understanding the Error

The network path was not found error appears when accessing \\SERVERNAME or \\192.168.1.100 network paths. Windows 11 24H2 enforces stricter SMB security that breaks connectivity to network shares using guest access. This affects NAS devices, shared folders on other computers, and network storage systems.

• SMB Signing Required by Default – Affects all editions (Pro, Enterprise, Education) except Home
• Guest Fallback Disabled – Disabled on Pro edition by default

Enable Insecure Guest Logons Guide: https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3

SMB Signing Changes Documentation: https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-signing and https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

Fix 1: Enable Insecure Guest Logons

Using Group Policy (Pro/Enterprise)

1. Press Win + R, type gpedit.msc, press Enter
2. Navigate to: Computer Configuration → Administrative Templates → Network → Lanman Workstation
3. Double-click “Enable insecure guest logons”
4. Select “Enabled”
5. Click Apply then OK

Using Registry (Home Edition)

1. Press Win + R, type regedit, press Enter
2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation
3. Right-click LanmanWorkstation → New → DWORD (32-bit) Value
4. Name it AllowInsecureGuestAuth
5. Double-click, set Value data to 1
6. Click OK

Fix 2: Disable SMB Security Signature

1. Press Win + X
2. Select “Terminal (Admin)” or “Windows PowerShell (Admin)”
3. Run this command:

Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

Restart and Test

1. Restart your computer
2. Open File Explorer
3. Type \\SERVERNAME or \\192.168.1.100
4. Press Enter

Your network shares should now be accessible without the network path was not found error.

These changes reduce Windows 11 security by allowing unsigned SMB connections and unauthenticated access. Only use on trusted home networks behind a router firewall. Never apply these settings on public or corporate networks.

Better Alternative: Use Proper Authentication

Instead of disabling security to fix the network path was not found error:

1. Create user accounts on your network storage device
2. In Windows, map network drives with credentials
3. Right-click This PC → Map network drive
4. Enter network path and check “Connect using different credentials”
5. Provide username and password

This maintains Windows 11 security whilst eliminating the network path was not found error permanently. For additional authentication troubleshooting, see this guide on fixing unauthenticated guest access errors.

Additional Links

• Windows 11 24H2 and Insecure Guest Logins settings
• Can’t access share folders in windows 11 in home network

Conclusion

Whilst effective for home networks, the recommended solution is implementing proper user authentication on your network storage. This maintains security whilst providing reliable network share access and also fixes the network path was not found error. Use some rudimentary username password combination rather than just allowing it insecurely. Just saying..

That’s it, Enjoy!