Problem in network Windows 11 24h2

> but I also believe I cannot stay at 23H2 forever

The Microsoft Product Lifecycle for the "23H2" release of Windows 11 states that updates to it will end after mid-October 2025. So, you can stay with "23H2" for a few more months, with security updates through October 2025, but no security updates in November 2025, and beyond. It becomes "paddle your own canoe".

So, Microsoft has a few months (Feb/Mar/Apr/May/June/July/Aug/Sept/Oct to design & release an update, before the "sunset" of this release.

Windows Update probably will post a message about the end of service for "23H2", as it approaches its sunset. It did, for an earlier release.

I observed the same problem immediately after upgrading my samsung book2 laptop to 24H2. The wireless network stopped working most of the time, but not always. But mcAfee vpn always fails to connect, without exception. I had to roll back to 23H2 and the problem disappeared.

Given the problem has been there for at least 3months now, I'm wondering whether Microsoft already have a fix to this problem. I wasted hours following some posted fix/workaround (which worked for me sometimes, but mcAfee fails, regardless), and would prefer to take an official version with the fix, but wondering how long I have to wait, and whether windows would allow me to wait for that long.

Here are the policies to paste into a GPO if you want a more global fix

<?xml version="1.0"?>

<Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="IPHelperDependOnSVC" status="DependOnService" image="6" changed="2025-01-22 15:48:15" uid="{822B1313-DD9D-4661-BF3D-053A99C704EA}"><Properties action="R" displayDecimal="0" default="0" hive="HKEY_LOCAL_MACHINE" key="SYSTEM\CurrentControlSet\Services\iphlpsvc" name="DependOnService" type="REG_MULTI_SZ" value="RpcSS tcpip nsi"><Values><Value>RpcSS tcpip nsi</Value></Values></Properties></Registry>

<?xml version="1.0"?> <Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="WinConMgrSrvDependOn" status="DependOnService" image="6" changed="2025-01-22 15:48:09" uid="{8F16FCB8-6298-4A90-86D7-F7DC7A323A39}"><Properties action="R" displayDecimal="0" default="0" hive="HKEY_LOCAL_MACHINE" key="SYSTEM\CurrentControlSet\Services\Wcmsvc" name="DependOnService" type="REG_MULTI_SZ" value="RpcSS nsi"><Values><Value>RpcSS nsi</Value></Values></Properties></Registry>

Command lines to adjust the dependency which may be easier for some. I did notice some machines did not have the WinHttpAutoProxySvc as a dependency for the Windows Connection Manager service, so it appears possibly dependent on upgrade paths for machines.

sc config iphlpsvc depend= RpcSS/tcpip/nsi

sc config Wcmsvc depend= RpcSS/nsi

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.