[German]Short information for users or those switching to Windows 11 24H2. I have received reports that users suddenly notice sporadic network connection failures or run into network problems after switching to Windows 11 24H2 (adapters are deactivated and cannot be activated or do not work). Here is an overview of the error pattern and possible workarounds.
A first user report
I received the information via the Patchmanagement.org mailing list. A user reported on January 10, 2024 that he had a total of six (6) computers "in the last week" that had lost network functionality after updating to Windows 11 24H2. The error patterns were slightly different in all cases.
- On some systems, all network adapters were deactivated and could not be activated in the Windows 11 network environment.
- In other cases, the network adapters were activated in Windows 11 24H2, but the network connections simply did not work.
The person concerned writes that the Wi-Fi connection is not even displayed in the taskbar. There he only finds icons for Bluetooth or airplane mode. It is an Intel NUC, three Dell laptops and two Lenovo laptops. In other words, a colorful mix of hardware. The whole thing reminded me directly of the blog post Windows 11 24H2: Issues with VPN connections, Direct Access …,where broken network connections are mentioned.
Second user confirmation
A few hours ago, user Rory Monaghan joined the mailing list thread and confirmed network problems. He is using a Dell Inspiron and after upgrading to Windows 11 24H2 is suffering from his network connection also "crashing".
Sometimes when he tries to disable and re-enable the network adapter in the Windows 11 24H2 network environment, the network settings UI hangs and crashes.
In this situation, it then has to restart Windows 11 to get the network connection working again. This then works until the next network failure.
In the forum thread of the Patchmanagement.org list, other affected persons have reported similar error patterns – some did not associate it with Windows 11 24H2.
Workarounds for this problem
In this context, I also remember the blog post Windows 11 24H2: DHCP problem missing gateway entry from December 2024, which also deals with network problems and names a cause. There was a wild discussion at the time, and those affected reverted from Windows 11 23H2.
In the Patchmanagement.org list, Britt Adams mentions several solutions that could be used to try and solve this problem.
1. Remove the WinHTTPAutoProxySvc Dependency
Open regedit (Registry Editor)Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WcmSvc
Locate the DependOnService entry
Remove WinHTTPAutoProxySvc from the list, leaving only RpcSs and NSI.
2. Enable the WinHTTP AutoProxy Service
In regedit, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc. Locate the Start entry. Change its value from 4 (disabled) to 3 (manual).
3. Modify Windows Connection Manager
Open Command Prompt(Admin) Run the following command: sc config WcmSvc depend= RpcSs/NSI
Emin Atac writes that he has set a dhcp option with ipconfig /setclassid. The Windows 11 24H2 DHCP client does not send option 77 in the DHCP discover packet. Therefore, the client ends up with an APIPA IP because the DHCP server is not configured in its environment to offer an IP if the option is missing. In Windows 11 23H2, on the other hand, it works – and with a static IP address, the Windows 11 24H2 client also gets a network connection.
User RiversideKid writes that the challenge is to provide the user with a solution when the network is gone. You have added the local user to the local group of the network configuration manager. This allows most users to re-enable the adapter. But it doesn't always work.
Looks like Microsoft still has a problem with Windows 11 24H2, which is still unfixed in January 2025. Does anyone else have these problems and is there a known solution?
Similar articles
Windows 11 24H2: Issues with VPN connections, Direct Access …
Windows 11 24H2: DHCP problem missing gateway entry
Same problem w11 on laptop Lenovo L15 gen 1.
Can anyone confirm if the problems that are happening are showing up on machines that have both 24h2 and Wireguard VPN on them? We've seen this a lot on our work machines with Wireguard after 24h2 installs but not at home.
Quite Same problem here (I use a LAN cable) on 02 Feb 2025 and still no solution
Similar issues seen here, but ours had been when 24h2 was installed, with Intel 219 nic chipsets, and Webroot. If you roll 24h2 back, no issue (atleast up until this week for us). Or if you uninstall Webroot, then it seems to be fine for our systems we support. We have seen Mcafee cause same issues, and have uninstalled and ran with Windows Defender, which does not seem to have issues. We have updated firmware on our Asus motherboards, and Intel nic drivers, which about 9months ago, seemed to fix this issue. But at that time there were no tech articles or blogs I could find of any one elese having similar issues. But now it has progressed to instantly once 24h2 is installed, having network disconnect issues; regardless of which nic driver version or motherboard firmware installed. For us the nic never has an issue with Dhcp, and even putting a static ip on for us made no difference. We have reached out to Webroot, and they want us to do their testing for them, even though I don't believe it is a Webroot issue but Microsoft – even though few years back Webroot did have a network dropout issue with their app. Also will mention another fix we found was to install a usb 3.0 to gigabit adapter, that is not an Intel chipset, and that seems to work also for us. This week however, we have started seeing 23h2 doing exact thing on some machines, confirmed by System Even Viewer showing nic drop offs every 3-5min. BEYOND frustrating! Hope this helps, and appreciate your post.
same issue with a DELL 5820 since upgrading to 24H2, no webroot, using sentinel.
Did everything including drivers updates, all DELL updates, all suggestions on the web, consulted CHATGPT, nothing works. Seems to be the problem goes away after 10 minutes of usage. If I didn't know better, I'd say it has to warm up :)))))
But seriously – this is annoying as hell. Hope MS will get a patch.