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

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.

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.

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.

Hi Welcome to Microsoft community. I completely understand how frustrating it can be to face connectivity issues, especially after an update like the Windows 11 24H2 version. It’s great that you’ve already tried various troubleshooting steps to resolve the issue. Since you've done quite a bit of troubleshooting and the problem still persists, I recommend providing feedback directly to Microsoft. You can do this through the Feedback Hub app on your PC. Microsoft attaches great importance to user experience, you can submit your ideas and suggestions through the Feedback Hub, and the development team will regularly review submissions for ideas or fixes. Please share the feedback link here after submitting as it will allow others on the forum to vote for your submission, including me. More votes will lead to more visibility and higher priority to the development team. In the meantime, I encourage you to be patient as they work on fixes and updates. If you have any other questions or need further assistance, feel free to reach out!Best regardsDerrick Qian | Microsoft Community Support Specialist

what is the point if no one will action it? I posted one 2-3 months ago with no update from MS yet.

P.S. I have tried all the proposed solutions here (except removing DHCP 121) with no resolution...

When using version 23H2, I did not experience the intermittent Wi-Fi disconnection issues that I encountered with version 24H2. However, I recently purchased a new Galaxy Book5 Pro, which came pre-installed with 24H2. Unfortunately, I faced several software-related issues with this version, so I ultimately reverted back to 24H2.

To share some new information, there was an additional update for 24H2 yesterday. I'm not sure if this update is related to Wi-Fi connectivity, but since applying it, the Wi-Fi disconnection issue seems to have disappeared. That said, I've only been using it for a day, so the reliability of this feedback is not very high yet.