Quick answer: Reset the Windows network stack (Winsock + TCP/IP), then reinstall or roll back the Wi‑Fi adapter driver and ensure the WLAN AutoConfig service is running.
These steps fix most cases where Windows WiFi shows no networks, won’t connect, or stays stuck on “Connected, no internet” after an update or driver change.
Quick Fix Checklist
Use this order to avoid wasting time (each item takes 1–5 minutes).
- If Wi‑Fi toggle is missing or no networks appear: verify WLAN AutoConfig service + adapter status in Device Manager.
- If networks appear but won’t connect: remove the saved network profile and reconnect with a fresh handshake.
- If it connects but says “No internet”: reset DNS/Winsock and remove VPN/security filtering drivers.
- If it broke after a Windows update: roll back the Wi‑Fi driver (or install the OEM driver).
- If it only fails on one network: disable random hardware addresses for that SSID and force WPA2/WPA3 compatibility.
Fast decision flow:
- No Wi‑Fi icon / Wi‑Fi button missing → Go to Step 1 and Step 2.
- Wi‑Fi icon present but no networks listed → Go to Step 2 and Step 5.
- Networks listed but can’t connect → Go to Step 3 and Step 6.
- Connected but “No internet” → Go to Step 4 and Step 7.
| What you see | Most likely cause | Fix that works |
|---|---|---|
| Wi‑Fi option missing / greyed out | WLAN service stopped, adapter disabled, driver failure | Start WLAN AutoConfig, enable adapter, reinstall driver |
| No networks found | Radio blocked, corrupted driver, wrong region/channel support | Driver reinstall/rollback, disable random MAC, update OEM driver |
| Can’t connect to any network | Bad saved profile, 802.1X/WPA mismatch, security filter driver | Forget network, reset stack, remove VPN/AV network filter |
| Connected, no internet | DNS/Winsock corruption, proxy/VPN, captive portal blocked | Reset Winsock/TCP-IP, clear proxy, renew IP, flush DNS |
| Works on hotspot but not home Wi‑Fi | Router WPA mode/channel width, MAC randomization conflict | Disable random hardware address for SSID, adjust router security |
Causes (realistic, not generic)
- Driver regression after Windows Update: Windows installs a newer driver that breaks roaming, WPA3, or power management.
- WLAN AutoConfig service stopped: Wi‑Fi scanning and profile management won’t run.
- Corrupted network stack: Winsock/LSP entries or TCP/IP settings get damaged by VPNs, security suites, or failed updates.
- VPN or security suite filter drivers: NDIS filter drivers can block DHCP/DNS even when Wi‑Fi shows connected.
- Saved Wi‑Fi profile mismatch: old credentials, changed encryption (WPA2→WPA3), or enterprise settings cause repeated failures.
- Random hardware address (MAC) conflicts: some routers/ISPs bind access to a MAC; randomization breaks authentication.
- Power management cutting the radio: adapter is allowed to sleep aggressively, causing drops or “no networks” after wake.
Step-by-Step Fix
Work top to bottom. Stop when Wi‑Fi works reliably for 5–10 minutes.
1) Confirm the Wi‑Fi adapter is present and enabled (Device Manager)
- Press Win + X → Device Manager → expand Network adapters.
- Find your Wi‑Fi adapter (Intel/Realtek/Qualcomm; often includes “Wireless” or “Wi‑Fi”).
- If it shows a down arrow: right‑click → Enable device.
- If it shows a warning icon: right‑click → Properties → note the error code (then continue to driver steps below).
Actionable check: If the adapter is missing entirely, go to View → Show hidden devices. If still missing, it’s usually a driver or hardware detection issue—jump to Step 6 (driver reinstall) and Still Not Working.
2) Ensure WLAN AutoConfig is running (Wi‑Fi scanning depends on it)
- Press Win + R → type services.msc → Enter.
- Find WLAN AutoConfig.
- Set Startup type to Automatic.
- Click Start (or Restart if it’s already running).
If this service won’t start, note the error message; it often points to a corrupted driver stack or system files (see Step 8).
3) Remove the broken Wi‑Fi profile and reconnect cleanly
- Go to Settings → Network & internet → Wi‑Fi → Manage known networks.
- Select your network → Forget.
- Reconnect from the Wi‑Fi list and re-enter the password.
Why this matters: Windows can keep an incompatible security setting (WPA2/WPA3/802.1X) in the saved profile even after the router changes.
4) Reset Winsock + TCP/IP (fixes “Connected, no internet” and DNS failures)
Open Windows Terminal (Admin) and run:
Commands:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
Then disconnect/reconnect Wi‑Fi. This specifically repairs broken LSP entries and TCP/IP parameters that VPNs/security tools often alter.
5) Disable Random Hardware Addresses (MAC randomization) for the failing SSID (uncommon but real fix)
- Go to Settings → Network & internet → Wi‑Fi.
- Click Manage known networks → select your Wi‑Fi → Properties.
- Set Random hardware addresses to Off.
When this fixes it: the router/ISP uses MAC binding, or the network has access rules tied to your device’s original MAC.
6) Roll back or reinstall the Wi‑Fi driver (best fix after updates)
- Roll back (if available): Device Manager → your Wi‑Fi adapter → Properties → Driver → Roll Back Driver.
- Reinstall cleanly: Device Manager → right‑click adapter → Uninstall device → check Attempt to remove the driver for this device (if shown) → uninstall.
- Then install the latest OEM driver from your laptop/motherboard vendor (preferred over Windows Update), or let Windows detect it after removal.
Specific tip: If you’re on Intel Wi‑Fi, the OEM package often includes fixes for WPA3/roaming that the generic Microsoft catalog driver doesn’t.
7) Remove VPN / security suite network filters that break DHCP/DNS
If Wi‑Fi connects but traffic doesn’t pass, a filter driver is a common culprit.
- Go to Control Panel → Network and Internet → Network Connections.
- Right‑click your Wi‑Fi adapter → Properties.
- Uncheck non-Microsoft items that act as filters (examples: VPN client filter, web protection, packet inspection). Keep Internet Protocol Version 4 (TCP/IPv4) and IPv6 checked.
- Also check Settings → Network & internet → Proxy and set Use a proxy server to Off unless you intentionally use one.
If your VPN is required for work, reinstall it after Wi‑Fi is stable and ensure it’s updated to a version compatible with your Windows build.
8) Repair system networking components (advanced)
If WLAN AutoConfig fails, drivers reinstall but Wi‑Fi still won’t scan/connect, repair system files:
Open Windows Terminal (Admin) and run:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
After completion, re-check Wi‑Fi scanning and connection behavior.
9) Fix adapter power management (prevents drops after sleep)
- Device Manager → Wi‑Fi adapter → Properties → Power Management.
- Uncheck Allow the computer to turn off this device to save power.
- Optional: Control Panel → Power Options → your plan → Change advanced power settings → Wireless Adapter Settings → set to Maximum Performance (on battery and plugged in if needed).
Still Not Working
If the steps above didn’t restore Wi‑Fi, use these targeted checks to isolate the failure quickly.
A) Run a focused wireless report (find driver/auth failures)
- Open Command Prompt (Admin).
- Run: netsh wlan show wlanreport
- Open the generated report (it will show the file path) and look for:
- Reason codes (authentication failures, wrong key, WPA mismatch)
- Driver resets or frequent disconnect reasons
This is one of the fastest ways to confirm whether the issue is credentials/security vs driver stability.
B) Check IP/DNS state to confirm whether it’s Wi‑Fi or routing
- Open Terminal and run: ipconfig /all
- Look for:
- IPv4 address (if you see 169.254.x.x, DHCP failed)
- Default Gateway (missing gateway usually means DHCP/router issue or filter driver)
- DNS Servers (blank or unusual entries can indicate VPN/proxy interference)
If DHCP fails repeatedly, try setting IPv4 to automatic (not static) in adapter properties, then re-run ipconfig /renew.
C) Do a full Network Reset (last resort, but effective)
- Settings → Network & internet → Advanced network settings → Network reset.
- This removes and reinstalls network adapters and clears custom settings (VPN adapters may need reinstall).
D) If Wi‑Fi works on hotspot but not your router
- Disable Random hardware addresses for that SSID (Step 5).
- On the router, temporarily set security to WPA2-Personal (AES) to test compatibility (some Windows drivers choke on mixed WPA2/WPA3 transitions).
- Avoid DFS-only channels on 5GHz if your adapter/region doesn’t support them; test a common channel (36–48) and 20/40MHz width.
E) Suspect hardware if the adapter disappears intermittently
- If the Wi‑Fi adapter vanishes from Device Manager after sleep or under load, it can be a failing card or loose internal connection (common in laptops).
- Confirm by checking whether the adapter is detected in BIOS/UEFI (if your system exposes it) and whether Linux live USB detects it.
If you need a fast next step: capture your Wi‑Fi adapter model (Device Manager), Windows version (Settings → System → About), and the exact symptom (no networks vs can’t connect vs connected/no internet). That combination determines whether driver rollback, filter removal, or DHCP/DNS repair is the correct fix.