Find evidence of a Wi-Fi drop with Windows 11’s wireless network report

When Wi-Fi drops intermittently on a Windows 11 laptop, “it disconnected again” gives support little to investigate. A wireless network report can help you connect a recorded event with the time you noticed the problem, before making more changes.

This guide explains how to collect and use that evidence. For the underlying troubleshooting sequence, see Wi-Fi keeps disconnecting. Generating a report is a diagnostic step, not a repair.

1. Capture the symptom and time first

At the next interruption, note the time, room, activity and whether Windows actually left the Wi-Fi network. Check whether another device had trouble at the same time.

If the laptop remains connected but websites fail, keep that distinction in your notes. Our connected but no internet guide covers that branch. A dropped call by itself does not establish a wireless disconnection.

2. Create the report

Microsoft’s report instructions use an administrator Command Prompt. On a managed work or school computer, ask IT before proceeding; do not try to bypass an administrator restriction.

1. Search Windows for Command Prompt.
2. Right-click it and choose Run as administrator. Approve only the expected Windows prompt.
3. Enter the following command and press Enter:

netsh wlan show wlanreport

Open the HTML report at the location shown in the command’s output using your browser. Microsoft says it groups the last three days of Wi-Fi events into connection sessions.

If the command fails, record the exact message. Do not paste unrelated reset commands from a forum to make this step succeed. If your problem happened outside the report’s time window, collect fresh observations when it next occurs.

3. Match one event to your notes

Use the summary chart to find the session near your recorded time. Microsoft identifies red circles as errors; selecting a chart section leads to its session details. Look at the disconnection reason and related events.

Start with one occurrence rather than counting every coloured mark as a new fault. Ask: is this the same time as the interruption, was this the affected adapter, and were you intentionally disconnecting or moving the laptop?

A matching event strengthens the case that Windows recorded a connection problem. It does not, on its own, prove that the router, driver or internet provider caused it. An event with a technical-looking name is evidence to interpret, not an instruction to replace hardware.

4. Share a small, redacted excerpt

The report can contain computer and user details, network names, addresses and certificate information. Microsoft says Wi-Fi security keys and passwords are not displayed, but that does not make the full report suitable for a public upload.

Prefer a short description of the relevant event and your comparison results. If a screenshot is needed, remove unrelated network names, account details and identifiers. Our Windows screenshot guide helps keep the evidence focused.

Use your organization’s approved support channel for work-device reports. Do not send a complete report to an unsolicited person offering remote support.

5. Choose the next test from the pattern

• Only this laptop has trouble: give its manufacturer or IT team the event, timing and recent software changes.
• Several devices fail together: include that shared timing when contacting the router provider or ISP.
• No matching disconnection appears: revisit whether this was a Wi-Fi drop, an internet-access problem or one failing app. Absence of a matching event does not certify the network as healthy.

Keep the original notes so a later test can be compared fairly. This documentation-based guide does not claim that the report was generated or tested on your equipment.