Windows 11 update 24H2 changes network access

Anonymous
2024-07-22T06:06:40+00:00

I have two pc's that are almost identical hardware, with W11 Home, but one has not yet updated to 24H2 while the other has.

The apps links shown on the bottom of this image are not present on the 24H2 version, which is a retrograde step as finding the settings app should be easy..

Annoyingly the 24H2 update seems to have broken the network sharing, and finding advanced sharing settings to enable file transfer isnt easy.

Its been working until this morning, but now I'm unable even to see other devices from the "un-updated" machine.

*** Moved from Windows / Windows 11 / Windows update ***

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

69 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-10T10:59:25+00:00

    I tried everything, and I think I finally found the culprit. In Windows Defender Firewall with Advanced Security, 24H2 does two things: (A) disables all File and Printer Sharing rules, and (B) adds a bunch of rules called File and Printer Sharing (Restrictive) [blah blah blah].

    In some cases, even if (A) is not done, (B) is done and something else is disabled that breaks file sharing.

    The solution is:

    1. Go to Windows Defender Firewall with Advanced Security => Inbound Rules
    2. Scroll down to File and Printer Sharing. Look at column "Profile" and make sure all rules with your correct Profile are enabled (right click - enable)
    3. Enable all items at the bottom which have the word (Restrictive) in the name. The most important one is called File and Printer Sharing (Restrictive) (SMB-In).

    To be clear, just enabling File and Printer Sharing (Restrictive) (SMB-In) should do it, but I went overboard to make sure the computer responds to pings, etc.

    Thanks for this Andrew - but afraid it didn't work for me and my 24H2 PC. I have tried all the suggestions I can find, including yours, but nothing seems to work. My Netgear router USB attachment (Readyshare) doesn't show under Networks, nor do any computers on the home network. Interestingly, the only thing that does show up is a Synology NAS. However, the problem 24H2 computer shows up fine on my other 23H2 computers on the network. Please post if you come up with any other suggestions!

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-10-13T03:57:09+00:00

    omg thank you

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-10-17T01:09:21+00:00

    What is the exact 24H2 Build # you are using?

    Here is the problem that I saw with Build 26100.2152 and reported by other users:

    After updating to 26100.2152, I found that "File and printer sharing" got turned off, and I had to turn it back on to get my local network to work properly again.

    I also had to enable the new option in the security settings "File and printer sharing (Restrictive)"

    Image

    Enabling the above setting got rid of the yellow warning message showing on 1st shot.

    This security setting "File and Printer Sharing (Restrictive)" was disabled in one machine after the update to 26100.2152.

    Image

    I had to enable manually "File and Printer Sharing (Restrictive)", in my case just for Private network which is what I 'm set for.

    After that the file sharing started to work correctly.

    Image

    When it failed before changing the settings, it was just hanging trying to access the 26100.2152 PC and eventually pop up the message below.

    It worked fine after fixing the settings described above.

    Image

    What's new in Windows 11, version 24H2 for IT pros | Microsoft Learn

    SMB firewall rule changes

    The Windows Firewall default behavior has changed. Previously, creating an SMB share automatically configured the firewall to enable the rules in the File and Printer Sharing group for the given firewall profiles. Now, Windows automatically configures the new File and Printer Sharing (Restrictive) group, which no longer contains inbound NetBIOS ports 137-139.

    This change enforces a higher degree of default of network security and brings SMB firewall rules closer to the Windows Server File Server role behavior, which only opens the minimum ports needed to connect and manage sharing. Administrators can still configure the File and Printer Sharing group if necessary as well as modify this new firewall group, these are just default behaviors.

    For more information about this change, see https://aka.ms/SMBfirewall. For more information about SMB network security, see Secure SMB Traffic in Windows Server.

    4 people found this answer helpful.
    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2024-10-17T10:34:56+00:00

    Hi - thanks for taking the trouble to reply. However, your advice points have I believe been covered before in previous posts. I checked through all items again and still no progress. My build on the 24H2 machine is 26100.2033. The other 4 machines frequently connected on the network are on 23H2 and are working fine. It is just the 24H2 machine which is not showing devices under Explorer Network. I can however identify and link to the other machines (and the Netgear Router's Readyshare USB) using network shares and mapping. Below is a screenshot of Network devices when running DESKTOP-7RFCN5O under 23H2.

    The second screenshot is of what shows under 24H2 after all the advice and suggestions from you and others had been taken on. The only device showing under Network is the NAS.

    Of course, this may be something straightforward that I have overlooked. But it is mighty frustrating. Any ideas? Please note that I have tried everything suggested previously on this set of posts.

    0 comments No comments