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.

0 comments No comments

69 answers

Sort by: Newest
  1. Anonymous
    2024-10-23T21:24:52+00:00

    That's what I get too. Need to run FDResPub restart to see "host" PC. Still experimenting with Netgear. But given this is fine on 23H2, I do think MS has blocked its appearance under Network. Can't find anything in the firewall - but I don't know what most of the settings are for anyway!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-23T03:01:40+00:00

    Hello all,

    Another peculiar behavior of FDResPub common to all Windows 11 Builds. I did a few more tests to see how it behaves.

    The service is set by default to Manual (Trigger Start).

    The Trigger Start is only working if the profile is set for Private network, when set for Public network the trigger is not working, and the service never runs unless started manually. πŸ˜‚

    This makes sense considering that with Public network by default they try to keep the PCs non discoverable.

    When the profile is set for Private network the trigger works and the service is running after Windows is up.

    Still, they have the problem causing the local PC not to show on the network unless the service is restarted.

    Only intermittently it shows up without the restart of the service.

    Even if it shows, it disappears when the file explorer window is closed and then reopened around 5 minutes later. πŸ˜‚

    This same problem has been going on for years and never got any response from Microsoft to the various FBH reports submitted.

    I just filed another one about this issue.

    Please upvote.

    https://aka.ms/AAt2mlc

    Image

    Image

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-22T23:22:18+00:00

    Hi - actually the suggested means of switching on smb I have already actioned. On 23H2 and before this works. It doesn't on 24H2.

    Maybe they blocked it with the Firewall. πŸ€·β€β™‚οΈ

    Does it have anything to do with SMBDirect? I have it disabled because I don't use it, but I have seen other users that have that enabled. 😎

    Perhaps your Netgear USB Readyshare can add Windows credentials? 24H2 does not like Insecure log in.

    Image

    Maybe this below is your specific issue with the USB Router? You may need to AllowInsecureGuest?

    Microsoft to block access to routers with USB storage in Windows 11 24H2 | SNBForums

    About the network credentials in Windows 11 new update 24H2 - Microsoft Community

    Windows 11 24H2 and Insecure Guest Logins settings - Microsoft Community

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-10-22T21:02:49+00:00

    Hi - actually the suggested means of switching on smb I have already actioned. On 23H2 and before this works. It doesn't on 24H2.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-10-22T17:28:52+00:00

    @GazzazGDBB,

    Glad to hear that you got it working.

    As for the FDResPub problem, it has been around for years, and MS has been ignoring the reports.

    We need more upvotes on the FBH reports to try to get MS to finally fix the bug.

    About SMB1, it can probably still be enabled and allowed through the firewall, even if they recommend not to use it.

    Let us know how that goes. πŸ˜‰

    Image

    Was this answer helpful?

    0 comments No comments