24H2 Network Share Not Working

Windows 11 24H2 share access failures often trace to SMB hardening or credentials—fix guest access, firewall, and usernames in order.

Windows 11 24H2 tightens SMB behavior, which can trip up older NAS boxes, router USB shares, and loose home workgroup setups on your LAN. You may see a looped credential prompt, 0x80070035, “path not found,” or “access denied” when you open \\SERVER\Share or map a drive.

This guide sticks to fixes that match the actual failure point: identity, guest access, discovery, firewall, SMB version, and name resolution. You’ll start with quick checks, then move into settings that 24H2 makes less forgiving.

What Changed In Windows 11 24H2 That Can Block SMB Shares

Microsoft notes that security changes in Windows 11 24H2 can prevent access to some third-party NAS appliances or other devices that don’t meet current SMB expectations. That shows up most on consumer gear that relies on guest access or weak authentication paths. Microsoft TechCommunity: third-party NAS access may fail

Two patterns are common:

Guest access is blocked — If the share expects anonymous or “guest” logons, 24H2 may refuse the session and show a policy message about unauthenticated guest access.
Authentication is stricter — Some servers accept a password only when the client presents the account in the expected format, or when the server has required SMB security features.

In most homes, the clean fix is to stop using guest and connect with a named account that has a password.

Fast Checks Before You Change Anything

Run these first. They catch the easy wins and keep you from changing settings that weren’t broken.

Try the IP path — In File Explorer, enter \\192.168.1.50\Share. If IP works but the name fails, SMB is fine and name resolution is the issue.
Confirm the network profile — Public profile can block discovery and sharing. Set your home LAN to Private when it’s safe.
Restart both ends — Reboot the PC and the NAS/router/share host. Also re-seat Ethernet and confirm link lights.
Clear saved credentials — Remove old entries for the host in Credential Manager, then reconnect with the correct user.
Test another client — If a second PC reaches the share, the host is up and the 24H2 client needs adjustment.

If you’re seeing 24h2 network share not working on only one PC, treat it like a local state issue first. A wrong saved credential, a stale session, or a Public network profile can block access even when the NAS is fine. Clear sessions with net use, delete stored credentials for the target, then reconnect once using the same server name each time.

If the IP path fails too, keep going. The table next helps you pick the right branch.

Match The Error To The Fix That Fits

Similar-looking messages can point to different layers. Use this as a quick sorter.

What You See	Most Likely Cause	First Fix To Try
0x80070035 “Network path not found”	Name resolution, discovery, firewall, SMB service	Try IP path, then check discovery and File And Printer Sharing rules
Credential prompt repeats	Saved creds, wrong username format, local account mismatch	Delete saved creds, then sign in as HOST\user or user@host
Guest access blocked by policy	Guest-only share	Create a named NAS user, or enable insecure guest logons only if needed
“Access is denied”	Share permissions, NTFS permissions, auth mismatch	Verify permissions, then re-enter credentials in the correct format

Microsoft’s troubleshooting for error 0x80070035 frames it as “network path not found” and lists SMB features and firewall checks as common next steps. Microsoft Answers: 0x80070035

Fix The Share Step By Step

Work in order. Stop when the share opens and still works after a reboot.

Credential And Account Fixes

For workgroup sharing, Windows is happier when the host and client agree on identity. If you’re connecting to another Windows PC, also confirm the host is awake and not in sleep.

Use a clean username format — For a local account on the share host, try SERVER\username. If you see a domain field, fill it with the host name.
Create a dedicated share user — On a NAS, add a user with a password and grant access to the share. Use that user from every PC.
Save one Windows credential — Add a Windows credential for the server name or IP, then reconnect so Windows stops guessing.

Quick Command Tests

When File Explorer is vague, a couple of commands can tell you which layer is failing. Run these in PowerShell today.

Test port 445 — Run Test-NetConnection 192.168.1.50 -Port 445. If it fails, a firewall, router rule, or the NAS service is blocking SMB.
Try a clean net use — Run net use \\192.168.1.50\Share /user:NAS\user, then enter the password. If that works, Explorer was using the wrong saved identity.
List current sessions — Run net use to see existing connections. If you see the same server listed twice under different names, delete them with net use \\NAS\IPC$ /delete (adjust the target) and reconnect once.

These checks also help when you see the classic “already connected with a different user name” message. Clearing sessions gives you one identity per target, which SMB expects.

Guest Access And “Insecure Guest Logons”

