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: Most helpful
  1. Anonymous
    2024-10-21T22:05:46+00:00

    I did see with some amazement that PUBLIC was the new RECOMMENDED setting. No reason for this in my opinion and my little villa here with 3 computers. As of the moment now, I thought I could force connect 24H2 with both 22H2 machines. This works 25% of the time. Then there is one of the 22H2 machines that does not network with the other 22H2 machines but does fine with the 24H2. So I freaking give up. MS broke it I hope they fix it soon. Nothing seems to have what is called sustained connectivity. In short the only Windows 10 computer that is working correctly seeing the entire network is running 22H2 19045.5011. The rest of mine are hit and miss. I have tried EVERYTHING.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-21T19:45:19+00:00

    Thanks @fgf2001. I will give the public profile a try and report back tomorrow.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-21T19:24:25+00:00

    Hi @fg2001

    Not only can I not see other computers on the network from my 24H2 machine, it does not show the Readyshare USB connection of my Netgear router. So it does seem to me to be an issue with the settings of the 24H2 machine. Rather than deal with all other potential computers on my network let us focus on one of them running under 23H2 called HomePC (all others are similar 23H2 but not always connected). This is using build 22631.4317. From this I can see all other machines (including the Netgear Readyshare USB and my 24H2 machine). But it does not show up on the 24H2 machine's network in Windows Explorer. I can though set up a mapped network drive for this HomePC shared resources (so they aren't being blocked).

    The 24H2 machine is using build 26100.2033. File and printer sharing is set correctly as you have illustrated and both FDPH and FDRP are running on both machines.

    I am using ethernet connection for both machines. The same issues arise if I switch to wireless. Private network profile is deployed on both. Any thoughts?

    I have no idea about the USB Netgear router. You should post a question on their support site.

    My machines are connected with Ethernet to the Router and some with Wi-Fi.

    The Router is a 5268AC supplied by my Service provider (AT&T).

    As for the Network Profile I used to have Private, but I switched all machines to Public which is the recommended by MS.

    (Not sure why they recommend Public also for my Home network, but I have USB shared printer on my main PC and when using Printer sharing it was automatically turned on for Public networks. I think that was another bug of W11 23H2, no longer happening with 24H2. πŸ‘πŸ€·β€β™‚οΈ)

    After I saw that, I decided to use the recommended Public network settings even if I couldn't see a valid reason for my home network. πŸ˜΅β€πŸ’«

    I think it should work also if I change all back to Private networks, I'll probably change it back to Private as I always had it before. 😎

    Image

    Image

    Note that I use "Password protected sharing".

    My user ID is the same on all the PCs in my home network and I use Local accounts with password, easier for me to remember. πŸ˜‰

    Image

    Note that I don't use "Public folder sharing", On every PC I set up one shared folder that I use when I want to share files. πŸ˜‰

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-10-21T18:09:26+00:00

    Hi @fg2001

    Not only can I not see other computers on the network from my 24H2 machine, it does not show the Readyshare USB connection of my Netgear router. So it does seem to me to be an issue with the settings of the 24H2 machine. Rather than deal with all other potential computers on my network let us focus on one of them running under 23H2 called HomePC (all others are similar 23H2 but not always connected). This is using build 22631.4317. From this I can see all other machines (including the Netgear Readyshare USB and my 24H2 machine). But it does not show up on the 24H2 machine's network in Windows Explorer. I can though set up a mapped network drive for this HomePC shared resources (so they aren't being blocked).

    The 24H2 machine is using build 26100.2033. File and printer sharing is set correctly as you have illustrated and both FDPH and FDRP are running on both machines.

    I am using ethernet connection for both machines. The same issues arise if I switch to wireless. Private network profile is deployed on both. Any thoughts?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-10-21T17:30:20+00:00

    Unfortunately the "sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation" HACK does not work anymore. The dependency is created but does not stop FDResPub from "not doing its job" and having to stop and start as noted above or below. Also need to enable Printer & File Sharing in Firewall settings, especially the (Restrictive) ones. Hope this helps.

    I already tried it, and I said earlier that it did not work. πŸ˜œπŸ€·β€β™‚οΈ

    So, I removed it.

    Was this answer helpful?

    0 comments No comments