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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-22T04:41:55+00:00

    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.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-10-09T08:26:44+00:00

    This simple fix works perfectly for me:

    FIX FOR NETWORKING ISSUES AFTER Windows11 24h2 major update

    Search for and open "Local Group Policy Editor" in settings:

    Navigate to:

    Local Computer Policy: Computer configuration: Administrative Templates: Network: Lanman workstation: Enable insecure guest logons - Enable

    Reboot and problem is solved

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2024-10-07T14:30:14+00:00

    Cara, como mencionei no post acima.

    Resolvi esse problema desativando a opção 43 no escopo DHCP.

    É provável que o roteador da VIVO esteja com essa opção no DHCP Server habilitada. Tenta verificar se tem opções de escopo habilitado no DHCP Server do roteador.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-10-03T21:18:16+00:00

    ipv6 works perfectly for you too, right?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments