I also had problems with the Internet after the update, rolling back to the previous version solved the problem
Problem in network Windows 11 24h2
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-17T21:53:29+00:00 -
Anonymous
2024-10-17T13:11:09+00:00 How can i block 24H2 update installation?
-
Anonymous
2024-10-16T22:26:31+00:00 The fix for no Wifi:
Open Regedit as admin
Look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wcmsvc
Open DependOnService and remove WinHTTP Web Proxy Auto-Discovery Services.
Click OK and reboot.
We tried this solution on one computer, and it worked. Many thanks to schluety
-
Anonymous
2024-10-16T15:38:22+00:00 In our work environment we have WPAD disabled. When I got the new Surface 11 pro and put on the domain it removed WIFI completely from windows even though the adapter is still there. In checking the service dependacies with the 23h2 version, the WLAN service now depends on WPAD to be running. I don't think I can roll back as when I booted this Surface is auto updates before anything.
-
Anonymous
2024-10-16T13:16:22+00:00 Hi all
we had the same issue. It is caused by Win11 Device Security settings, Win 11 23H2 suffers the same fate. These features I believe are now turned on by default with this release when using Enterprise and Education Versions on Win11. If using a GPO you can set this feature to Disabled here. Howver this substantially reduces your security posture so is not recommended.
The underlying issue is that MS-CHAPv2 is no longer a secure auth method so you will nead to switch to EAP-TLS Certificate Based Auth when using Wireless Authentication. I need to emphasise this was our experience so, use this at your own risk (TEST TEST TEST!!!) and please use this setting with caution as it is a bit of a mission once you Disable this setting to reinstate default Windows Security settings such as Core Isolation, Driver Guard etc... but it is a temporary work around for now.
We have now permanently overcome this issue by means of configuring our Enterprise CA, to issue Machine and User Certs throughout our Domain using Auto Enrollment GPO Policies and authenticating using EAP-TLS Thankfully the issue is no more....