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 No comments

269 answers

Sort by: Oldest
  1. Anonymous
    2024-10-07T17:51:35+00:00

    So For my issue, (at least on one machine, we have 2 right now with the problem) the WinHttpAutoProxySvc was disabled (from install). Made this change to the registry here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc"Start"=dword:00000003 rebooted and resolved our issue. Internet back and working without anything else.

    Not sure why this would be the case but it worked, I will try the other system and let you know.

    ***UPDATE***

    Maybe spoke too soon! Not shocked, but when we rebooted that machine again (after the initial reboot and the internet was working on WIFI) the Start DWord in the registry had gone back to 4. And the internet did not work until the registry was changed and rebooted again.

    So not sure what to say now.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-10-07T18:25:53+00:00

    to me, the value is in "3" and not working... :(

    complementing, my network adapter is a "Intel(R) Wi-Fi 6E AX 211 160MHz"
    current version "23.60.1.2" and Driver Date "6/3/2024" .... :/

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-10-07T19:06:30+00:00

    After some more messing around I think this time I got it.

    The WLAN AutoConfig service has a dependency on Windows Connection Manager.

    Windows Connection Manager has a dependency on the WinHTTP Web Proxy Auto-Discovery Service.

    I went to the registry and removed the dependencies on the WinHTTP Web Proxy Auto-Discovery Service. Rebooted a few times and success.

    I base this upon the 23H2 services NOT having the dependencies on the WinHTTP Web PRoxy Auto-Discovery Service.

    Here is the change I made in the Registry: NOTE THIS IS FROM MEMORY

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wcmsvc

    DependOnService = REG_MULTI_SZ:RpcSs NSI

    I Removed the 3rd Service listed there which should be the WinHTTPAutoProxySvc

    This has seemed to resolve my issues for now.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-10-07T19:26:54+00:00

    just for reference, in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wcmsvc

    DependOnService" I have only "RpcSs". But let's see if someone else can fix the issue using your solution.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-10-07T19:49:13+00:00

    Between your posts and a couple other things I've been reviewing, I set up a custom event view that aligned from the time I performed the update to current (types 7000, 7040: event levels warning, error, information).

    By doing this I was able to isolate that the "WinHTTP Web Proxy Auto-Discovery Service" was changed from demand start to disabled in the process of updating to 24h2.

    All the other processes discussed are contingent on that process working, which led to the other failures (including the WLAN process that we're trying to get working). Each boot after that change had resulted in the others all failing.

    [removed info about how to enable WinHTTP process] <- I ended up removing the dependency for WinHTTP from wcmsvsvc per Ryan's comment above.

    Once I did this, everything has been working for multiple reboots.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments