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-09T14:49:38+00:00

    I tested several computers yesterday and restored them to full functionality by simply removing the winhttpautoproxysvc service from dependency.

    That service should be disabled because it is insecure.

    The exact fix I found to work 100% of the time is:

    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.

    Ok, yes, this does work - but only as a temporary workaround, not a full solution. For a one or two device situation, sure, but not for an enterprise with laptops and docking stations. MS needs to come out with a proper FIX for this.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-09T14:57:47+00:00

    I fully agree with your statement that MS NEEDS to come out with a proper fix for this.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-09T15:48:05+00:00

    We just started preparing new Lenovo computers with W11 24H2, the clean installation does not present any problems with the wireless adapters, we disabled Windows Update to avoid the installation of KB5043178, at least with this we finished customizing the computer, entering the domain, installing AV and encrypting the disk without presenting the network problem again. In case you can replicate it in your deployments.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-10-09T15:56:04+00:00

    We just started preparing new Lenovo computers with W11 24H2, the clean installation does not present any problems with the wireless adapters, we disabled Windows Update to avoid the installation of KB5043178, at least with this we finished customizing the computer, entering the domain, installing AV and encrypting the disk without presenting the network problem again. In case you can replicate it in your deployments.

    The issue I'm seeing doesn't happen on Wireless. It's only happening when using a USB based network adapter.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-10-09T16:20:04+00:00

    I tested several computers yesterday and restored them to full functionality by simply removing the winhttpautoproxysvc service from dependency.

    That service should be disabled because it is insecure.

    The exact fix I found to work 100% of the time is:

    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.

    Interestingly, after a reboot, the issue returned. I also found that running netsh int ipv4 reset will allow dns to propagate until I move to another usb port.

    I also had a person that doesn't disconnect her docking station report that after I changed the service dependency, the problem came back. Ultimately I disconnected the wired network connection from the dock and she's on wireless now which has not been an issue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments