ProblemAn empty Wi-Fi list is different from a connection without Internet. Before changing the router, distinguish whether Windows still offers Wi-Fi, whether it sees other networks and whether another device sees the expected network from the same location. This separates adapter detection, radio and band compatibility; DNS does not determine whether a network name appears.

Windows can't find Wi-Fi networks

The Wi-Fi control exists, but Windows shows no available networks. Check the radio and band compatibility; use the missing Wi-Fi option guide if the control or adapter is absent.

Try this first

1 quick checks · ~3 min

  1. Compare the list and radio without changing the networkSeparate a missing control, one missing network and a completely empty list.

Find your situation

See all the clues. Choose the one that matches what you observe.

Diagnostic signals

ObservationIt happens after sleep or an update
Record whether a normal restart restores the list and whether sleep triggers it again. This points toward adapter/driver state but does not prove the cause by itself.

Step-by-step solutions

01

Compare the list and radio without changing the network

Separate a missing control, one missing network and a completely empty list.

  1. Check that airplane mode is off and Wi-Fi is on; check the laptop’s physical radio switch or key if present. Do not change the router password: authentication has not started yet.

  2. From the same location, compare the list with another device. If neither sees the expected network, ask its owner to check that it is on and broadcasting its name. If only this PC cannot see it but sees others, follow the missing-single-network branch.

  3. If Windows does not offer Wi-Fi, check the adapter. If it does but shows none of the networks another device sees, move to local radio and service checks.

02

Check whether Windows detects the adapter

  1. Find the wireless adapter and open its properties. Record its status and any code; do not uninstall the device.

    1. Device Manager
    2. Network adapters
  2. If it is disabled and this is your unmanaged PC, enable only that adapter and check the list again. If it shows Code 10 or Code 43, follow the specific guide: this is no longer only a visible-networks problem.

  3. If it is absent, an external USB adapter can be checked in another compatible direct port, without a hub or forcing connectors. If it remains absent, or is internal, contact the manufacturer/IT with the model. Do not download packages for an adapter Windows cannot even identify.

03

Check the band of the one missing network

  1. Move the PC closer to the access point and ask its owner which bands it broadcasts. If an authorized 2.4 GHz network appears but the 5/6 GHz network does not, that difference points toward compatibility or coverage rather than complete Wi-Fi failure.

  2. Check the exact adapter model in its official specifications. Wi-Fi 6 does not guarantee 6 GHz: Intel requires a compatible product, Windows 11, manufacturer enablement and regional availability for that band. Do not change the country to bypass restrictions.

  3. If someone manually restricted the band or wireless mode in the adapter’s advanced properties, record the value and correct it only according to the manufacturer. If that option is absent, skip it. Use a compatible band offered by the owner without disabling security; do not reset the router.

04

Separate radio, service and failure after sleep

  1. Open services.msc and inspect, without changing, the WLAN AutoConfig (WlanSvc) state. If stopped, discovery may not work: follow the missing-Wi-Fi-option guide or contact IT on a managed PC. Do not blindly change policies or startup types.

  2. Command Prompt
    netsh wlan show interfaces

    Read-only check: identifies the interface and, where shown, radio state. “There is no wireless interface” points to the adapter; a service error points to WlanSvc, not the router.

  3. Command Prompt
    netsh wlan show networks mode=bssid

    Compare detected networks with the Windows list. A permission or location requirement does not mean no networks exist: use the Windows interface and consult privacy policy/IT. Do not publish network names or identifiers without redacting them.

  4. If service and radio are active, save work and perform one normal restart. If networks return but fail again after sleep, record that pattern and the driver version for the manufacturer. If it began immediately after a driver update, evaluate only that rollback in the next step.

Sources:
Advanced

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

05

Roll back only an identified recent driver

  1. Continue only if the adapter is detected, failure began with a known driver change and you can access the manufacturer’s official package through another connection or device. On a managed PC, give this information to IT.

  2. If available, roll back that driver and restart when requested. If unavailable, do not uninstall to force it; contact the manufacturer.

    1. Device Manager
    2. Wi-Fi adapter
    3. Properties
    4. Driver
    5. Roll Back Driver
  3. Check the same network and, if it was the trigger, one normal sleep cycle. Stable recovery supports a driver regression; no change means preserve the results and escalate without cycling versions, resets or router settings.

Next step

Still not working?

Escalate with adapter model, status code, band visible on other devices and relation to sleep/updating. An absent adapter or no networks with active radio and service justifies manufacturer support; those tests alone do not diagnose a failed antenna or board. Do not reset the entire network without a new hypothesis.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems