Hello Ohidul Mallick,
Your file sharing issue stems from intentional security enhancements introduced in the Windows 11 24H2 update, which fundamentally alters how the Server Message Block protocol handles local network traffic. Microsoft now mandates network signing by default on all connections, acting as a cryptographic seal to prevent data tampering, and guest authentication is strictly blocked. When you attempted to modify the registry using the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters to set AllowInsecureGuestAuth, the connection still failed because the newly updated 24H2 host system is actively rejecting these unsigned, unauthenticated guest requests regardless of your client-side registry overrides. Older systems and guest accounts simply cannot negotiate these new mandatory security signatures.
To resolve this while maintaining the integrity of your network, the recommended approach is to completely transition away from guest network access. You should create dedicated local user accounts with strong passwords directly on the newly updated Windows 11 24H2 machines and explicitly grant those accounts permission to access your shared folders. When you attempt to connect from the older systems, Windows will prompt you to enter these specific credentials, which successfully satisfies the cryptographic signing requirements and securely restores your access across all machines.
If your computers operate on an isolated, strictly private home network and you absolutely must rely on legacy guest access, you can manually revert these new security protocols. You will need to open PowerShell as an Administrator on your Windows 11 24H2 systems and execute the command Set-SmbServerConfiguration -RequireSecuritySignature $false followed by Set-SmbClientConfiguration -RequireSecuritySignature $false. This instructs the operating system to stop demanding the cryptographic seal on file sharing traffic. After confirming both prompts and restarting your systems, your previous sharing configuration and the insecure guest logon registry edits you previously applied should begin functioning exactly as they did before the update.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN