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.
Result: doesnt work for me
The only workaround that I could apply is Workaround 2: registry hack, because I already have a static IP for my machine and DNS already setted.
Rebooted my PC: internet connection really slow or absent.
Rebooted 2 times and I'm here to write this post.
How are you measuring the "slowness" ?
After restarting, open the Windows Task Manager,
or run the "resmon.exe" Resource Manager.
It could be Windows Update checking for updates,
monopolizing your CPU & your Internet.
It could be Disk Defragmenter, monopolizing your disk-drive.
How are you measuring the "slowness" ?
After restarting, open the Windows Task Manager,
or run the "resmon.exe" Resource Manager.
It could be Windows Update checking for updates,
monopolizing your CPU & your Internet.
It could be Disk Defragmenter, monopolizing your disk-drive.
I'll try, but I don't tkink because:
> I'll try, but I don't think
When you do try the advice freely given to you, please reply here.
I was able to solve this issue on my network. It was due to dependencies that appear to have changed with 24H2.
On my network I disable the WinHTTP proxy service as it is a legacy service and also a security vulnerability. This caused no issues with wifi until 24H2.
The Windows Connection Manager relies on WinHTTP. WLAN Autoconfig relies on Windows Connection Manager. If WinHTTP cannot start, then neither can WLAN Autoconfig.
The fix here is removing the WinHTTP dependency in the registry or using the sc command line. Just deleting the WinHTTPAutoProxySvc from the following registry keys and rebooting will allow wifi to work again if this is what is blocking yours.
