Your PC's Wi-Fi keeps disconnecting because the link between the adapter and the access point is failing at the frame level, not because the internet is "down." The usual culprits are power-saving that puts the adapter to sleep, driver and firmware mismatches, band-steering or roaming decisions, 2.4 GHz interference, and weak signal at the client. Each causes a specific, observable failure: a deauth, a beacon miss, or an authentication timeout. Identifying which one is happening tells you what to fix.
The disconnect mechanism, frame by frame
Wi-Fi is a managed link, not a cable. The access point (AP) and your adapter continuously negotiate state, and either side can tear the link down. Three events account for most PC dropouts.
First, the deauthentication frame. The AP sends a deauth when it decides the client is gone, when a roaming handoff completes elsewhere, or when a management policy evicts the client. On enterprise and mesh networks, band steering and load balancing generate these deliberately. Your PC sees a clean disconnect and reconnects within seconds.
Second, the beacon miss. Every AP broadcasts a beacon roughly every 100 milliseconds. If your adapter misses a threshold of consecutive beacons (commonly 7 to 10, vendor-dependent), it declares the link dead and drops association. Weak signal, interference, or a saturated channel causes missed beacons even when Windows shows "connected."
Third, the four-way handshake failure. When the adapter tries to rejoin, it must complete WPA2 or WPA3 authentication and key exchange. A stale key, a mismatched passphrase cache, or a driver that mishandles the handshake produces repeated "authenticating" loops. In plain terms: the radio hears the network but cannot finish the password dance.
How often dropouts happen and what counts as abnormal
A single disconnect per week is normal on consumer gear. Multiple disconnects per hour is not, and it points to an active mechanism rather than random RF noise.
Consumer survey data and support-forum sampling consistently place persistent dropout complaints among the top Wi-Fi issues, though no authoritative body publishes a definitive rate. What is defensible: 2.4 GHz links in dense housing routinely see 10 to 30 competing networks, and each occupies overlapping channels. At 5 GHz, the usable channel count drops and DFS channels (52 to 144 in the US) add radar-driven vacate events that can force a band switch.
Windows event logs timestamp every disconnect. The WLAN-AutoConfig operational log records association and disassociation reasons, which converts "it keeps dropping" into a count and a cause code. That log is the single most useful diagnostic you have.
Driver, power, and firmware interactions
The adapter driver sits between the radio and the operating system, and it owns power state. Windows enables "Allow the computer to turn off this device to save power" by default on many adapters. Under this setting, the driver may enter a low-power state during idle and miss beacons, producing a disconnect that looks random but correlates with inactivity.
Driver version mismatches matter more than most guides admit. Intel, Realtek, MediaTek, and Qualcomm ship separate driver branches for the same chipset across OEMs. An OEM-customized driver can lag the chipset vendor's generic driver by months, and the lagging branch may mishandle WPA3, 802.11ax power save, or fast roaming. The counterintuitive detail: newer is not always better. Some chipset updates regress idle stability, and rolling back one or two versions resolves dropouts that an update introduced.
Firmware on the router side participates too. Mesh systems run roaming algorithms that decide when to push a client to a better node. A PC that clings to a distant node triggers repeated steering deauths.
Interference, band steering, and roaming edge cases
At 2.4 GHz, only channels 1, 6, and 11 are non-overlapping in the US. A neighbor on channel 3 bleeds into both 1 and 6. Microwave ovens, cordless phones, and Bluetooth coexistence add bursty noise. The adapter retries frames, latency climbs, and eventually beacon misses accumulate.
At 5 GHz and 6 GHz, the problem shifts. 6 GHz (Wi-Fi 6E) has clean spectrum but shorter range and worse wall penetration, so a PC at the edge of coverage drops more often than it did on 5 GHz. DFS radar events force the AP to vacate a channel, and clients that cannot follow the switch get dropped.
Band steering is a common edge case. The AP refuses or delays 2.4 GHz association to push your PC to 5 GHz. If the PC's driver responds poorly to the rejection, you get a connect-disconnect loop that repeats every few seconds until the client finally lands on the intended band.
Misconceptions that send people down the wrong path
"It's the ISP." An ISP outage kills internet access but leaves the Wi-Fi link associated. If Windows still shows connected with no internet, the dropout is upstream, not the radio link.
"Reinstalling Windows will fix it." OS reinstalls rarely change adapter firmware or router behavior. They may reset a corrupted profile, which is why it sometimes appears to work, but the underlying mechanism returns.
"More antennas means more stability." Antenna count affects throughput and MIMO, not link maintenance. A weak-signal client with four antennas drops as readily as one with two.
"5 GHz always beats 2.4 GHz." Range and penetration favor 2.4 GHz. A distant PC on 5 GHz disconnects more, not less.
"Disabling IPv6 helps." IPv6 has no role in layer-2 association. This advice persists but does not address disconnects.
Red flags that mean stop and escalate: Disconnects began immediately after a driver or router firmware update. The adapter disappears from Device Manager entirely. Event logs show authentication failures with no successful association between them. Dropouts affect only one device while others stay stable. The adapter or router runs hot enough to throttle.
Comparing the four common causes
| Cause | Typical signature | Time to first drop | Fix difficulty |
|---|---|---|---|
| Adapter power saving | Drops after idle periods | Minutes to hours of inactivity | Low |
| Driver/firmware mismatch | Drops after update, auth loops | Immediate to days | Medium |
| 2.4 GHz interference | Drops under load or at peak hours | Variable, load-correlated | Low to medium |
| Band steering / roaming | Repeated fast connect-disconnect | Seconds, at band edge | Medium |
| Weak signal at range | Drops with distance or walls | Distance-correlated | Medium to high |
A dropout timeline you can match to your logs
| Elapsed time | Event in log | What it means |
|---|---|---|
| T+0 s | Disassociation, reason code | AP or client initiated teardown |
| T+0.5 s | Scan for available networks | Adapter hunting for the SSID |
| T+1 to 3 s | Authentication request | Handshake begins |
| T+3 to 6 s | Association and 4-way handshake | Keys exchanged |
| T+6 to 10 s | DHCP request | IP lease renewed |
| T+10 to 30 s | Internet reachable | Link restored |
Reading the reason code is the shortcut. A code indicating the client left (often 3) points to power saving or a local decision. A code indicating inactivity or beacon loss points to RF. Repeated codes at the authentication stage point to credentials or driver.
Practical actions with thresholds
Work from cheapest and most reversible to most involved. Change one variable at a time and note the effect in the event log.
Disable adapter power saving: Device Manager, adapter properties, Power Management tab, clear the checkbox. Then in Power Options, set Wireless Adapter Settings to Maximum Performance on both AC and battery. Threshold to confirm success: zero idle-triggered disconnects over 24 hours. Update or roll back the driver: get the chipset vendor's generic driver if the OEM build is stale, or roll back one version if dropouts began after an update. Confirm over 48 hours. Pin the band and channel: set the router to a fixed non-overlapping 2.4 GHz channel (1, 6, or 11) or a clean 5 GHz channel. For a distant PC, prefer 5 GHz only if signal at the client stays better than roughly -67 dBm; below that, 2.4 GHz is more stable. Separate the SSIDs: if band steering causes loops, split 2.4 and 5 GHz into distinct names and connect the PC to the stable band. Update router firmware and, on mesh systems, disable aggressive client steering for the PC or reserve it on the nearest node.
Signal thresholds worth knowing: about -50 dBm is excellent, -60 dBm is good, -67 dBm is the common voice/video floor, and below -70 dBm dropouts become frequent. Measure with a Wi-Fi analyzer rather than trusting the Windows bars.
Limits of what local fixes can prove
You cannot fix what the router or the ISP controls. If event logs show clean association but internet reachability fails afterward, the radio is fine and the problem is upstream. If dropouts persist across a second adapter, the router or environment is the variable. If they persist across a second router, the PC or its driver stack is.
Some chipsets have documented stability regressions that no setting resolves, only a specific driver branch does. Others have hardware-level antenna issues that show as signal dropping sharply when the chassis is moved. Without packet capture on the client and AP, you can narrow the cause but sometimes not prove it.
For high-stakes environments such as medical devices, trading systems, or remote work with contractual uptime, treat a PC that drops Wi-Fi as unsuitable for that role until the mechanism is identified. General educational information only; for workplace or safety-critical network decisions, consult a qualified network engineer or your organization's IT authority.