This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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?
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.
The update so awaited is arrived, it's named KB5050094 and is possible to download it just now without wait 11 february, but it hasn't solved the bug! I think my Windows 11 is corrupted and I must format completely my PC but now I will disable windows Update because I don't trust Microsoft anymore
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Finally I have done this attempt, how I have said is not related. My CPU is free, the slowness has nothing to do with my CPU, is only related to this terrible update and Windows from months doesn't fix this bug!
Lee: Microsoft releases updates at 10 AM Pacific on the second Tuesday of each month. January 28 is not the 2nd Tuesday.
Microsoft also releases what they call "out-of-band" updates, after they determine that a security vulnerability is "in-the-wild" and is being exploited.
So, you probably will have to wait until Tuesday, February 11, 2025.
this is still the same issue and its it january 28