If your NAS/router share is guest-only, 24H2 may block it. Microsoft documents SMB insecure guest logon behavior and the approved ways to enable it when you accept the risk. Microsoft documentation: enable insecure guest logons

Prefer authenticated access:

Turn off guest on the NAS — Disable anonymous access and require a username and password.
Grant share permissions — Assign read or read/write rights to your NAS user and remove “everyone” if the NAS uses it for guest.

If you must use guest on a trusted LAN, Windows Pro and Enterprise can toggle the policy under Lanman Workstation. A 24H2 thread in Microsoft Answers points to that setting and notes guest access may be disabled by default. Microsoft Answers: 24H2 guest logons

Network Discovery And Firewall Rules

Discovery and file sharing depend on the network profile and firewall rules. A single toggle can make PCs visible but unreachable.

Turn on Network Discovery — Enable discovery and file sharing for the Private profile.
Allow File And Printer Sharing — In Windows Defender Firewall, confirm File and Printer Sharing is allowed on Private. Microsoft Answers: allow File and Printer Sharing
Check third-party firewalls — If you use a security suite, confirm it trusts your LAN and is not blocking TCP 445.

SMB Version And NAS Compatibility

Older devices may need a firmware update or a setting change for SMB2/SMB3. Treat SMB1 as a last resort and only on a trusted LAN segment.

Update NAS firmware — Install the latest vendor update, then reboot the NAS.
Set minimum SMB to 2 — In the NAS SMB settings, pick SMB2 as minimum if the option exists.
Review SMB signing rules — Microsoft describes how SMB signing works and the errors you may see when a third-party server can’t sign traffic. Microsoft documentation: SMB signing

At this point, most cases are fixed. If it still fails, the next two sections cover name-only failures and post-update breakage patterns.

Network Share Not Working In 24H2 On Windows 11 By Name Only

If \\192.168.1.50\Share works but \\NAS\Share fails, work on name resolution. Home networks can rely on router DNS, mDNS, and legacy broadcasts, and updates can expose weak name records.

Try the device FQDN — If your router hands out a local domain, test nas.lan or your local suffix.
Reserve the NAS IP — Use DHCP reservation so the NAS keeps one address and the name stays stable.
Add a hosts entry — As a diagnostic step, map the name to the IP in the hosts file and retry by name.
Remove duplicate saved targets — Clear saved credentials for both the name and the IP so Windows doesn’t try old identities.

If you want one fast check, ping the name and confirm it resolves to the IP you expect. If it resolves to an old address, fix DHCP reservation first, then reconnect.

If you landed here after a clean install or upgrade and your shares stopped the same day, treat it as a compatibility shift, not random bad luck. Users have tracked timing to 24H2 and to later cumulative updates that enforce stricter SMB authentication on some setups. Microsoft Answers: 24H2 SMB share access thread

Run this checklist and you’ll usually pinpoint the blocker:

Switch the NAS to authenticated SMB — Create a user, set a password, disable guest, and grant share rights.
Reconnect with clean credentials — Remove saved entries, then connect again with the NAS username and password.
Read the exact wording — Guest policy messages point to guest access; 0x80070035 points to discovery or firewall; access denied points to permissions or identity.
Update the NAS and router — Install firmware updates, then confirm SMB2/SMB3 settings after reboot.

If you’re in a managed workplace, policies can block local guest toggles. In that scenario, the practical fix is to update the file server settings so it handles authenticated SMB that meets current expectations.

Make Sure The Fix Stays Put

After the share opens, prove it stays stable across reboot and sleep. This prevents the “it worked once” trap.

Reboot and reconnect — Restart the PC, then open the share by name and by mapped drive.
Test sleep and wake — Sleep the PC, wake it, and open the share. If it fails, test disabling power saving on the network adapter.
Verify one credential entry — Keep a single, correct Credential Manager entry for the host, and remove older duplicates.
Lock the IP — DHCP reservation avoids sudden name/IP drift.
Log the next failure — If it breaks again, check Event Viewer under Windows Logs and note the SMB client or security error that matches the time.

Most of the time, once you stop guest access and align credentials, the “24h2 network share not working” issue is gone. If the same machine keeps dropping the session, re-run the command tests and confirm port 445 stays reachable over time. If it only fails on one Wi-Fi band, check router isolation settings and client steering.

If you need a final sanity check, try the share from another Windows build. If that works and 24H2 does not, the share host likely needs a firmware update or a shift away from guest access. That’s the long-term fix that keeps 24H2 happy without weakening your LAN.