Pages

Windows 11 shared pc acces problem





After a Windows 11 update, shared folders on a PC may become inaccessible due to changes in network discovery, file sharing, or security settings.


See how to fix the problem

Open Gpedit.msc

Local computer policy>Computer Comfigration>Administrative Templates>Netwok>Lanman Server Worksatation> Enable insecure guest logons  If it is Not- Configured  then Change it to Enable









Local computer policy>Computer Configration>Security Setting>Local Policies>Security Options : Microsoft network client: Digitally sign communications (always)







==========================================================================



Using  Regedit














a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step 8.

b. In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.

c. Double-click Microsoft network client: Digitally sign communications (always).

d. Select Disabled OK.

 

7. Disable the guest fallback protection:

a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step e.

b. In the console tree, select Computer Configuration > Administrative Templates> Network > Lanman Workstation.

c. Double-click Enable insecure guest logons

d. Select Enabled OK.




If you're running Windows 11 Home edition, the guest fallback option is still enabled by default, so you're probably not reading this blog post. But if for some reason it is on, or you need to turn off SMB signing due to some third-party NAS, you will need to use PowerShell to configure your machine because there is no gpedit tool by default. To do this:

a. On the Start Menu search, type powershell then under the Windows PowerShell app, click Run as administrator. Accept the elevation prompt.

b. To disable SMB signing requirement, type:

 

Set-SmbClientConfiguration -RequireSecuritySignature $false

d. Hit enter, then hit Y to accept.

c. To disable guest fallback, type: 

 

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

e. Hit enter, then hit Y to accept.

 

At this point you will be working if Signing or Guest were your real problems. 

 

Important: we have not removed your ability to enable SMB1. All editions of Windows 11 have SMB1 disabled by default - this has been the case for over a year now and, in some editions, going back to Windows 10 - but you are free to re-enable it if you have a third-party NAS that only supports SMB1. SMB1 supports signing but your NAS may not, so the steps above for disabling signing can still apply. SMB1 always allows guest fallback and it cannot be stopped, so the guest steps are not applicable. If your third-party NAS still requires SMB1, it's likely listed here https://aka.ms/stillneedssmb1. If you find that it also doesn't support SMB signing, please let us know with the email address below. 

 


MS Office Instalation

  https://massgrave.dev/genuine-installation-media Windows 10/11 enterprise edition https://massgrave.dev/windows_ltsc_links MS office insta...