Can't connect to this Wi-Fi after updating windows 11 24H2 update

Thank you very much! This was it for me. My organization had this value set to 4 (disabled) through Group Policy to prevent man in the middle attacks on all workstations so enabling it again worked (rollbacks to 23H2 also worked).

I'll give a summary of my experience in case it helps anyone. A number of my machines had no working wifi after updating to 24H2, however Bluetooth would work fine (and it's the same card running wifi and bluetooth). In Device manager it showed that it was working fine. In Control Panel it showed Disabled. If you enabled it, it would just go back to disabled with nothing much showing up in event viewer. In event log for the wifi adapter (Device Manager -> Network Adapter Properties -> Events) it showed that on the 24h2 update the device settings we're migrated from previous OS installation. After trying to uninstall and reinstall the device it would say the device settings we're not migrated from previous OS installation due to partial or ambiguous device match. Then i found that a USB wifi adapter also wouldn't work, and direct ethernet would connect for a second and then not work either (however it would get a dhcp address, but couldn't even ping the gateway). A USB C to ethernet connection (ie, through a dock) was the only thing that would work, so then I knew it was a Windows issue, not wifi or hardware. Then i found this post and it was the fix for me.

My best guess is that Windows 24H2 is now using auto proxy service to make a test connection somewhere to see it's connectivity (similar to how wifi tries to connect to that msftredirect site before completing the connection). When it can't use that auto proxy service, it just disables. Would love to know the real answer, but that's my guess. Our org has had this setting disabled for a couple of years and working fine through previous updates until 24H2.

Arvind - I just read that MS have now decided to make 24H2 mandatory. It will be installed whether I want it or not. At the moment I have it blocked. When it happens my PC's will be bricked. Are they insane? They must know the problems this will cause.

Last time I had my wife's PC to search the internet for solutions, when the mandatory rollout happens both our PC's will be cut off. Right now I'm going through this thread and others copying comments like yours into a save file. I just retired after 30 years working in software development, I will be able to follow all the driver and registry actions you listed and hopefully find one that works. We both know that a lot of users won't be able to do that. I don't know what percentage of users will have these problems but from talking about it for a day I've found quite a few. Apart from no internet connection I've had the one where the screen freezes and I had to ctrl/alt/delete to reboot. My PC is a 3 month old Dell.

We both also know that MS are very hard to reach for help. Any suggestions.

Derrick - I understand the patience thing. But this happened to me on 1/16/25, it's been happening since Oct. Then an hour ago I read that MS is about to make 24H2 mandatory. I'll try the Feedback Hub thing you mentioned.

OK - I put a comment on the MS Feedback Hub about this problem. Here is the link.

https://aka.ms/AAhdrxh

Microsoft representatives keep responding with macro replies, suggesting the use of the Feedback Hub like parrots. I find this approach utterly irresponsible. With so many people posting about the same issue in the community, how much clearer can feedback possibly get?

It's been quite some time since 24H2 was released, yet this issue remains unresolved. Microsoft's response to this problem feels akin to that of a small startup, not a leading tech giant. I urge you to move beyond these generic replies and provide a prompt and effective solution.