Hello Logan,

Thank you for reaching out with your question regarding insecure guest logins in Windows 11 24H2.

Background:

Microsoft has been progressively increasing the security measures in Windows, and disabling insecure guest logins is one of those steps. Insecure guest logins can pose a significant security risk because they allow access to network shares without requiring a username or password. This change aligns with the security enhancements seen in Windows Enterprise editions.

Your Situation:

After updating to Windows 11 24H2, you found that connecting to network shares without requiring a login (everyone access, password protected sharing turned off) no longer works. Shares with a password and those configured in group policy to allow insecure guest logins function correctly.

Explanation:

Based on the behavior you described, it seems Microsoft is indeed defaulting insecure guest logins to disabled in Windows 11 24H2. This change would enhance security by preventing anonymous access to network shares.

Steps to Address the Issue:

1. Enable Insecure Guest Logins via Group Policy:

  • Press **Win + R**, type gpedit.msc, and press Enter to open the Group Policy Editor.
  • Navigate to **Computer Configuration** > **Administrative Templates** > **Network** > **Lanman Workstation**.
  • Double-click **Enable insecure guest logons** and set it to **Enabled**.
  • Apply the changes and restart your computer.

2. Enable Insecure Guest Logins via Registry Editor:

  • Press **Win + R**, type regedit, and press Enter to open the Registry Editor.
  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.

  • If the AllowInsecureGuestAuth entry does not exist, right-click and select **New** > **DWORD (32-bit) Value**, and name it AllowInsecureGuestAuth.
  • Set the value of AllowInsecureGuestAuth to 1.
  • Close the Registry Editor and restart your computer.

3. Consider Alternative Security Measures:

  • Instead of enabling insecure guest logins, consider setting up password-protected sharing for better security.
  • Ensure that all users have appropriate permissions to access the necessary shares.

Best regards,

Rosy

Top answer
1 of 5
67

Hello Logan,

Thank you for reaching out with your question regarding insecure guest logins in Windows 11 24H2.

Background:

Microsoft has been progressively increasing the security measures in Windows, and disabling insecure guest logins is one of those steps. Insecure guest logins can pose a significant security risk because they allow access to network shares without requiring a username or password. This change aligns with the security enhancements seen in Windows Enterprise editions.

Your Situation:

After updating to Windows 11 24H2, you found that connecting to network shares without requiring a login (everyone access, password protected sharing turned off) no longer works. Shares with a password and those configured in group policy to allow insecure guest logins function correctly.

Explanation:

Based on the behavior you described, it seems Microsoft is indeed defaulting insecure guest logins to disabled in Windows 11 24H2. This change would enhance security by preventing anonymous access to network shares.

Steps to Address the Issue:

1. Enable Insecure Guest Logins via Group Policy:

  • Press **Win + R**, type gpedit.msc, and press Enter to open the Group Policy Editor.
  • Navigate to **Computer Configuration** > **Administrative Templates** > **Network** > **Lanman Workstation**.
  • Double-click **Enable insecure guest logons** and set it to **Enabled**.
  • Apply the changes and restart your computer.

2. Enable Insecure Guest Logins via Registry Editor:

  • Press **Win + R**, type regedit, and press Enter to open the Registry Editor.
  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.

  • If the AllowInsecureGuestAuth entry does not exist, right-click and select **New** > **DWORD (32-bit) Value**, and name it AllowInsecureGuestAuth.
  • Set the value of AllowInsecureGuestAuth to 1.
  • Close the Registry Editor and restart your computer.

3. Consider Alternative Security Measures:

  • Instead of enabling insecure guest logins, consider setting up password-protected sharing for better security.
  • Ensure that all users have appropriate permissions to access the necessary shares.

Best regards,

Rosy

2 of 5
25

In admin PowerShell type in:
Set-SmbClientConfiguration -RequireSecuritySignature $false

It is the SMB sign in that is on by default on 24H2.

Check here: https://techcommunity.microsoft.com/t5/storage-at-microsoft/smb-signing-required-by-default-in-windows-insider/ba-p/3831704

