How to Read a Windows Wi-Fi Report to Diagnose Random Disconnects
If a Windows laptop drops Wi-Fi for a few seconds and reconnects before you can inspect it, the connection history can be more useful than another speed test. Windows includes a built-in wireless network report that turns recent Wi-Fi sessions and adapter information into an HTML file.
The command is:
netsh wlan show wlanreport
The report covers the previous three days. It is not a packet capture and it cannot prove what happened inside an access point, but it gives you a timeline that helps separate a client-side problem from a wider wireless outage.
1. Generate the report
-
Reproduce the disconnect if possible, then note the approximate time.
-
Open Windows Terminal or Command Prompt as an administrator.
-
Run:
netsh wlan show wlanreport -
Read the output for the path of the generated HTML file and open that file in a browser.
Run the command soon after the fault. The report is limited to recent history, so an incident older than three days may no longer appear.
Microsoft documents the command and the report sections in its guide to analysing the Windows wireless network report.
2. Start with the session timeline
The summary chart groups activity into Wi-Fi connection sessions. A red error marker is a useful place to start, but do not treat every warning as the root cause.
For each affected session, note:
- Start and end time: Does the failure line up with the time users noticed it?
- SSID: Did the laptop switch to another saved wireless network?
- Connection mode: Did Windows connect automatically or after a manual action?
- Session duration: Does the session end after a predictable interval?
- Disconnection reason and events: What did Windows record immediately before the session ended?
Compare a failed session with a successful one from the same laptop. A repeated pattern is more useful than a single event viewed in isolation.
3. Check the adapter and driver details
The report lists network adapters, including hidden adapters, and shows information such as the adapter name, driver version, driver date and any reported problem number.
You can collect a fresh adapter summary with:
netsh wlan show drivers
netsh wlan show interfaces
Look for the supported radio types, driver details, current connection state, signal and channel information. Compare the adapter model and driver version with the laptop or wireless-adapter manufacturer’s support page. Prefer the computer manufacturer’s validated driver when it provides one; do not assume the newest generic driver is always the right choice.
If only one laptop disconnects while nearby devices stay online, investigate that laptop’s adapter, driver, saved profile and power settings before changing the access point.
4. Correlate the report with Windows event logs
The report provides a readable overview. For more detail, inspect the WLAN AutoConfig operational log around the same timestamp.
In PowerShell, run:
Get-WinEvent -LogName 'Microsoft-Windows-WLAN-AutoConfig/Operational' -MaxEvents 50 |
Select-Object TimeCreated, Id, LevelDisplayName, Message |
Format-List
Find entries close to the disconnect time. Read the events before and after the failure as a sequence: authentication, association, roaming, disconnect and reconnect events can explain more together than a single event ID.
If the log is empty or unavailable, check that the WLAN AutoConfig operational log is enabled in Event Viewer under Applications and Services Logs > Microsoft > Windows > WLAN-AutoConfig. Event availability and wording can vary by Windows build and driver.
5. Decide whether the fault is local or shared
Use a second device as a control. Test it on the same SSID and, if practical, near the affected laptop.
| Evidence | What to investigate next |
|---|---|
| One laptop disconnects; other devices stay connected | Laptop driver, adapter power management, saved profile or hardware |
| Several devices disconnect at the same time | Access point, wireless controller, channel changes, power or upstream network |
| The laptop stays connected to Wi-Fi but loses internet access | DHCP, gateway, DNS, firewall or ISP path rather than radio association alone |
| Disconnects happen only in one room | Signal strength, interference, roaming thresholds and access-point placement |
| Disconnects begin after a driver or OS update | Driver compatibility and recent configuration changes |
A Wi-Fi disconnect is not automatically an internet outage. If Windows remains associated with the access point, test the local gateway and DNS separately. Our guide to basic wireless networking concepts explains the roles of the access point, client and wireless security.
6. Apply one change at a time
Once the evidence points to a likely cause, change one variable and collect another report:
- Install a suitable adapter driver from the PC or adapter manufacturer if the current driver is outdated or known to be faulty.
- Check whether adapter power-management settings are suspending the device. Test a change only if the disconnect pattern supports that hypothesis.
- Compare the 2.4 GHz and 5 GHz bands where both are available. A different band can help distinguish coverage from compatibility or interference.
- If several clients fail together, review access-point logs, channel utilisation, firmware and wired uplink health.
- Record the time of each test so it can be matched against the next report.
Avoid changing channel width, security mode, roaming settings and drivers all at once. If the problem disappears, you need to know which change made the difference.
7. Treat the report as diagnostic data
The report can contain the computer name, Windows build, user and domain information, adapter identifiers, SSIDs and saved wireless-profile details. Microsoft notes that profile security keys and passwords are not displayed, but the remaining information can still reveal details about a person or organisation.
Before sending the HTML report to a public forum or an outside support provider, review it and redact identifying information. Share it only with people who need it to troubleshoot the issue.
What the wireless report can—and cannot—tell you
The report is a strong first step when a Windows device disconnects intermittently: it provides a recent session timeline, adapter information and disconnect events in one place. It does not replace an access-point log, a packet capture or a test from another device. Use it to narrow the fault, then confirm the suspected cause with one controlled change.
If you are building a repeatable troubleshooting method, Subnetica offers interactive networking lessons, graded quizzes and hands-on labs that run in the browser. You can start with the free networking lessons without installing a simulator.