Your WiFi drops. The little globe icon takes over from the signal bars, or the bars sit there full and nothing loads, which is the more annoying version of the same problem. Before you factory-reset the router or sit on hold with your provider for half an hour, work the fault in order. Cheapest and least destructive checks first. Phone calls and new hardware dead last. I have watched a customer buy a brand new router to fix something a 30 second power cycle would have cleared, so let us not repeat that particular Tuesday.
How to fix WiFi in the right order
A WiFi fault has a diagnostic tree, and the trunk of it is a single question: how much of your network is actually broken. Answer that and half the guesswork falls away. Here is the sequence I run on a call, top to bottom, and you stop the moment the connection comes back.
- Work out whether one device is down or every device is down.
- Power-cycle the modem and router, and wait the full count.
- Forget the network and rejoin it with the correct password.
- Reset the Windows network stack from an admin prompt.
- Update the WiFi driver in Device Manager.
- Move bands or change the router channel if the signal is weak.
- Only now do you get to blame your ISP.
Notice what is missing from the top of that list. No factory reset. No new equipment. The order is deliberate, and it follows the same rule as every other fault on this site: try the free thing before the expensive thing, and the software thing before the hardware thing.
Is it one device or all of them
Pull out your phone, turn its WiFi on, and try to load a normal web page while the laptop is still failing. That one test splits the problem cleanly.
If every device on the network is dead, the fault lives at the router or upstream at your ISP, not in your laptop. If the phone and the tablet are happily online and only the one machine refuses, the problem is that machine. Its adapter, its driver, its saved password, its settings. This is the fork in the road, and getting it right saves you from resetting the wrong box.
One quick catch before you go further. Look at the physical laptop. Some models have a hardware WiFi switch on the side or an Fn key combo (often Fn plus F2, F3, or a key with a little antenna icon) that kills the wireless radio. And airplane mode, toggled on by accident, shuts off every wireless radio at once. Check the Action Center on Windows 11 by clicking the network or battery icons in the bottom-right corner, and confirm airplane mode is off and WiFi is on. People miss this constantly. It is not stupid, it is just easy to bump.
Power-cycle the router (30 seconds)
Unplug the router at the wall. Not the reset pinhole, not the app, the actual power cable. If your modem is a separate box, unplug that too.
Now wait. A full 30 seconds, and count it, because the point is to let the capacitors drain and the temporary state clear, not just to blink the lights. A router is reset by a 30 second power cycle, and that power cycle wipes the temporary junk it has accumulated: a stalled DHCP table, a memory leak in old firmware, a heat-soaked chip that has been running for 200 days straight. Plug the modem back in first, give it a minute or two to sync, then plug the router in and let it fully boot before you test.
This one step resolves a genuinely embarrassing share of WiFi tickets. If it works, great, you are done, close the tab. While the router is cycling, it is worth logging into its admin page later to check that the firmware is current, because outdated router firmware causes the exact kind of random drops people assume are the ISP’s fault.
Reset the network stack on Windows
Say the phone is online and only your Windows machine is stubborn. Now the problem is on the software side of that laptop, and the network stack is the usual suspect. A stuck IP lease, a poisoned DNS cache, a Winsock catalog that some half-removed VPN client left in tatters. You can rebuild all of it from the command line.
Open Command Prompt as administrator. Press the Start button, type cmd, then right-click Command Prompt and choose Run as administrator. Run these one at a time, pressing Enter after each.
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock resetHere is what each one does, because running commands you do not understand is how people get scared off doing them at all. ipconfig /flushdns clears the DNS cache, so your PC stops trying to reach sites at addresses that may have changed. ipconfig /release drops your current IP lease and ipconfig /renew asks the router for a fresh one, which fixes a stuck or duplicate address. netsh winsock reset repairs the Winsock catalog back to its default state, undoing the broken hooks that VPNs, proxies, and antivirus tools sometimes leave behind.
The Winsock reset only takes full effect after a reboot, so restart the machine before you decide whether it worked. Nothing here deletes your files or your saved networks, so it is a safe sequence to run.
Still dead after the reboot? There is a heavier option. Go to Settings > Network & Internet > Advanced network settings > Network reset, and click Reset now. A network reset removes and reinstalls every network adapter and returns networking components to defaults. Fair warning, and this is the part people skip and then curse me: it forgets all your saved WiFi networks and passwords, so have your WiFi password written down before you click it. The machine restarts on its own a few minutes later.
Update the WiFi driver in Device Manager
An outdated or corrupt WiFi driver drops connections for no reason you can see. Connected one minute, limited the next, fine again after a reboot. That pattern points at the driver more often than at the router.
Right-click the Start button and open Device Manager. Expand Network adapters, find the entry with “Wireless” or “Wi-Fi” in its name (often something like Intel Wi-Fi 6 AX201 or a Realtek adapter), right-click it, and choose Update driver, then Search automatically for drivers. Windows will look for something newer and install it.
Windows often reports the driver is already up to date when a better one exists on the manufacturer’s site. If the auto-search comes up empty and you are still dropping, note the adapter name from its Properties box, and download the current driver straight from Intel, Realtek, or your laptop brand (Dell, HP, Lenovo, ASUS). That is the most reliable source.
Two situations flip the fix. If the drops started right after a Windows or driver update, do the opposite: right-click the adapter, choose Properties, open the Driver tab, and use Roll Back Driver to return to the version that worked. And if you want to force a clean reinstall, right-click the adapter, pick Uninstall device, then reboot. Windows reinstalls a fresh copy on startup. Do that one over Ethernet or with the installer already downloaded, so you are not stuck without WiFi and without a way to get the driver.
2.4 vs 5 GHz and the channel
Most home routers broadcast two bands, and they are good at different jobs. The 2.4 GHz band offers longer range and punches through walls better, but it is crowded and slow, capping out around 100 Mbps in the real world. The 5 GHz band offers much faster speed at short range and drops off quickly once you put a wall or two between you and the router.
So if the WiFi is technically connected but crawling, your position in the house matters. Far from the router, or through a couple of brick walls, and 2.4 GHz will hold a connection where 5 GHz gives up. Sitting in the same room streaming or on a video call, and 5 GHz is the one you want. A weak signal is worsened by distance and walls, plainly and simply, and no amount of driver fiddling changes physics.
Interference is the other half. The 2.4 GHz band shares its airspace with microwaves, baby monitors, cordless phones, and every neighbour’s router in an apartment block. If yours keeps stuttering at the same time each evening, WiFi interference is reduced by changing the router channel. Log into the router admin page and set the 2.4 GHz channel to 1, 6, or 11, since those three do not overlap. Leave it on Auto if that has been fine, but a manual pick to 1, 6, or 11 often steadies a congested band.
When it is your ISP
You have power-cycled everything, the driver is current, the phone is just as dead as the laptop, and the router lights show no internet. At that point the fault is upstream and out of your hands.
A slow or dead connection on every site, on every device, after a proper power cycle, may indicate an ISP outage. Check it on your phone’s cellular data, not on the WiFi that is broken. Most providers have a status or outage page, and many will text you an estimated fix time if you ask. Before you call, kill any VPN and test again, because a VPN can quietly cut your speed and make a healthy line feel broken. Turn it off, reload a page, then decide.
Here is the honest line on when to stop. If a power cycle, a network reset, and a current driver all fail, and the modem’s internet light is off or red with no outage on the provider’s map, call the ISP and let them push a signal to the modem or send a tech. Do not buy a new router to chase a dead upstream line, and do not start swapping parts inside the laptop over what is almost certainly a service problem. And if only your one machine will not connect after every software step above, the WiFi card itself may be failing, which on most laptops is a cheap part but a proper teardown. If the rest of the machine has been sluggish on top of the WiFi trouble, that is a separate rabbit hole, and our guide on how to fix a slow computer walks that one.
The repair ticket
Symptom. WiFi will not connect, keeps dropping, or connects with full bars but loads nothing.
Cause. In order of likelihood: a router that needs a power cycle, airplane mode or a hardware switch left on, a stale IP or DNS cache and a mangled Winsock catalog, an outdated WiFi driver, a weak or congested band, and last, an ISP outage.
Fix. Test one device against all devices to locate the fault. Power-cycle the modem and router for a full 30 seconds. On a single stubborn PC, run ipconfig /flushdns, /release, /renew, and netsh winsock reset, then reboot, and use Network reset if that fails. Update or roll back the WiFi driver in Device Manager. Match your band and channel to your distance from the router. If every device is down after all that, it is the ISP, so call them and do not buy hardware.