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

69 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-10-17T16:48:52+00:00

    @GazzaGDBB,

    26100.2033, is one update behind mine, the problem I described was happening with Build 26100.2152 which is the latest 24H2 update in R.P..

    All the other machines on my network are on 23H2.

    Sorry, I don't have 26100.2033 anymore, so I cannot check out the same configuration you have.

    I may have another PC where I can install 26100.2033 and see what happens. 🤷‍♂️

    From your description you don't see any of the other PCs on the network from the one with 26100.2033.

    Edit:

    I got one machine with Build 26100.2033, sorry I cannot reproduce your problem, I can see all the other PCs on the network from the one with 24H2. (Showing below as K3-PRO-24H2) no problem from any of the other PCs either. 🤷‍♂️

    Without seeing your exact configuration settings, I cannot even guess what could be causing your issue. 🤷‍♂️

    Image

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-10-18T18:55:19+00:00

    You are a star for trying! Thank you. What you are showing is exactly what I would have expected/hoped for. I did a clean install of 24H2 2033 with no transfer of settings. Exactly the same problem - can't see any devices on network except the Synology NAS. Only difference from your set up might be Win11 Pro vs Home. I'll probably give up on 24H2 and stick to 23H2 which does work OK. If I discover anything I will post it here.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-10-19T02:11:52+00:00

    YES ABSOLUTELY TRUE... SOMETHING BROKE SPENT 8 HOURS TODAY TRYING TO FIX IT. STILL BROKEN. THANKS A LOT MICROSOFT.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-10-19T02:13:02+00:00

    8 HOURS IS ENOUGH SOMEBODY TELL ME WHEN IT IS FIXED!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-10-19T02:38:44+00:00

    You are a star for trying! Thank you. What you are showing is exactly what I would have expected/hoped for. I did a clean install of 24H2 2033 with no transfer of settings. Exactly the same problem - can't see any devices on network except the Synology NAS. Only difference from your set up might be Win11 Pro vs Home. I'll probably give up on 24H2 and stick to 23H2 which does work OK. If I discover anything I will post it here.

    I had a PC on Public Build 22631.4317 and last night W.U. downloaded and installed 24H2 without asking.

    The update failed and reverted back due to this error 0xC1900101, there was no subcode specified.

    After that I tried to upgrade with ISO 26100.1742 and that completed fine. But then I found that there was another problem on the network where it kept switching the profile to Public instead of Private after every reboot, also the setting for the profile was missing in the Network settings.

    Image

    https://aka.ms/AAsy7he

    This setting options were completely missing; I had to restore my backup with 23H2 22631.4317 to get this back to work properly.

    Yet, I had 2 other machines upgraded to 24H2 that did not have this problem at all. Very inconsistent results, 24H2 doesn't seem ready for prime time.

    I wasted too much time trying to see why this specific machine did not work like the other 2.

    For now, I'm back on 23H2, I may give it another try on the weekend. 🤷‍♂️

    Image

    Was this answer helpful?

    0 comments