Wi-Fi Keeps Disconnecting: Separating the Layers
Three layers fail differently: the adapter, the wireless link, the internet beyond it. Power saving, band steering and roaming each look like a drop.
“Wi-Fi keeps disconnecting” covers at least four unrelated failures, and the first job is working out which one is happening. The adapter losing the connection, the link degrading until it is unusable, the client roaming badly, and the internet dropping behind a perfectly healthy wireless link all present as the same complaint.
Separate the Layers First
| Test | Result | Points at |
|---|---|---|
| Can the device reach the router’s interface during a drop? | Yes | Wireless is fine; problem is upstream |
| No | Adapter or wireless link | |
| Do other devices drop at the same moment? | Yes | Access point, or the connection behind it |
| No | The one device’s adapter or driver | |
| Does it drop only when the machine is idle? | Yes | Power saving |
| Does it drop when moving between rooms? | Yes | Roaming behaviour |
| Does it drop at a consistent time of day? | Yes | Interference from a scheduled device, or an ISP event |
This table is most of the diagnosis. The answers separate a driver problem from a radio problem from an upstream problem, and each has a different fix.
Adapter Power Saving
Windows reduces the power state of a wireless adapter when the machine looks idle, and some drivers do not recover the connection cleanly afterwards. The result is a drop after a period of inactivity, often noticed when returning to a machine that was left alone.
Two settings control it. The adapter’s advanced properties hold a power saving option, and the active power plan holds a separate wireless adapter setting. Both have to be changed; altering one and leaving the other is why this fix often appears not to work.
This is the single most common cause of drops on laptops that are otherwise stable, and it is quick to rule out.
Band Steering
Where both radio bands share one network name, the access point steers clients toward whichever band it considers better. The handover is meant to be invisible.
On some client drivers it is not, and each steering event produces a brief disconnection. The test is to separate the bands into two distinct network names temporarily and connect the device to one of them explicitly. If the drops stop, steering was the cause.
The fix is either to leave them separated, to disable steering on the access point, or to update the client driver, depending on which is under your control.
Roaming Between Access Points
In a network with several access points sharing a name, the client decides when to move from one to another. Access points can encourage it, but the decision belongs to the client.
Some clients hold a weak signal stubbornly, staying attached to a distant access point long after a nearer one would serve better. The connection degrades to the point of being unusable, then finally roams. Experienced from the user’s side, this is a drop that happens when walking between rooms.
Some adapters expose a roaming aggressiveness setting in their advanced properties. Raising it makes the client move sooner. Where the access points support it, the standards-based roaming assistance features help clients make better decisions, but only if both ends implement them.
Interference and Channels
The 2.4 GHz band has a small number of non-overlapping channels and long range, which means in any dense area it is crowded with networks that overlap each other. Overlapping networks do not share cleanly; they interfere, causing retries and collapsed throughput.
Non-network sources matter too. Microwave ovens, some cordless phones and certain video senders all sit in the same band, and a drop that happens at the same time every evening is worth correlating with something being switched on.
The 5 GHz band has far more channels and much less congestion, at the cost of range and wall penetration. Where a device can use it and stays in range, moving it there resolves a category of problems outright.
Access points that select their channel automatically usually do so at boot and then stay put, so a channel chosen when the neighbourhood was quiet may be a poor one now.
Drivers
A driver update is worth trying when the drops started after a Windows update, when the adapter is a model with known issues, or when nothing else fits. Obtain it from the machine or adapter manufacturer rather than through a general search, because wireless adapters are sold under many names with different firmware.
Rolling a driver back is equally valid when the drops began after a driver changed. Device Manager holds the option and it is reversible.
When the Wireless Is Fine
If the router remains reachable during a drop, the wireless link is working and the problem is beyond it. That moves the investigation to the connection itself, the router’s handling of it, or the path upstream.
Repeated brief losses upstream often show in the router’s own log. Packet loss against latency covers how to characterise what is happening on that path, and CGNAT covers a related class of connection problems that look like drops from inside the network.
What People Get Wrong About This
The first mistake is changing settings before establishing which layer is failing. Adjusting roaming aggressiveness does nothing for a connection that is dropping upstream.
The second is changing only one of the two power saving settings and concluding power saving was not the cause.
A third is moving to a mesh system to solve drops that were caused by client roaming behaviour. More access points give a stubborn client more options it will not take.
A fourth is testing with one device. Whether other devices drop at the same moment is the single most informative question available.
And the last is assuming a strong signal indicator means a good connection. Signal strength says nothing about interference, and a strong signal on a congested channel performs worse than a moderate one on a clear channel.
A Working Order
Establish whether the router stays reachable. Check whether other devices drop simultaneously. Rule out power saving, which is quick. Test with the bands separated. Look at the channel and at what else is on it. Then consider drivers, and only then the hardware.
Common questions
How do I tell whether it is the Wi-Fi or the internet?
Check whether the device still reaches the router while it appears disconnected. If the router's own interface loads but nothing beyond it does, the wireless link is fine and the problem is upstream. If the router is unreachable too, the drop is in the wireless link or the adapter.
Why does Wi-Fi drop when the laptop is idle?
Adapter power saving. Windows lowers the adapter's power state when the machine appears idle, and on some drivers the connection does not survive that transition cleanly. The setting lives in the adapter's advanced properties and in the power plan, and both need changing for the behaviour to stop.
What is band steering and why does it cause drops?
It is the access point encouraging a client onto the less congested band when both share one network name. The transition should be seamless and on some client drivers it is not, producing a brief drop each time. Separating the bands into two named networks is the usual test.
Why does Wi-Fi drop when I walk between rooms?
Roaming between access points that share a network name. The client decides when to switch and some clients hold onto a weak signal far too long before moving, so the connection degrades to unusable before it finally roams. This is a client behaviour, adjustable on some adapters.
Could a neighbour's network be causing this?
On the 2.4 GHz band, yes. It has few non-overlapping channels and they are crowded in any dense area. Overlapping networks interfere rather than politely sharing, and the result is retries, slow throughput and apparent drops. The 5 GHz band has far more room.
Read next
- Carrier-Grade NAT: Why Your Public IP Isn't Yours Learn what carrier-grade NAT is, how to detect if your ISP uses it, and what you can and cannot fix from your side.
- Double NAT: What It Is and How to Fix It Double NAT occurs when two routers translate your traffic. Learn how to detect it, fix it with bridge mode, DMZ, or port forwarding, and know when you can't fix it.
- Multiple VPN Connections: Why the Second Tunnel Fails Learn why running multiple VPN connections from one network often fails due to NAT and routing conflicts, and how to fix it.
- ARP and MAC Addresses: Finding the Hardware How a host finds the MAC behind an IP, why ARP never leaves the local network, and how a stale cache entry produces a confusing partial outage.
- chkdsk, SFC and DISM: Which One to Run and When Three repair tools with three different jobs. Why DISM comes before SFC, what chkdsk actually checks, and when chkdsk can finish off a failing drive.