>

Windows Wi-Fi keeps disconnecting: diagnose and fix it

Find out why your Windows PC keeps dropping Wi-Fi using netsh diagnostics, then clean up the saved profile and reconnect.

WindowswlannetshcmdWi-FitroubleshootingDiagnosticsMedium risk
Run netsh wlan show wlanreport first — the report names the actual disconnect reason.

What this covers

Random Wi-Fi drops on Windows usually come down to a bad signal, a congested channel, or a corrupted saved network profile. This guide walks you from finding the cause to reconnecting on a clean slate, all from the command line.

Symptom

?Your Windows PC repeatedly loses its Wi-Fi connection — the network icon drops to the globe or reconnects on its own every few minutes or hours.

Generate a Wi-Fi health report to find the disconnect reason

Before changing anything, find out why the connection drops. The wlanreport gives you an HTML timeline of the last three days of Wi-Fi sessions, including disconnect reasons and signal trends. You can tell it worked when the command prints the path to the report file — open it and look for the sessions marked as disconnected and the stated reason.

WindowsGenerate a Wi-Fi health report on Windows (netsh wlan show wlanreport)Medium riskStep 1

Produce an HTML report of the last three days of Wi-Fi sessions, disconnect reasons and signal trends — hidden inside netsh.

Command
$ netsh wlan show wlanreport
Full explanation & undo →

Check live signal strength and channel

Weak signal or a congested channel is a common cause of repeated drops. This shows the live state of the current wireless connection, including signal percentage and the radio channel in use. It worked when you see your connected SSID with its signal level — note whether it is low or fluctuating while the disconnects happen.

WindowsCheck Wi-Fi signal strength and channel on WindowsMedium riskStep 2

Show live details of the current wireless connection with netsh wlan show interfaces.

Command
$ netsh wlan show interfaces
Full explanation & undo →

Delete the broken Wi-Fi profile and start fresh

A corrupted or stale saved profile can cause Windows to fail handshakes and drop repeatedly. Removing the profile forces a clean reconnect with fresh settings. You will need the password again afterwards, so have it handy. It worked when the network no longer appears as a saved profile.

WindowsForget a Wi-Fi network on Windows with netshMedium riskStep 3Optional

Remove a saved wireless profile so Windows stops auto-connecting to a network, using netsh wlan delete profile.

Command
$ netsh wlan delete profile name="CoffeeShopWiFi"
▾ Undo
Undo
$ netsh wlan add profile filename="C:\path\to\profile.xml" user=current
Full explanation & undo →

Recover the saved password before reconnecting

If you deleted the profile in the previous step, or you suspect the stored password is wrong, reveal the stored key first so you can reconnect without guessing. It worked when the Key Content field shows the network password. (If you already deleted the profile, this will not find it — get the password from the router instead.)

WindowsShow a saved Wi-Fi password on WindowsMedium riskStep 4Optional

Reveal the stored password of a wireless network Windows has connected to, using netsh wlan show profile key=clear.

Command
$ netsh wlan show profile name="HomeWiFi" key=clear
Full explanation & undo →

Reconnect and confirm the connection holds

After cleaning up the profile, establish a fresh connection and watch whether it stays up. It worked when the interface shows a connected state; leave the machine for a while and, if it stays online through your normal usage period, the disconnect issue is resolved. If it still drops, go back to the wlanreport from step one and compare.

WindowsConnect to Wi-Fi from the Windows command lineMedium riskStep 5

Start a wireless connection to a saved network profile with netsh wlan connect.

Command
$ netsh wlan connect name="HomeWiFi"
▾ Undo
Undo
$ netsh wlan disconnect
Full explanation & undo →
!Deleting a Wi-Fi profile removes the saved password — recover it first or have it ready, or you will be locked out of that network until you re-enter it.

How to confirm it worked

After deleting the stale profile and reconnecting, the connection should stay up through a normal usage session. If drops recur, generate a new wlanreport and compare it with the first one.

Undo everything

Every command above can be reverted. Run these in order to undo all of it.

Undo everything
$ netsh wlan disconnect
netsh wlan add profile filename="C:\path\to\profile.xml" user=current

Review before running — some steps may not be independent.

Sources

  • NETSH - Windows CMD
    SS64 · technical · 2026-09-17
    Evidence: SS64 documents the netsh wlan context, which includes show subcommands such as the wlanreport used to generate a wireless report.
  • netsh
    Microsoft Learn · vendor-doc · 2026-09-17
    Evidence: Documents the netsh wlan context; `netsh wlan show interfaces` returns signal, channel and receive rate for the current connection.

Last verified: 2026-09-21

Related guides

Why does my Windows Event Log keep showing errors?
WindowsProblem fix

Work through repeating System and Application errors in the right order: query the log properly, look at the other places errors hide, then confirm the noise actually stops.

Medium risk7 steps
Windows battery report: check your laptop battery health from the command line
WindowsScenario

Generate a Windows battery report with powercfg, check live charge status, and trace what is draining power — all from the terminal.

Low risk4 steps
Windows slow boot: diagnose and fix it from the command line
WindowsProblem fix

A step-by-step CLI guide to finding out why Windows starts slowly — boot config, event log errors, startup bloat — and the fixes that actually help.

Medium risk7 steps