We had the same issue, and we rolled back to 23H2
Problem in network Windows 11 24h2
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
After updating to the new Windows 11h2, some machines experienced network issues with both cable and Wi-Fi. They connect but don’t get network access and receive an IP address starting with 169…, resulting in no internet or network connection. I updated drivers, firmware, and reset the network settings. The machines’ MAC addresses haven’t changed. Does anyone know what could be causing this?
Windows for home | Windows 11 | Install and upgrade
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.
269 answers
Sort by: Most helpful
-
Anonymous
2024-10-02T20:24:02+00:00 -
Anonymous
2024-10-03T13:32:18+00:00 We had the same issue, and we rolled back to 23H2
The same problem for the entire network. When I first logged in, I had no internet either on WiFi or Ethernet. Even with manual IP and it still doesn't work. At the stations that had functional Windows at the first restart, after the second restart we ended up in the same non-functioning situation. The only solution was rollback to 23H2. So it is not a DHCP problem, nor could it be a DHCP problem because even when you wanted to select the WiFi network, the option did not appear. Only bluetooth no WiFi connection to select.
-
Anonymous
2024-10-03T14:59:52+00:00 We have several machines that after upgrade to 24H2, the wireless connecting capability in the OS is completely missing. It is missing from the system tray and also not able to "connect" from the network control panel. Configuration of static IP accomplishes nothing because the wireless will not connect. This is a pretty horrendous problem for Microsoft to have inflicted on us.
And yes, we have done complete resets and full reinstalls of all the drivers.
We are disabling the deployment of 24H2 at this point and are forced to roll back some systems.
-
Anonymous
2024-10-02T21:05:52+00:00 I found a workaround: the DHCP is having issues, but if you set a static IP, it works.
Apparently, there is some problem with the DHCP.
-
Anonymous
2024-10-04T19:07:42+00:00 24H2 is what is causing it. We attempted rollback to 23H2 and it did not work. So far we have several machines bricked requiring a full rebuild from scratch. We are blocking 24H2.