Problem in network Windows 11 24h2

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.

If you have AD check if any GPO disable this service. The problem solved for me as you say with registry key.

Well, that's a wrinkle with the 23h2's.

My event viewer showed that service becoming disabled during the update process and then when I looked at the dependencies that was the root one of the group that was causing issue. I'm sure we'll find out something from Microsoft soon-ish with a fix, but first it needs to be acknowledged that users are experiencing it. For my part, I've documented my experience here and in the feedback hub.

For my device, at least, the "WLAN AutoConfig" wouldn't start because it was dependent on the "Windows Connection Manager," which wouldn't start because it was dependent on "WinHTTP Web Proxy Auto-Discovery Service."

That said, I think you're on the right path that WinHTTP should not be in the chain of dependencies.

EDIT: I went and removed the dependency and disabled WinHTTP. Everything is working well and this seems like the better interim path until Microsoft releases a fix. That service is a potential security risk.

Hi, I tried it on 2 desktops, one laptop and one Surface and removed this WinHTTPAutoProxySvc , rebooted the workstations and it worked. Windows 11 23H2 does not have this dependency.

That is interesting, but I want to point out that on my current machine a 23H2 system, the WinHTTP Web Proxy Auto-Discovery Service is disabled and not running. When I checked the services that it was requiring, it was as I stated. So I am only pointing this out to ask the question of:

Did MS disable that service at some point for some security reason and in the wisdom, bring it back accidently when they were building the new version because they pulled a service from an older version of software? (As we all know they do that) and its dependency was on the WinHTTP Web Proxy Auto-Discovery Service when it should not have been? OR ....? I am really Not sure what the question is because all the other 23H2 machines I have checked have that service disabled and no dependency on the WinHTTP....?

Just wondering....

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.