Windows Wi-Fi keeps disconnecting? Use the WLAN report

A Wi-Fi dropout can last only a few seconds. Windows reconnects, the call resumes, and the cause stays unclear. Before changing network settings, save a record of what happened. Windows includes a wireless network report that summarises recent connection sessions, disconnect reasons, adapter details and related events. Microsoft's troubleshooting guidance recommends collecting this baseline before resetting the network stack, deleting Wi-Fi profiles, removing an adapter or driver, or restarting the PC, because those steps can remove evidence or change the behaviour. Microsoft's wireless troubleshooting guide

This guide is for Windows 11 and supported Windows 10 versions. The report can help you build a timeline. It cannot identify the root cause from one event by itself.

First, separate a Wi-Fi drop from an internet problem

If Windows shows that it disconnected from the wireless network and then reconnected, the Wi-Fi session ended. If Windows still shows the PC connected but websites, games or apps cannot reach the internet, the wireless link may still be active while a later part of the network path has failed.

That distinction changes what to investigate. Microsoft's guidance says that when Wi-Fi remains associated but network access fails, continue with TCP/IP, DHCP, DNS, proxy or firewall checks. A WLAN report full of successful, uninterrupted sessions is not proof that internet access worked throughout those sessions.

Generate the report before changing settings

1. In the taskbar search box, type Command Prompt.
2. Right-click Command Prompt, choose Run as administrator, and approve the prompt.
3. Run:

netsh wlan show wlanreport

Windows creates an HTML report and displays its location when the command finishes. Open that file in a browser. The netsh wlan command reference lists show wlanreport for Windows 10 and Windows 11; Microsoft's troubleshooting guide describes the report contents and output path. Microsoft's `netsh wlan` reference

Generate the report soon after the next dropout. It summarises recent wireless sessions, so an older event may be outside the history it contains. Write down the approximate time and time zone when the problem occurs. Also note what you were doing, whether the PC had just woken from sleep, and whether another device lost its connection at the same time.

If the problem is happening now, collect the report before forgetting the Wi-Fi network, removing the adapter, or reinstalling its driver. You can make those changes later if the evidence points to them.

Match the report to the time Wi-Fi dropped

Start with the summary of wireless sessions and find the entry closest to your recorded time. Confirm that it belongs to the Wi-Fi adapter you use. Then look at the session duration, the reported disconnect reason and the events around that point.

Ask three questions:

• Did Windows record a disconnect at the same time? If not, check whether the symptom was “connected, no internet” rather than a lost Wi-Fi session.
• Does the same adapter disconnect repeatedly? A pattern on one PC gives you a reason to inspect its adapter, driver, Windows updates and sleep or resume history.
• Did other devices lose Wi-Fi at that time? If several devices were affected together, the shared router or access point becomes a useful place to investigate. That pattern narrows the search; it does not identify which shared component failed.

A disconnect reason is a clue about what Windows recorded, not a standalone diagnosis. Event details can vary with the Windows version, adapter, driver, access point and authentication method. Microsoft documents these limits in its troubleshooting guidance.

Let the pattern choose the next check

If only one PC drops, compare the wireless adapter's driver version and date with the PC or adapter manufacturer's recommended version. Check whether the issue began after a Windows, driver, firmware or BIOS update, or after sleep and resume. Make one change at a time and repeat the same activity so you can tell whether it helped.

If the problem appears only in one room, test closer to the main router and record whether the timing changes. If it happens while moving through a building with several access points, note whether Windows appears to roam between them. Location and timing can point toward coverage or roaming, but a report from the PC cannot reveal every condition inside the router or access point.

For a more detailed event history, Microsoft's guide points to Event Viewer → Applications and Services Logs → Microsoft → Windows → WLAN-AutoConfig → Operational. Record the time of the failure before looking for a matching event. If the PC belongs to work or school, ask the IT administrator before changing managed network profiles or driver settings.

Keep the report private

Wireless reports can contain device, adapter and network identifiers. Review the file before sharing it. Send it through the support channel of your PC maker, internet provider, workplace or school, and remove identifying details before posting it in a public forum. Microsoft's guidance notes the identifiers these reports and traces may contain.

The useful result is a timeline: whether Windows recorded a Wi-Fi disconnect, when it happened, which adapter was involved, and whether other devices were affected. That gives you a better next check than changing several settings and hoping the next dropout disappears.

Sources and further reading

• Microsoft Learn, Wireless network connectivity issues troubleshooting , last updated 29 July 2026.
• Microsoft Learn, `netsh wlan` , last updated 9 October 2025.