Quick answer: Roll back (or clean‑reinstall) your Wi‑Fi driver, then reset Winsock/TCP/IP and reboot—Windows updates commonly swap drivers and break network bindings.
If it still fails, remove VPN/AV filter drivers, restart WLAN AutoConfig, and force a safer Wi‑Fi mode (disable 802.11ax/WPA3) to bypass update compatibility issues.
Quick Fix Checklist
- Confirm Wi‑Fi is actually enabled: Settings > Network & internet > Advanced network settings > More network adapter options > right‑click Wi‑Fi > Enable.
- Airplane mode / hardware switch: toggle Airplane mode off; on laptops check Fn hotkey or physical wireless switch.
- Roll back the Wi‑Fi driver: Device Manager > Network adapters > Wi‑Fi > Properties > Driver > Roll Back Driver.
- Reset the network stack (admin): run the commands in Step 2 and reboot once.
- Disable Wi‑Fi power saving: Device Manager > Wi‑Fi adapter > Power Management > uncheck “Allow the computer to turn off this device”.
- Temporarily remove VPN/AV network filters: uninstall VPN clients / third‑party firewalls (they add NDIS filter drivers that often break after updates).
- Clean reinstall the adapter driver: uninstall device + delete driver, then install the latest OEM driver from your PC maker (preferred over Windows Update).
- Fast sanity check: reboot router/AP and try a phone hotspot—this quickly separates “PC issue” vs “router compatibility issue”.
Causes (realistic, not generic)
- Driver replaced by Windows Update: a Microsoft driver may lack OEM fixes (Intel/Realtek/Qualcomm) or regress roaming/authentication.
- Corrupted network bindings: Winsock/LSP entries or TCP/IP stack becomes inconsistent after cumulative updates.
- VPN/security filter driver conflict: NDIS filter drivers can block DHCP, DNS, or captive portal detection after an update.
- Power management regression: update changes power plan defaults; the adapter sleeps and fails to wake.
- WLAN AutoConfig/service dependency issue: service startup type changes or dependencies fail, so scanning/connecting breaks.
- 802.11ax/WPA3 negotiation bug: new OS build/driver negotiates a mode your router/AP handles poorly (random drops, can’t see SSID, “Connected, no internet”).
- DNS client cache / NRPT / proxy leftovers: updates can expose stale DNS cache, a forced proxy, or name resolution policy rules from corporate tools.
| What you see | Most likely cause | Fix that works |
|---|---|---|
| Wi‑Fi toggle missing / no Wi‑Fi adapter listed | Driver failed/removed, device disabled, or BIOS/hardware radio off | Enable adapter; check Airplane mode/hotkey/BIOS; clean‑reinstall OEM driver |
| Connected but “No internet” | Broken TCP/IP, DNS cache/proxy, or VPN/AV filter driver | Reset stack + flush DNS; remove VPN/AV filters; clear proxy/WinHTTP |
| Can’t see any networks | WLAN AutoConfig stopped, radio disabled, or driver/region settings issue | Start WLAN AutoConfig; reinstall driver; toggle airplane mode; reset network |
| Disconnects every few minutes | Power saving, 802.11ax/WPA3 compatibility, roaming aggressiveness bug | Disable power saving; disable 802.11ax/WPA3; update OEM driver; set preferred band |
Step-by-Step Fix
0) Identify the exact failure (30 seconds)
- Adapter missing? Go to Step 4 (clean reinstall) and Step 10 (hardware/BIOS checks).
- Adapter present but no networks? Go to Step 6 (services) and Step 7 (safer Wi‑Fi mode).
- Connected but no internet? Go to Step 2 (stack reset) and Step 9 (DNS/proxy cleanup).
- Only your router fails? Go to Step 7 (802.11ax/WPA3) and Step 11 (router-side quick checks).
1) Roll back the Wi‑Fi driver (fastest post-update fix)
- Press Win+X > Device Manager.
- Expand Network adapters > double‑click your Wi‑Fi adapter.
- Driver tab > Roll Back Driver > choose “Previous version worked better”.
- If Roll Back is greyed out, do Step 4 (clean reinstall) and install the OEM driver.
Tip: If Wi‑Fi broke immediately after an “Intel/Realtek/Qualcomm – Net” driver update in Windows Update history, rolling back is especially likely to fix the windows wifi not working after update after update problem.
2) Reset Winsock/TCP/IP and renew DHCP (admin commands)
Open Windows Terminal (Admin) and run:
netsh winsock resetnetsh int ip resetipconfig /flushdnsipconfig /releaseipconfig /renew
Reboot once after the Winsock reset (required).
3) Disable Wi‑Fi power saving (prevents “connected then dead”)
- Device Manager > Network adapters > Wi‑Fi adapter > Properties > Power Management.
- Uncheck Allow the computer to turn off this device to save power.
- Control Panel > Power Options > Change plan settings > Advanced > Wireless Adapter Settings > set Maximum Performance (On battery and Plugged in).
4) Clean reinstall the Wi‑Fi driver (fixes missing adapter / Code 10 / Code 43)
- Device Manager > Network adapters > right‑click your Wi‑Fi adapter > Uninstall device.
- Check Attempt to remove the driver for this device / “Delete the driver software” if offered.
- Reboot.
- Install the latest OEM Wi‑Fi driver from your laptop/motherboard support page (preferred over Windows Update drivers).
If you can’t download on the affected PC, use another device to download the driver and copy it via USB.
5) Remove VPN/AV network filter drivers (common after updates)
When Wi‑Fi shows “Connected” but traffic fails, filter drivers are a frequent cause.
- Settings > Apps > Installed apps > uninstall VPN clients and third‑party firewalls temporarily.
- Reboot.
- Run the network reset commands again (Step 2).
If you must keep the VPN, install its newest version that explicitly supports your current Windows build.
6) Repair WLAN AutoConfig and required services
- Press Win+R > type
services.msc. - Set WLAN AutoConfig to Automatic > click Start.
- Also verify these are running: DHCP Client, Network Connections, Network List Service, Network Location Awareness.
7) Force a safer Wi‑Fi mode (targets 802.11ax/WPA3 regressions)
If the update introduced random disconnects, “Can’t connect to this network”, or you can’t see/keep your SSID:
- Device Manager > Wi‑Fi adapter > Properties > Advanced.
- Set 802.11ax to Disabled (or set Wireless Mode to 802.11ac/802.11n).
- If available, set Preferred Band to 5GHz (or 2.4GHz for range).
- If your router supports WPA3 and you recently enabled it, try WPA2/WPA3 mixed mode or WPA2 temporarily.
8) Reset Windows network components (stronger than Winsock reset)
This reinstalls network adapters and clears many broken bindings.
- Settings > Network & internet > Advanced network settings > Network reset > Reset now.
- Reboot when prompted.
- Rejoin your Wi‑Fi network (you’ll need the password again).
9) Advanced: fix DNS/proxy leftovers (non-obvious but common)
Use this when pages won’t load but Wi‑Fi says connected, especially on PCs that used corporate VPN/proxy tools.
- Open Windows Terminal (Admin) and run:
netsh winhttp reset proxyipconfig /flushdnsipconfig /registerdns
- Then check: Settings > Network & internet > Proxy > turn off “Use a proxy server” unless you intentionally use one.
- If you set custom DNS earlier, temporarily switch to automatic DNS or a known-good resolver.
10) Repair corrupted system components (DISM/SFC)
Run in Windows Terminal (Admin):
DISM /Online /Cleanup-Image /RestoreHealthsfc /scannow
If DISM reports source errors, use a matching Windows ISO (same build) as a repair source and rerun DISM with /Source.
11) Quick router/AP checks (when only one network fails)
- Forget and re-add the network: Settings > Network & internet > Wi‑Fi > Manage known networks > Forget.
- Reboot router/AP and update its firmware if available.
- Temporarily split SSIDs (separate 2.4GHz and 5GHz) to avoid band-steering issues.
- Try a different channel (especially on 2.4GHz) if you’re in a crowded area.
Still Not Working
- Uninstall the specific update that triggered it: Settings > Windows Update > Update history > Uninstall updates. Remove the most recent cumulative update or “Net” driver update if Wi‑Fi broke immediately after.
- Boot into Safe Mode with Networking: if Wi‑Fi works there, a startup app/driver (VPN, security suite, traffic shaper) is likely the conflict.
- Check Event Viewer for driver resets: Event Viewer > Windows Logs > System. Look for WLAN/Netwtw/rtwlane/NDIS errors around disconnect times; this helps confirm driver regression vs signal issues.
- Generate a WLAN report (actionable evidence): Terminal (Admin) >
netsh wlan show wlanreport. Open the report and look for authentication failures, DHCP timeouts, or driver resets. - Verify the adapter isn’t disabled at firmware level: some laptops have BIOS/UEFI wireless toggles that can reset after firmware/driver changes.
- Test with a USB Wi‑Fi adapter: if USB Wi‑Fi works reliably, your internal card/antenna connection may be failing (common on older laptops) or the internal driver is the issue.
- System Restore (fast rollback): Control Panel > Recovery > Open System Restore > choose a restore point before the update.
- Last resort escalation: perform an in-place repair install of Windows (keeps files/apps) or Reset this PC (keep files). If it’s a managed work device, contact IT—policies (proxy/NRPT/VPN) can reapply after each reboot.
To get a precise fix, note your Wi‑Fi adapter model (Device Manager name) and your Windows version/build (Settings > System > About). With those two details, you can match a known-good OEM driver version that avoids the update regression.
If the Problem Started After an Update
If the problem started right after an update, the timing strongly suggests a compatibility or local data issue.
Why this happens
Updates can change permissions, invalidate saved sessions, or leave behind temporary cached data that no longer matches the latest app or system version.
How to fix it
- Restart the device first to clear temporary glitches triggered by the update.
- Check whether a follow-up patch is already available for the app or system.
- Sign out and sign back in if the app still opens but a specific function fails.
- Clear cache or reinstall the app if the issue appears tied to corrupted local data.
- Look for reports from other users to confirm whether the update introduced a wider bug.
Important notes
- If many users report the same issue after the same update, a vendor-side patch may be required.
- Do not reset the whole device too early if simpler update-related fixes have not been tested yet.
How to Check for a Temporary Outage
Before changing device settings, confirm that the problem is not caused by a temporary outage.
Why this happens
Service interruptions can make normal accounts, apps, and networks appear broken even when nothing is wrong locally.
How to fix it
- Try the web version to see whether the same action fails outside the app.
- Check official status pages or recent outage discussions if available.
- Avoid repeated retries if the platform appears unstable.
- Wait a few minutes and test again from the same trusted network.
Important notes
- If both the app and browser fail in the same way, the issue is much more likely to be service-side.
- Changing passwords or reinstalling apps will not help during a real outage.
Frequently Asked Questions
Windows Wi‑Fi not working after update after update problem — what’s the fastest fix?
First roll back the Wi‑Fi driver in Device Manager (Driver > Roll Back). Then run netsh winsock reset + netsh int ip reset, reboot, and reconnect to Wi‑Fi—this fixes most post-update driver swaps and broken bindings.
Why is my Wi‑Fi toggle missing or the adapter disappeared after a Windows update?
Usually the driver failed to load, was replaced, or the radio was disabled. In Device Manager, enable the adapter if present; if it’s missing or erroring, uninstall it (delete driver if offered), reboot, and install the latest OEM Wi‑Fi driver from your PC manufacturer.
Wi‑Fi says “Connected, no internet” after the update—what should I check next?
Reset the network stack (Winsock/TCP/IP), flush DNS, and renew DHCP. If you use a VPN, third-party firewall, or security suite, uninstall it temporarily because its NDIS filter driver can block DHCP/DNS after updates; also reset WinHTTP proxy and disable any forced proxy in Settings.
How do I fix constant Wi‑Fi disconnects after updating Windows 11/10?
Disable adapter power saving and set Wireless Adapter Settings to Maximum Performance. If it still drops, disable 802.11ax (Wi‑Fi 6) and/or switch WPA3 to WPA2/WPA3 mixed mode to work around driver/router compatibility issues introduced by the update.
Roll Back Driver is greyed out—what do I do?
Do a clean reinstall: uninstall the Wi‑Fi adapter in Device Manager and check “Delete the driver software” if available, reboot, then install the newest OEM driver from your laptop/motherboard support page (not Windows Update).
What logs or reports help prove whether it’s a driver issue vs router issue?
Run “netsh wlan show wlanreport” and review the timeline for authentication failures, DHCP timeouts, or driver resets. Also check Event Viewer > System for WLAN/NDIS/adapter driver errors at the exact disconnect time; if a phone hotspot works but your router doesn’t, it strongly points to a router mode (802.11ax/WPA3/band steering) compatibility issue.