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

I was waiting patiently for MS to fix this problem but I was getting older by the day.

Today I printed off all the suggestions in this thread and reinstalled 24H2. Sure enough the WiFi didn't work. So I started working my way down the list of suggestions provided by Arvind Kumar. The very first item did the job.

* Uninstall WiFi Adapter - restart computer and let Win install the default driver.

Got my WiFi back but I'm not sure if this leaves me with the correct driver installed though. The last step says:

• Restart your PC to allow Windows to reinstall the default driver, or manually download the latest driver from your Wi-Fi adapter or laptop manufacturer’s website.

So now I have the "default driver" installed. Don't know if that's different from the one that wasn't working. Or it was the same driver but it had been messed up by 24H2 and just needed replacing. Or something.

Now I'm confident I can get my PC working so I might check out drivers. Maybe go to the manufacturer site and take a look, see if I've got the latest driver.

I must say this is a bit dodgy. I worked in software development for years and this wasn't hard to do. I'm pretty sure my wife wouldn't be able to do it. And she wouldn't have known that you can roll back upgrades, or even realised the problem had been caused by an upgrade. And without internet connection she would have had no way of finding out. I figured it out by using her computer to search for info about the problem but lots of folks only have one computer.

Sorry this post got long.

Anyway - thanks for your help Arvind

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.

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...

I tried all the fixes in this post but none worked for me.

To be specific, my laptop would connect and stay connected to the WiFi, but would just drop out complaining about DNS repeatedly every 30 seconds or so.

I came across another post that mentioned a different registry edit that worked for me.

In RegEdit navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wcmsvc

Edit entry "DependOnService"

Remove "WinHTTPAutoProxySvc" from list leaving "RpcSc" and "NSI"

Restart computer and my internet worked again.

Thanks it works mine laptop but another one has still issue.