After upgrading to Windows 11 24H2 or later (including 25H2), some people suddenly can’t open a NAS or shared folder that used to work fine. File Explorer shows something like:
You can't access this shared folder because your organization's security policies block unauthenticated guest access. …
The NAS isn’t broken. Windows tightened its default settings. Below: how to tell which setting is the cause, the safe fix, and the workaround if you really can’t fix the NAS, following Microsoft’s documentation.
My NAS has always used a user name and password, so I didn’t hit this myself. But when I checked my own PC (Windows 11 Pro 25H2), its settings didn’t match what Microsoft describes. So I reproduced the “signing required” state on my PC and tested whether my two home NAS units still connect. Those results are further down.
Two causes: guest access blocked, SMB signing required
When shared folders stop opening on 24H2 and later, it’s almost always one of these two, or both:
| Cause | What changed | Typical errors |
| Guest access blocked | Windows no longer connects to shares that let you in without a user name and password (guest access) | “…security policies block unauthenticated guest access…” “Error code: 0x80070035 The network path was not found.” “System error 3227320323 has occurred.” |
| SMB signing required | Signing is now mandatory, so a NAS that doesn’t support signing (or has it turned off) can’t be reached | 0xc000a000 -1073700864 STATUS_INVALID_SIGNATURE “The cryptographic signature is invalid.” |
Microsoft’s documentation explains them like this:
- Guest access: since Insider Preview build 25267, Windows 11 Pro by default won’t connect with guest credentials even when the remote server asks for it (Windows 10 Enterprise, Education and others already behaved this way)
- SMB signing: on Windows 11 24H2 Enterprise, Pro and Education, SMB signing is required for both outbound and inbound connections. Home edition doesn’t require it
- How they relate: SMB signing can’t be used with guest access. So even if you allow guest access, a guest connection still fails while signing is required
On my PC (Windows 11 Pro 25H2), though, SMB signing was not required, probably because the PC has been upgraded several times (more below). It can differ from PC to PC, so checking your own settings first is the fastest route.
In short, the most likely combination to break is “Windows 11 Pro + a NAS used without a password”, common at home and in small offices.
First, check your current settings
Run this in PowerShell. No admin rights needed.
Get-SmbClientConfiguration | Format-List RequireSecuritySignature, EnableInsecureGuestLogons
- RequireSecuritySignature is True: SMB signing is required
- EnableInsecureGuestLogons is False: guest connections are not allowed
Also check your Windows version and edition: press Win + R, type winver.
The safe fix: create a user on the NAS and connect with a password
What Microsoft and NAS makers recommend is not weakening Windows, but switching the NAS to password-protected access.
- In the NAS admin page, create a user (user name and password) and give it permission on the shared folder. The steps vary by maker, so follow your NAS manual
- If SMB signing is disabled in the NAS settings, enable it. If there’s no such option, update the firmware
- From Windows, connect with the new user name and password
From the command line, net use creates a password-protected connection:
net use \\NAS-name\share-name /user:user-name *
The trailing * prompts for the password without echoing it. If you back up to the NAS automatically, see Back up a local folder to a password-protected NAS with Robocopy.
Microsoft’s documentation also recommends connecting by name rather than by IP address (not \\192.168.x.x\share).
If you really can’t fix the NAS: workaround (not recommended)
If an old NAS can’t create users or doesn’t support SMB signing, the only option left is relaxing Windows. Microsoft recommends neither workaround: allowing guest access raises the risk of being lured to fake servers, man-in-the-middle attacks and ransomware. On a work PC, don’t change this yourself; ask your IT department. On PCs managed by Group Policy, your change will be reverted anyway.
If you still want to change it, run this in PowerShell as administrator:
# Allow guest connections Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force # Do not require SMB signing when connecting Set-SmbClientConfiguration -RequireSecuritySignature $false
To connect as a guest, you have to change both settings (guests can’t use signing). In Group Policy (gpedit.msc) the settings are:
- Guest: Computer Configuration → Administrative Templates → Network → Lanman Workstation → “Enable insecure guest logons”
- Signing: Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options → “Microsoft network client: Digitally sign communications (always)”
Once the NAS is fixed, restore the defaults:
Set-SmbClientConfiguration -EnableInsecureGuestLogons $false -Force Set-SmbClientConfiguration -RequireSecuritySignature $true
What I found on my PC
I ran the check commands from this post on my own PC. Version: Windows 11 Pro 25H2 (OS build 26200.9711).

Then the SMB client settings:

- EnableInsecureGuestLogons is False. Guest connections aren’t allowed, as Microsoft describes, so this PC can’t open password-free shares
- RequireSecuritySignature is also False. Microsoft’s documentation says 24H2 Pro requires SMB signing, but my 25H2 Pro didn’t
Why signing wasn’t required
This PC wasn’t bought new with 24H2; it has been upgraded repeatedly. You can list past upgrades with:
Get-ChildItem HKLM:\System\Setup | Where-Object Name -like "*Source OS*" | Select-Object Name
Mine showed three: January 2021, December 2023 and January 2025. Then I looked at the registry values behind the signing setting:
Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters | Format-List RequireSecuritySignature, EnableSecuritySignature
RequireSecuritySignature : 0 EnableSecuritySignature : 1
RequireSecuritySignature is explicitly 0 (not required). EnableSecuritySignature is 1, so signing itself is supported. Before 24H2, “not required” was the Windows default, so the old value most likely carried over through the upgrades. I couldn’t find a Microsoft document that says outright that upgrades keep the previous value, though.
So an upgraded PC may still reach an old NAS while a newly bought PC can’t. Picture an office handing out new PCs, and only those PCs fail to open the shared folder.
Does my NAS still connect with signing required?
My home NAS connections were in fact unsigned. To see current SMB connections, run this in PowerShell as administrator (otherwise you get “Access is denied”):
Get-SmbConnection | Format-List ServerName, ShareName, Dialect, Signed, Encrypted
Dialect is the SMB version, and Signed shows whether the connection is signed. On my PC both NAS units showed Dialect 3.1.1, Signed False.
To reproduce a newly bought PC, I made signing required and reconnected. Existing connections keep their old settings, so I opened each NAS by IP address instead of its usual name to force a new connection (a reboot would also work).


Both new IP-address connections came up Signed True. The old connections by name stayed Signed False. So if your NAS supports signing, requiring it on the PC causes no trouble.
Since nothing broke, I left signing required on my PC. That matches a new Windows 11 install and protects against tampering and impersonated servers, which is the better state. Put the other way: if you can’t reach your NAS on 24H2 or later, either the NAS doesn’t support signing (or has it off), or you are using a guest share.
My NAS units use a user name and password and work fine: the “safe fix” state above.
Summary
- On Windows 11 24H2 and later, NAS access breaks because guest access is blocked and SMB signing is required
- An upgraded PC may not require signing (my 25H2 Pro didn’t), so only new PCs may fail
- A NAS that supports signing still connects with signing required (tested with my two NAS units)
- Start by checking your settings with Get-SmbClientConfiguration
- The real fix is a NAS user with a password (and SMB signing enabled on the NAS)
- Relaxing Windows is the last resort. On a work PC, ask IT


コメント