Problem in network Windows 11 24h2

Anonymous
2024-10-02T19:40:22+00:00

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.

0 comments No comments

269 answers

Sort by: Newest
  1. Anonymous
    2025-02-27T17:38:11+00:00

    I solved the problem in the same way. I reinstalled my two operating systems (on the same PC). I used the USB installation media that I created three weeks ago (W1164bit 24H2).

    What was really strange was this:

    I reinstalled the first operating system successfully, and everything worked perfectly right away. So, I proceeded to install the second operating system (on a different partition, but still on the same PC). After booting into the newly installed second operating system (version 24H2), I experienced the same problems – the network wasn't working properly. I reinstalled this operating system again, but with the same results. Therefore, I was forced to copy the first working operating system to this partition to make it work. That's really really strange, isn't it?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-02-27T17:35:43+00:00

    I certainly didn't hope you had to go back to square one and do a clean install? But you know if your problems have gone away, I guess there is a win here.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-02-27T17:20:23+00:00

    While After months of being hopeful that Microsoft would resolve an issue they clearly created, we have moved on. We paused updates for the devices experiencing this issue and revisited the update every 5 weeks. Everytime the 24h2 update was installed the network connectivity would fail for both ethernet and wifi. Each time we rolled back to Windows 23H2 resolving all of the issues until the next attempt. We have tried every fix posted in this community during our testing none of which resolved the issue.

    Ultimately we have re imaged the devices that were experiencing this problem about 2.5% of our devices and this has resolved the issue. Each device is now running 24h2 without issue.

    Thank you to everyone who has taken the time to try and help out here.

    Hi JethroAG, what do you mean with "we have re imaged the devices"? Did you perform a new install?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-02-27T17:17:52+00:00

    Thanks for posting. Same boat here. Have tried the update 3 times over the last 4 months hoping they would resolve this issue.

    Each time, after installing the update, my wired network bounces up and down with "media disconnected".
    Disappointing that this hasn't been resolved. I just don't have time to reimage my workstation and fix the resulting issues.
    If anyone from Microsoft wants to look at the issue, I'd be happy to help.

    John

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-02-27T17:08:54+00:00

    While After months of being hopeful that Microsoft would resolve an issue they clearly created, we have moved on. We paused updates for the devices experiencing this issue and revisited the update every 5 weeks. Everytime the 24h2 update was installed the network connectivity would fail for both ethernet and wifi. Each time we rolled back to Windows 23H2 resolving all of the issues until the next attempt. We have tried every fix posted in this community during our testing none of which resolved the issue.

    Ultimately we have re imaged the devices that were experiencing this problem about 2.5% of our devices and this has resolved the issue. Each device is now running 24h2 without issue.

    Thank you to everyone who has taken the time to try and help out here.

    Was this answer helpful?

    0 comments No comments