Consolidated list of all known fixes and workarounds for the current Wi‑Fi auto‑connect regression affecting Intel Wi‑Fi 6/6E adapters in build 26220.x.
1. Update the Wi‑Fi driver
Install the latest Intel Wi‑Fi driver (23.30+ or 24.x series).
Windows Update may install an older inbox driver that triggers the issue.
2. Rebuild the Wi‑Fi profile
- Settings → Network & Internet → Wi‑Fi → Manage known networks
- Select your network → Forget
- Reconnect and tick Connect automatically
- Set Random hardware addresses → Off
This fixes the profile‑mismatch bug in 26220.
3. Disable Fast Startup
Control Panel → Power Options → Choose what the power buttons do →
Untick
Turn on Fast Startup → Save → Reboot.
This prevents a race condition where the adapter initialises too late.
4. Adjust Intel AX210/AX211 advanced settings
Device Manager → Network adapters → Intel Wi‑Fi 6E AX210 → Properties →
Advanced
Set the following (names vary by driver version):
- MIMO Power Save Mode → No SMPS
- U‑APSD → Disabled
- Throughput Booster → Enabled
These force earlier firmware initialisation during boot.
5. Registry workaround: disable the new WLAN secure startup
This addresses the early‑boot auto‑connect regression in 26220.x.
Registry Editor →
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wlansvc\Parameters<br>
Create DWORD (32‑bit):
DisableWlanSecureStartup<br>
Set value:
1<br>
Reboot.
6. Reset the network stack
Run in
Administrator PowerShell:
netsh winsock reset<br>netsh int ip reset<br>ipconfig /flushdns<br>
Reboot and reconnect.
7. Confirm MAC randomisation is disabled
Settings → Network & Internet → Wi‑Fi → Manage known networks → your network →
Random hardware addresses → Off
This prevents profile mismatch on reboot.
8. Known limitation: Power Management tab missing
On AX210/AX211 with Modern Standby (S0), the
Power Management tab is intentionally hidden in current Intel drivers and cannot be restored.
This is expected behaviour and not a fault.
9. Known issue: WLAN AutoConfig cannot be set to Delayed Start
Attempting to set wlansvc to delayed start returns
Error 87.
This is a known limitation in 26220.x and cannot be changed.
10. If all else fails
This is a confirmed regression in the 26220 networking stack.
Options:
- Wait for the next Canary/Dev build (fix already in validation)
- Roll back to build 26120 (last stable networking stack)
- Use a startup script as a temporary workaround:
netsh wlan connect name="YOUR_SSID"<br>
----------------
For the record, I have tried all of the above and many others suggested by Microsoft forum, ChatGPT and Copliot, nothing worked until I did the last one, using ye olde time batch script
