Opened the Wi-Fi list and it’s completely empty — just a spinning icon or nothing at all. No networks showing. This is different from “can’t connect to my network” — the adapter can’t find any networks at all. We go deeper on the whole subject in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Three things to rule out before touching any settings:
Check whether the physical Wi-Fi switch or Fn+key combo is off. Some laptops have a dedicated airplane mode key (F12, or an antenna icon somewhere in the function row). One accidental press disables all wireless. Check the notification center too — the airplane mode tile might be on.
Check if the problem is just the list not refreshing. Click the Wi-Fi icon → click the refresh/cycle arrows if visible, or toggle Wi-Fi off and back on in Settings → Network and internet → Wi-Fi. Sometimes the network list just goes stale.
Confirm with another device — phone on the same Wi-Fi — that the router is actually broadcasting. If the router is malfunctioning and not sending out beacons, no device will see the network.
The WLAN AutoConfig service — the fix most guides miss
If the Wi-Fi adapter is present in Device Manager but shows no available networks, this service being stopped is the most common single cause. Windows WLAN AutoConfig manages network discovery, and when it’s not running, the adapter connects to the OS but can’t perform any scanning.
Win + R → services.msc → find “WLAN AutoConfig” → if it’s Stopped, right-click → Start. Also check that Startup type is “Automatic.” After starting it, the Wi-Fi network list typically populates within 30 seconds.
If it’s already running: try restarting it anyway. Right-click → Restart. A service that’s running but stuck can behave as if it’s stopped.
Driver issue or corrupted driver state
This usually presents as the Wi-Fi adapter appearing in Device Manager with a yellow warning triangle, or the adapter being missing entirely from Device Manager (only visible when “Show hidden devices” is enabled).
The proper fix: download the Wi-Fi driver from the laptop manufacturer’s support page — the specific model page, not just a generic driver. Generic Intel/Qualcomm/Realtek drivers sometimes work, but manufacturer-validated drivers almost always work better for network discovery.
For a quick test before the full driver reinstall: Device Manager → Network Adapters → right-click the Wi-Fi adapter → Disable device → wait 10 seconds → Enable device. This power-cycles the driver state without reinstalling anything. Occasionally that’s enough.
After a Windows update, specifically
Windows updates sometimes swap out the working manufacturer Wi-Fi driver for a generic version. Networks still show up — usually — but occasionally the generic driver has a scanning bug and the list goes empty.
Check the driver date in Device Manager → right-click Wi-Fi adapter → Properties → Driver tab → Driver Date. If it changed recently to match when the update installed, that’s your culprit. Roll Back Driver if available. If not, manually download the previous version from the manufacturer’s driver archive.
The network stack reset
Corrupted network configuration can prevent scanning from working even when everything else looks fine. This sequence clears it:
netsh winsock reset
netsh int ip reset
netsh wlan delete profile name=* i=*Wait — that last command deletes all saved Wi-Fi profiles. Have passwords ready before running it. But it’s sometimes necessary when a corrupted profile is preventing the adapter from scanning. After restarting, the adapter initialises clean and networks reappear.
If you don’t want to delete saved profiles, just run the first two commands and restart — they handle the network stack without touching profiles.
Adapter not appearing in Device Manager at all
This is a different problem. If the Wi-Fi adapter isn’t in Device Manager even with hidden devices shown, it’s either disabled at the BIOS level or the hardware isn’t being detected.
Check BIOS first: restart → enter BIOS → look for Wireless or Network settings → confirm Wi-Fi isn’t disabled there. Some corporate laptops come configured with Wi-Fi disabled in firmware, and a BIOS update or factory reset can trigger this.
If the adapter was present before and is now missing: try a system restore to before the adapter disappeared. Settings → System → Recovery → Open System Restore → pick a restore point from before the issue. This reverses driver and configuration changes without affecting personal files.
Regional frequency band restrictions
A less-obvious cause: the Wi-Fi adapter’s country/region setting being incorrect. Windows uses this to determine which frequency channels to scan. If set to the wrong country, the adapter might not scan the channels your router uses, making it appear as though no networks exist.
Device Manager → right-click Wi-Fi adapter → Properties → Advanced tab → look for “Country Region” or “Regulatory Domain” → confirm it’s set to your actual country. This shouldn’t change on its own, but it sometimes does after major Windows updates or clean installs.
The Wi-Fi not working guide covers connection failures after networks appear — if you solve the empty list but then can’t connect, that guide picks up from there. And if the adapter disappeared from Device Manager entirely, the diagnostics in the device detection guide apply since the underlying hardware detection issue is similar. Microsoft’s wireless adapter troubleshooting covers the advanced event log paths in WLAN-AutoConfig that capture exactly why scans are failing at the driver level.
Hidden SSIDs and what they look like
If all nearby networks have their SSIDs hidden (not broadcast), they won’t appear in the automatic scan list — that’s by design. You’d need to manually add each network: click “Manage known networks” in the Wi-Fi settings → Add network → enter the SSID name manually. This is unusual in home environments but common in some corporate setups where IT hides the network name for (debatable) security reasons.
Bluetooth and Wi-Fi interference
Both use 2.4 GHz spectrum. Heavy Bluetooth usage — wireless headphones actively streaming, Bluetooth mouse and keyboard both connected — can create enough RF interference to degrade Wi-Fi 2.4 GHz scanning to the point where no networks are detected or the list shows intermittently.
Test: turn Bluetooth off entirely (Settings → Bluetooth and devices → toggle Bluetooth off). Try scanning for networks. If networks appear, the interference is real. Either switch to a 5 GHz Wi-Fi connection (not affected by Bluetooth interference) or use the 2.4 GHz connection with fewer Bluetooth devices active.
Checking the adapter’s transmit power
Wi-Fi adapters have a transmit power setting in their Advanced tab that affects how far they can both broadcast and detect. If someone reduced this setting (for battery saving or mistakenly), the adapter’s effective range drops significantly — nearby networks may still appear but distant ones won’t, or in severe cases even nearby networks become inconsistent.
Device Manager → right-click Wi-Fi adapter → Properties → Advanced → “Transmit Power” or “Power Output” → set to Highest or 100%. For laptops where battery life matters more than range, “Medium” is usually fine. “Lowest” or “1 mW” will cause exactly the symptoms described — intermittent or empty network list despite the adapter functioning normally otherwise.
Checking what the adapter sees with netsh
Before blaming Windows UI, check if the adapter itself is actually scanning:
netsh wlan show networks mode=bssidRun this in Command Prompt. If it returns a list of SSIDs and BSSIDs, the adapter is finding networks — the Windows GUI just isn’t displaying them correctly. This is a UI rendering issue with the network flyout, not an actual scan failure. Restarting Explorer (Task Manager → Windows Explorer → Restart) usually fixes the display.
If netsh wlan show networks returns “There are no wireless networks visible in range” — the adapter genuinely isn’t finding anything. That points at the adapter itself, its driver, or the WLAN AutoConfig service.
USB Wi-Fi adapters specifically
USB wireless adapters (dongles) have different failure modes than built-in adapters. They depend on the USB port for both power and data, and can fail if:
- The USB port is in power-saving mode and cut power to the dongle
- The dongle was pulled out without ejecting, corrupting driver state
- The USB 3.0 port is causing RF interference with the 2.4 GHz band (a well-documented issue)
For the USB interference issue specifically: if using a USB 3.0 dongle and only 2.4 GHz networks disappear while 5 GHz networks remain visible, try moving the dongle to a USB 2.0 port (usually black interior instead of blue) or use a short USB extension cable to move the dongle away from the USB port itself. USB 3.0 interference at 2.4 GHz is a hardware physics issue — the solution is physical distance between the dongle antenna and the USB 3.0 port.
Running the network troubleshooter
Windows has a built-in troubleshooter that catches common causes automatically. Settings → System → Troubleshoot → Other troubleshooters → Internet Connections → Run. Also run “Network Adapter” from the same list. These two together handle the WLAN AutoConfig service restart, basic driver checks, and some adapter configuration resets automatically.
Worth running early — it takes two minutes and catches about 30% of the causes described above without manual intervention.
Confirming the fix worked
After any fix: click the Wi-Fi icon → the network list should show your router and several other nearby networks (neighbours’ routers, etc.) within 30–60 seconds of the adapter reinitialising. Seeing at least 3–5 networks confirms the adapter is scanning correctly. Seeing only your own network could indicate reduced range (transmit power) or interference (USB 3.0). Seeing nothing still means the adapter or driver still has an issue.
Safe Mode Wi-Fi as a test
Boot into Safe Mode with Networking (hold Shift → Restart → Troubleshoot → Advanced options → Startup Settings → press 5). If Wi-Fi networks appear in Safe Mode, a startup application or non-essential service is interfering with the WLAN service in normal mode. Common culprits: third-party network management software, VPN clients that modify the network stack, and certain antivirus products with aggressive network filtering.
When it works for 5 minutes then goes empty again
Intermittent empty list — networks appear after a restart but disappear after a few minutes — is usually one of these three things:
Power management cutting the adapter. Windows decides the adapter is idle and cuts power, at which point it loses its scan results. Fix: Device Manager → Wi-Fi adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also set the Wi-Fi Power Saving Mode to “Maximum Performance” in the advanced power settings.
The WLAN AutoConfig service crashing. It starts, fails, and stops — taking network scanning with it. Event Viewer → Windows Logs → System → look for “WLAN-AutoConfig” errors around when the list goes empty. If you see frequent errors: reinstalling the Wi-Fi driver usually fixes it, since the crash is typically triggered by a corrupted driver component.
Interference. If you’re near a microwave, baby monitor, or dense 2.4 GHz environment, signal quality can drop so much that the adapter shows no available networks even though the networks are technically there. Moving closer to the router temporarily confirms whether interference is the issue.
Laptops that only show empty list on battery
Some laptops aggressively reduce Wi-Fi adapter power when running on battery to extend runtime. In extreme cases, power savings are so aggressive that network scanning produces no results. The fix: plug in the laptop and confirm networks appear. Then: Settings → System → Power → set the “Power mode” to “Balanced” rather than “Best power efficiency” while on battery. Also adjust the wireless power saving in Control Panel → Power Options → change plan settings → advanced settings → Wireless Adapter Settings → change Power Saving Mode to Maximum Performance even on battery.
This trades some battery runtime for reliable wireless operation. For a laptop that’s primarily used plugged in, this is an acceptable trade. For truly portable use, Balanced mode usually finds a workable middle ground.
Final note on diagnosis order: the WLAN AutoConfig service check and the netsh command to verify actual scan results are the two fastest ways to determine whether the problem is a service/software issue or a hardware/driver issue. Do those first. Everything else in this guide branches from that initial determination — whether the adapter is scanning but results aren’t showing, vs whether the adapter isn’t scanning at all, vs whether the adapter isn’t even loading. Knowing which branch you’re on saves working through fixes that won’t apply to your specific situation.
One last check for completeness: if you’re in an area with very few Wi-Fi networks nearby — rural location, isolated building — the empty list might just be accurate. The adapter might be working perfectly and there genuinely are no detectable networks in range. Using your phone as a hotspot temporarily tests both whether the adapter can connect (not just scan) and whether anything was within range to begin with. Our guide on How to Fix WiFi 5GHz Not Showing Windows 11 covers an adjacent issue.
