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.
However I've tried also this solution and of course is not useful for my PC. I don't know if I'm the only one with this particular problem because my internet connection isn't completely absent but it's slow, if I reboot my pc, sometimes also 5/6 times, internet speed is normal again until the next reboot. I don't know at this point, if Microsoft really want solve this problem or not because 4 month are passed and with the last update nothing is changed
You are getting confused. The screenshot I posted was of 2 different services that had dependencies on WinHTTPProxy. One has TCPIP, the other did not. I only removed the WinHTTPProxy dependency from those services.
ik gebruik wifi
I don't understand if this workaround is useful only for who connect through wifi or also with LAN because I use a LAN cable and if yes I don't understand precisely what I do on my PC to apply this patch. In the previous page Eric Holzhueter has posted this solution but I see that he suggest to remove WinHTTPAutoProxySvc but in the screenshot I see that then he has removed tcpip... Can you explain better?
Looks like they don't mention anything in regard to the problem with the network adapters, yet. I think we'll have to wait until the next full patch that they send out. In the meantime, I think the fix that includes the WinHTTP service will be your best bet.
