Problem in network Windows 11 24h2

Yes, this works—a direct and simple solution. Just read and follow along.

I have had the same issue as many have mentioned. Updated to 24H2 and bang my network sharing no longer functions. I am running a private network with shared access to Everyone connected to my network. I use this network as a backup solution between my house and my computer repair shop. Hopefully EVERYONE that is having problems with 24H2 killing their home network sharing will read this fix. This worked for me on all 3 of my networked computers. Two of my computers are running Windows 11 Pro 24H2 and one is running Windows 11 Home 24H2. Perform the following steps:

1.   In the seach box immediately to the right of the Start button type gpedit.msc, you will see the Microsoft Common Console Document; click that:

1. In the left pane under Local Computer Policy, navigate to Computer Configuration\Administrative Templates\Network\Lanman Workstation.
2. Open Enable insecure guest logons, select Enabled, then select OK.
3. Restarting computers on the network is likely not necessary, but I did so just as a Nyaaaaa because by this time I was aggravated. This immediately made my networked computers visible and accessible. I didn't have issues with WiFi connectivity only the loss of my network sharing visibility and access. I hope this helps!

Use IPCONFIG /ALL

and examine whether a fake DNS server (which is not advertized by your DHCP server) has been inserted on top of the list of DNS servers.

This DNS server having an IPV6 address does not resolve correctly, especially your internal hosts.

Also your local domain suffix is not taken into account.

If I disable IPV6 at the interface level, the networking seems to be alright.

As I had also problems with the RDP client, I decided to revert to 23H2 (remember: this is possible only for 10 days after the upgrade)

In this thread, one person suggested to disable IPv6 on their computer's networking configuration. Did you try that?

Thank you Melvin Klassen for the detailed response. As the origin of this thread from months ago when I first troubleshoot these issues related to Windows update 24h2. This issue is 100% related to the device and something changing within the update. I now have a few computers in our enterprise network running Windows 11 that experience this issue after the update is installed. Today I took a different a route and attempted multiple of the "solutions" found within this thread to no avail.

The issue is 100% related to the updated as rolling back once again resolved all the issues. The issue is 100% related to the update, but does not seem to effect all devices, for instance I am on a similar model Dell Precision laptop running a similar dock as the computer with the issue today. The issue affected two physical ethernet NIC's as well as the WiFi NIC.

When I have more time I will troubleshoot the issue again and see what new things I can chase down while Microsoft turns a blind eye!

For anyone else who experiences the issue attempt to ping or remote desktop into a local computer by IP address. Also attempt to ping an outside source by IP address 8.8.8.8 for instance. If this works it will help narrow down whatever is causing the issue. I was successful in this today proving I have network, but DNS is not resolving correctly or being blocked by some change 24h2 is making.