🌐
Microsoft Learn
learn.microsoft.com › en-us › windows-hardware › customize › desktop › unattend › microsoft-windows-workstationservice-allowinsecureguestauth
AllowInsecureGuestAuth | Microsoft Learn
<settings pass="generalize"> <component name="Microsoft-Windows-WorkstationService" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AllowInsecureGuestAuth>1</AllowInsecureGuestAuth> </component> </settings>
🌐
BleepingComputer
bleepingcomputer.com › bleepingcomputer forums › microsoft windows support › windows 10 support
Confusion regarding AllowInsecureGuestAuth registry key and event 31018 - Windows 10 Support
2 weeks ago - On Windows 10 2004, Windows 10 20H2, and Windows 10 21H1 Enterprise and Education editions with KB5003173 installed, guest authentication is disabled if AllowInsecureGuestAuth doesn't exist or if it exists with a value of 0 in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] AllowInsecureGuestAuth.
🌐
Spiceworks
community.spiceworks.com › software & applications
Editing allowinsecureguestauth 0 to 1 not fixing access errors - Software & Applications - Spiceworks Community
January 30, 2025 - Edit allowinsecureguestauth Here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters 0 to 1. Still getting: you can’t access this folder because your organization security policies blo…
🌐
Microsoft Support
support.microsoft.com › en-US › onedrive › share-files-and-folders-in-microsoft-onedrive
Share files and folders in Microsoft OneDrive | Microsoft Support
Use OneDrive as a cloud backup to share your files and folders with others. Learn how to control permissions, allow editing, or set expiration dates.
🌐
Microsoft Support
support.microsoft.com › fi-fi › help › 4046019 › guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser
Enable insecure guest logons in SMB2 and SMB3 for Windows client and Windows Server | Microsoft Learn
June 25, 2020 - This article describes how to enable guest logons policy in SMB2 and SMB3 for Windows client and Windows Server devices using Group Policy and PowerShell.
Find elsewhere
🌐
GitHub
gist.github.com › Disassembler0 › 2acf07a232cd6dff4a5aa0f9c93319d8
Allow insecure guest authentication · GitHub
Allow insecure guest authentication. GitHub Gist: instantly share code, notes, and snippets.
🌐
Syxsense
syxsense.com › wp-content › uploads › syxsense-securityarticles › cis_benchmarks › syx-1033-12369.html
18.6.8.1 Ensure 'Enable insecure guest logons' is set to 'Disabled' (Level 1)
CIS Microsoft Windows 10 Enterprise Benchmark v4.0.0 · 🗏 18 Administrative Templates (Computer) | 18.6 Network | 18.6.8 Lanman Workstation
🌐
Microsoft Support
support.microsoft.com › en-US › onedrive › restrictions-and-limitations-in-onedrive-and-sharepoint
Restrictions and limitations in OneDrive and SharePoint | Microsoft Support
Troubleshoot problems uploading files to OneDrive or SharePoint such as invalid characters in file names, blocked files, or files with specific permissions.
🌐
Microsoft Support
support.microsoft.com › en-us › office › -sorry-we-can-t-perform-this-action-error-when-you-try-to-open-a-document-from-a-onedrive-for-work-or-school-0eed92fd-de5e-4a3a-82ad-f9822285e2a8
"Sorry, we can't perform this action" error when you try to open a document from a OneDrive for work or school - Microsoft Support
Note: This article applies only to the previous OneDrive for work or school sync app (groove.exe). In most cases, we recommend that you use the newer OneDrive sync app (onedrive.exe) instead. Which OneDrive app · Consider the following scenario
🌐
Google Support
support.google.com › mail › thread › 182882752 › application-specific-password-required
application-specific password required - Gmail Community
October 7, 2022 - Skip to main content · Gmail Help · Sign in · Google Help · Help Center · Community · Gmail · Terms of Service · Submit feedback · Send feedback on
🌐
Lokalisointi
lokalisointi.fi › sanasto
lokalisointi.org sanasto
Jos ohjelmiston kohderyhmä on peruskäyttäjät, ovat he tottuneet kansio-termiin Windowsissa. Kansio-termi on myös yhtenevä kansiota esittävän kuvakkeen kanssa. Hakemisto on peruskäyttäjälle vaikeasti ymmärrettävä termi, koska kaikissa muissa kuin ATK-alan merkityksissä hakemisto ...
🌐
Epson
download.epson-europe.com › pub › download › 6327 › epson632792eu.pdf pdf
Järjestelmänvalvojan opas NPD5978-01 FI
Kansion nimessä voi olla 1–12 aakkosnumeerista merkkiä. Jos kansion nimi on tätä pidempi, et ehkä pysty
🌐
Asteri Ohjelmat
asteri.fi › etusivu › mikrotuelle › windows 11 optimointia
Windows 11 optimointia - Asteri Ohjelmat
March 25, 2026 - Herjasi ”Paikallisen laitteen nimi on jo käytössä” Uudelleenkirjautuminen herjaa: Et voi käyttää tätä jaettua kansiota, koska organisaatiosi suojauskäytännöt estävät todentamattoman vieraskäytön.
🌐
Microsoft Support
support.microsoft.com › fi-fi › servicing › os › windows-server › 2021 › 01 › delayed-error-message-when-you-try-to-access-a-shared-folder-that-no-longer-exists-in-windows
Viivästynyt virheilmoitus, kun yrität käyttää jaettua kansiota, jota ei enää ole Windowsissa | Microsoft Support
Korjaa ongelman, jossa saat viivästyneen virhesanoman, kun yrität käyttää jaettua kansiota, jota ei ole. Tämä ongelma ilmenee tietokoneessa, jossa on käytössä Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2 tai Windows Server 2016.