Hello,
�I am currently running Windows 11 25H2 and using a 5G Wi-Fi connection. I am experiencing the same network issues following the KB5077181 update. Only the devices that received this update are affected.
�Here are the specific issues I encountered:
�No Networks Detected: Initially, no networks appeared in the available network list. Upon checking the Wi-Fi properties, I discovered that the security type was forcibly changed from WPA2-Personal to WPA3-Personal.
�Forced WPA3 Conversion: When I manually changed the security type back to WPA2-Personal, my 5G network finally appeared in the list.
�Severe Speed/Signal Limitation: However, the signal strength is extremely limited. I checked the advanced driver settings and found that the 5GHz Channel Width is restricted to only "Auto" and "20MHz", capping the link speed at 144Mbps.
�I have tried all known troubleshooting methods found on Google, including resetting the network settings, but nothing has worked. I even tried forcing the 5GHz channel settings via the Registry Editor based on advice from Gemini, but it was futile.
�Gemini suggests that the KB5077181 update is causing a conflict where Windows incorrectly identifies WPA2 environments as WPA3, leading to connection failures or severe speed degradation, and that the driver is being forced into a 20MHz bandwidth mode.
�Furthermore, uninstalling the KB5077181 update did not resolve the issue. At this point, it seems my only remaining option is a clean installation of Windows.

I have another issue. Network adapter works and all seems ok.
But no networks (routers) are visible in the Wifi connect pane.
Restored an old image of the C disk and then all worked again.
Can this issue be related to the KB5077181 update too?

The SENS issue is a result of the Microsoft policy to force people off of using the older authentication methods which still work in Windows XP, but for which they will not provide an update for Windows XP to enable the new methods.

Specifically, the BlockNTLMv1SSO registry key is changed from "Audit" to "Enforce".

Additionally, since the component OID path changes anytime the component version changes, the registry path cannot be specified normally in a .REG file, it can be simply reloaded after each update with a new componentis pushed by Microsoft on any given Patch Tuesday.

The first version of Windows, which supported the replacement for the old authentication mechanism, the new one being SPNEGO, was Windows 2000.

I suspect that many of the people doing the complaining for the login, have Windows XP clients.

If they are thin clients, this also explains the inability to log into the server to mount the network root volume.

This is very likely an attempt, which Microsoft knows very well that it is making, to put a stake in the heart of Windows XP, once and for all.

Any small business, I cannot afford to upgrade all of their computers at once — an incidentally, not pay for a Windows 11 license on all of those new computers at the same time — is likely buying any new computer to run a VM of Windows XP, so that they can continue to use the same small business stacks that they have been using in all of the other computers they use in their business, without having to replace them all at once.

Which, if you've ever owned or run a small business, you know will simply cause a cash flow business to go bankrupt paying a Microsoft tax.

Such businesses keep old computers, going for forever, or as long as they are "permitted" to keep them going, because every dollar spent on new hardware or new software is a dollar they cannot spend to keep their business afloat.

Microsoft on the other hand views, a non-accelerated amortization of a three year purchase cycle for their products, as lost revenue.

I would say these "unexpected issues" are more than likely a bullying tactic, but that's merely in my opinion, and as I've only been working in this business for 40 years, it's probably my inexperience that would lead me to believe that.

Authentication has always been the Sisyphean boulder that has been used in most integrated computer systems to punish them for not upgrading all of the networked computers and software at the same time.