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: Most helpful
  1. Anonymous
    2025-04-03T18:33:22+00:00

    I believe people have been misguided with the amount of fat in this thread. The solution to this fix is by simply removing the winhttpautoproxysvc service from dependency.

    HKLM\System\CurrentControlSet\Services\WcmSvc

    In the root of the key, look for value DependOnService.

    Edit it.

     

    Remove WinHTTPAutoProxySvc

    Save.

    Start Windows Connection Manager service. Start WLAN AutoConfig service.

    Then location services complains about being off. Go into Settings, Location. Turn OFF the notifications about location services being off.

    It might be a solution on your machine, doesn't mean it's right for everyone else. None of the things have completely fixed my problem, although some have made it more bearable in that it only cannot find my Internet sometimes on coming out of sleep, and more likely when restarting Win 11.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-03-10T16:32:18+00:00

    This is what I have found so far, I have 2 PCs and a Laptop, the PCs are almost identical except one is built in graphics (PC1) and the other has a card (PC2)

    PC1 has had the problem of not connecting to the Internet sometimes, both resuming from Sleep and Win-X U Restart. I have tried various things in this long thread and disabling IPv6 in the adaptor settings does help, before that it was a nightmare trying to get an Internet connection. At least now it sometimes connects on resuming from sleep

    Here is what I found though it does appear to be a timing problem with the Network Adaptor not finding the connection that is causing it, if after resuming or a Restart and it comes up with No Internet, disabling the adaptor and waiting approx 30-40 seconds then re-enabling it, it finds the connection, there is the odd occasion I have to use the Diagnose option and Restart the Adaptor to get it to work.

    PC2 & Laptop were updated to 24h2 quite a while after PC1 and have never had the problem.

    Microsoft really needs to get this sorted out.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-02-01T14:45:49+00:00

    You are getting confused. The screenshot I posted was of 2 different services that had dependencies on WinHTTPProxy. One has TCPIP, the other did not. I only removed the WinHTTPProxy dependency from those services.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-02-01T07:42:36+00:00

    I don't understand if this workaround is useful only for who connect through wifi or also with LAN because I use a LAN cable and if yes I don't understand precisely what I do on my PC to apply this patch. In the previous page Eric Holzhueter has posted this solution but I see that he suggest to remove WinHTTPAutoProxySvc but in the screenshot I see that then he has removed tcpip... Can you explain better?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-01-31T20:03:32+00:00

    Looks like they don't mention anything in regard to the problem with the network adapters, yet. I think we'll have to wait until the next full patch that they send out. In the meantime, I think the fix that includes the WinHTTP service will be your best bet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments