Windows 11 update 24H2 changes network access

I am not using Ethernet but Wi-Fi. Any ideas?

Check the current profile for your Wi-Fi and enable Network discovery and File and printer sharing accordingly.

Looks like they are trying to force Public Profile without explaining why. 🤬🤷‍♂️

I am not using Ethernet but Wi-Fi. Any ideas?

Yeah and other stuff i left out did not seem to matter one way or the other. I am a retired tech. I began building Windows PCs in 2000. So many have issues with Windows and say good riddance get a Mac. But let's see been doing this for 24 years one way or another I am sure they know it is a problem. No point in rolling back because going to have to go forward sooner or later. Problem for my local home network is a nuisance but not a game changer for now just a pain in the asteroid.

I gave it another try today, and on this machine, they definitely eliminated the option for selecting Public or Private with my Ethernet connection.

The default was set to public profile.

Magically when I checked for updates again the option showed back like I had it before the upgrade. MS magic puzzle. 😂😂😝

just disappeared again after a reboot and defaulted back to Public. 🤐🤬🤷‍♂️

The only workaround to get my home network working again was, by enabling Network Discovery and File and printer sharing also on Public network.

That is not what I was looking for, but for now I'll live with it, till MS comes out with a proper fix.

Strange that 2 other machines at the same Build 26100.1742 do not have this bug. I cannot figure out what the difference is. 😝🤐🤬

Also, on this machine the Profile options are only missing on the Ethernet connection, while they are still available on the Wi-Fi.

Pretty messy puzzle! 😂😝

Edit:

I found an old post that solved the specific problem that was not showing the Network option for Public or Private on Ethernet.

As you can see above it also said "Unidentified network"

[SOLVED ]Unidenified Network, No Internet Access - Microsoft Community

Try to reset network connections: Open PowerShell or CMD and run as administrator, copy and paste the following commands by pressing enter at the end of each command line:

netsh winsock reset

netsh int ip reset

netsh advfirewall reset
ipconfig /flushdns

Restart the computer at the end of all commands.

After executing the commands above and rebooting, everything was back to normal and showing the profile type on the Ethernet. 👍

Second thing I had to enable this setting in the Firewall to allow the new "File and Printer Sharing (Restrictive)".

That is what they now use with 24H2 Build. 26100.2152, the same applies also to Dev Build 26120.2130.

Yeah and other stuff i left out did not seem to matter one way or the other. I am a retired tech. I began building Windows PCs in 2000. So many have issues with Windows and say good riddance get a Mac. But let's see been doing this for 24 years one way or another I am sure they know it is a problem. No point in rolling back because going to have to go forward sooner or later. Problem for my local home network is a nuisance but not a game changer for now just a pain in the asteroid.

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.

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. 🤷‍♂️