Windows 11 Wi-Fi Keeps Disconnecting: Troubleshooting

A disappearing Wi-Fi association is not the same symptom as staying connected to the wireless network while internet access fails. Watch the Windows network state when the problem occurs. If the PC drops the SSID, reconnects, or records a WLAN session ending, this workflow applies. If Windows remains associated with Wi-Fi but reports No Internet, use the separate connected-but-no-internet workflow because DHCP, gateway, DNS, router, or ISP reachability becomes the more useful diagnostic chain.

Also record the pattern before changing settings: whether the drop happens only after idle or sleep, only in one room, only on one SSID or frequency band, under sustained traffic, or immediately after a driver or Windows update. A repeatable trigger is much more useful than assuming weak signal, power saving, or a bad adapter from the symptom alone.

Windows includes a purpose-built WLAN diagnostic report. Open Command Prompt as administrator and run `netsh wlan show wlanreport`. Microsoft documents that the generated HTML report covers Wi-Fi events from the previous three days, groups them into connection sessions, and includes adapter details, driver information, session successes and failures, and disconnect reasons.

Use the report as evidence, not as an automatic hardware verdict. Match the timestamp of a real drop to the relevant wireless session and record its disconnect reason and surrounding events. Repeated failures with the same timing can narrow the investigation, while a single reason code without reproduction may only describe how Windows observed the session ending rather than why the underlying radio, access point, driver, or user action caused it.

Microsoft recommends testing the same Wi-Fi network with another device. Do that near the affected PC so the comparison is not dominated by location. If several devices disconnect together, the shared router, access point, upstream power, or radio environment deserves attention before reinstalling the Windows adapter. If only this PC drops while another device stays associated, the PC-specific branch becomes stronger.

When practical, also test the affected PC on a different trusted Wi-Fi network. A PC that remains stable elsewhere points back toward compatibility, coverage, band, or access-point behavior on the original network. A PC that repeatedly loses association across independent networks gives more weight to its adapter, antenna path, driver, power state, or Windows configuration. Neither result alone proves failed hardware.

Retest close to the router or access point. Microsoft specifically suggests trying another frequency band when a router exposes separate networks, such as 2.4 GHz and 5 GHz. A connection that is stable nearby or on one band but repeatedly drops at the original location is useful evidence for coverage, interference, band steering, or access-point configuration rather than a generic Windows networking failure.

Do not translate a signal-bar reading into a universal failure threshold. Walls, antenna orientation, neighboring networks, client capabilities, router channel width, and access-point placement all affect the usable link. If the problem is network-specific, use the router or access-point manufacturer documentation for supported channel and band settings instead of copying arbitrary channel numbers from a generic fix list.

If one SSID is consistently affected while other networks are stable, Microsoft documents forgetting the saved Wi-Fi network under Settings > Network & internet > Wi-Fi > Manage known networks and then reconnecting with the correct credentials. This is a focused way to rebuild that network profile without resetting every network adapter on the PC.

Use this step only when you know the credentials and any organization-specific requirements. Enterprise, campus, certificate-based, or managed networks can depend on profiles and policy supplied by an administrator. On those systems, preserve the WLAN report and contact the administrator rather than deleting managed configuration blindly.

Microsoft documents a Wi-Fi-specific power-management check in Device Manager: open the Wi-Fi adapter properties, use the Power Management tab when the driver exposes it, and clear “Allow the computer to turn off this device to save power.” Microsoft also documents the wireless-adapter power-plan setting for frequent connection drops. These are targeted tests when the symptom follows idle or power-state transitions.

Do not disable unrelated power-saving features across the PC in search of lower latency or a stronger signal. Not every adapter exposes the same controls, and a disconnect under load may have nothing to do with idle power management. Change one relevant setting, reproduce the original scenario, and keep the change only if the disconnect pattern actually changes.

Record the exact Wi-Fi adapter model, current driver version and date from Device Manager or the wireless report. If the problem began after a driver change, prefer the PC manufacturer or adapter manufacturer supported package and use a supported rollback when the previously working driver is still available. Avoid generic driver-updater utilities and unrelated INF packages.

Microsoft documents uninstalling the network adapter in Device Manager and restarting Windows as a later troubleshooting step, with an important precaution: obtain a backup driver first if losing connectivity would prevent you from downloading one. A successful reinstall is evidence that the driver/device configuration mattered; a persistent drop after reinstall is not proof that the physical adapter has failed.

Windows Network reset is not a harmless first step. Microsoft says it removes installed network adapters and their settings, reinstalls the adapters after restart, and can require networking software such as VPN clients or Hyper-V virtual switches to be configured again. Use it only after narrower profile, radio, power, and driver tests have failed.

After any change, verify the same failure condition rather than stopping as soon as Wi-Fi reconnects. Check whether the WLAN session remains stable through the period, location, sleep cycle, or workload that previously caused the drop. If the PC still disconnects across multiple independent networks after supported driver and configuration checks, preserve the wireless report and involve the PC or adapter vendor before replacing hardware.