Networking: No Wi-Fi networks found — the Wi-Fi adapter is missing, disabled or its driver failed
The operating system doesn't see a working wireless adapter, so no networks can be listed.
No Wi-Fi networks foundWi-Fi option missingNo wireless interfaces foundWi-Fi: Soft blocked: yesWireless capabilities Wi-Fi adapter not found Meaning
Check airplane mode and the hardware Wi-Fi key first, then Device Manager (Windows) or rfkill list / lspci -k (Linux). A missing driver, a disabled radio, a BIOS setting or a failed USB dongle are the usual causes; reinstall the vendor driver and power-cycle the machine.
Common causes
- Airplane mode or hardware radio switch on
- Wi-Fi driver missing, corrupt or replaced by an update
- Adapter disabled in Device Manager or BIOS
- Blocked by rfkill (soft/hard block)
- USB Wi-Fi dongle unplugged or underpowered
⚡ Quick fix
- Turn off airplane mode and check
rfkill list - Reinstall or roll back the Wi-Fi driver
- Enable the adapter in Device Manager / BIOS and reboot
Detailed fix by platform
Linux
rfkill list all && sudo rfkill unblock wifi && lspci -k | grep -A3 -i network
How to diagnose
- Airplane mode — Off?
- rfkill — Unblocked?
- Driver — Loaded?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 4-way handshake timeout / Incorrect password Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- captive portal Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026