Problem in network Windows 11 24h2

Anonymous
2024-10-02T19:40:22+00:00

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.

0 comments

269 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-01-22T15:42:44+00:00

    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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-22T15:50:36+00:00

    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>

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2025-01-26T21:03:21+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2025-01-27T00:10:08+00:00

    > 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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-01-28T02:56:30+00:00

    this is still the same issue and its it january 28

    Was this answer helpful?

    0 comments