How to Check Wi-Fi Channels on Windows with netsh

To see nearby Wi-Fi channels on Windows, open Terminal or Command Prompt and run netsh wlan show networks mode=bssid. Find the Channel field under each access point. Keep the command in English even when Windows displays its results in another language; translating show networks makes it a different, invalid command.

This gives you a local snapshot of networks your laptop can detect. It helps answer “which channel is this access point using?” It cannot by itself tell you which channel is least busy or why the internet is slow.

Run the correct command#

Turn Wi-Fi on and use a computer with a working wireless adapter. In Windows search, open Terminal or Command Prompt, then paste:

netsh wlan show networks mode=bssid

The mode=bssid option adds access point details to the network list. If you only want the network your computer is currently connected to, run:

netsh wlan show interfaces

Record the room, time and adapter you used. Repeat at the desk or room where the problem occurs, rather than treating a scan beside the router as the condition throughout the home. Moving the laptop changes what it hears; a different adapter can also show a different list.

Microsoft includes these commands in its Windows wireless troubleshooting guidance.

Understand SSID, BSSID, channel and signal#

An SSID is the network name. A BSSID identifies an individual access point radio. A mesh system or a router with multiple bands can expose several BSSIDs under the same SSID, so several rows do not necessarily mean several neighboring households.

A channel number needs band context, particularly with newer adapters and bands. Check the band field if Windows exposes it and confirm the radio in the router's status page. A missing field means this output is insufficient; avoid guessing the band or channel width from a single number.

For negative signal readings and signal-to-noise calculations, use the separate dBm, RSSI and SNR guide. A percentage in this command is not an SNR reading.

Work through an example#

This is shortened illustrative output, with invented names and identifiers. Labels and available fields vary with Windows, its language and the adapter:

SSID 1 : Example-Home
    BSSID 1 : 02:00:00:00:00:01
         Signal     : 80%
         Radio type : 802.11n
         Channel    : 6
SSID 2 : Example-Neighbor
    BSSID 1 : 02:00:00:00:00:02
         Signal     : 70%
         Radio type : 802.11n
         Channel    : 6

Both illustrated radios use channel 6. That is a reason to investigate shared airtime, not proof that the neighbor is causing the problem. An idle access point still appears; a busy client or non-Wi-Fi interference may not appear as another SSID.

For a useful comparison, make a small log:

If the router reports channel utilization, consider it alongside the scan. Counting visible SSIDs cannot replace that measurement. The channel congestion guide explains how to choose a channel and width once you have that evidence.

Fix missing networks or permission errors#

If no wireless interface appears, check that the Wi-Fi adapter is enabled in Device Manager, Wi-Fi is on and airplane mode is off. Ethernet connectivity does not give an Ethernet adapter the ability to scan wireless networks. Check the WLAN AutoConfig service if the command specifically reports that it is stopped.

If a network is missing, compare with another device in the same room and check whether the laptop supports that network's band. A hidden network name, unsupported band or radio setting can make the list incomplete. Do not conclude that the home has no interference because the scan is short.

If the command reports a location or access error, follow the message and review Windows location permissions. Microsoft's Wi-Fi access and location changes explain why access to BSSID-related Wi-Fi information can require location consent. On a managed computer, an administrator may control this setting. Running as administrator does not establish that location consent or organizational policy allows the scan.

Collect the error text and adapter details before resetting anything. The netsh wlan reference describes the available diagnostic commands; a network reset is not the first requirement for reading a channel.

Choose the next step from the evidence#

If Wi-Fi fails even near the router at the busy hour, inspect channel use, router load and the upstream connection. An extender will not create extra internet capacity or remove other networks from the air.

If the near-router test is healthy but a distant room consistently fails, investigate walls and placement. Change one thing, repeat from the same spots and test the activity that matters. Keep the scan as supporting evidence instead of converting a signal percentage into a promised speed.

For a coverage problem, download Range Up on iPhone or Android and draw the walls, router and target location. Its heatmap simulates coverage from the plan; it does not run Windows commands, scan channels or measure live RSSI. Premium adds extender placement, a recommended spot and a before/after comparison. Use real device readings to check the arrangement afterward.