My Wi-Fi Isn't Working: Complete Troubleshooting Hub

Start here — where to begin when Wi-Fi isn't working

The single most useful first test costs ten seconds: check a second device. Your phone, a tablet, a laptop — anything that joins the same network. If it works fine, your internet and router are healthy and the problem lives inside the one struggling device, so skip straight to that device's guide in the by-device section. If nothing works, the problem is upstream — the router, the modem, or the provider — and the device guides won't help at all.

From there, the order matters. A proper power cycle of the router and modem comes before any settings work, because stuck router state (exhausted IP leases, hung connections) is the most common cause of "nothing changed, everything broke." Then a two-minute outage check, because reconfiguring your network while the street is down is just extra work. Only after those does it make sense to open settings on anything.

If the problem is intermittent rather than total — it works, then it doesn't — the router, ISP or device? guide teaches the pattern-reading that points at the right branch: what drops, when, and in which rooms. That pattern is the cheapest diagnostic you have, and it's worth two minutes of observation before any intervention.

How to tell whether the problem is the router, the ISP, or your device

Three tests separate the three suspects. Test one: how many devices are affected? One device means that device. All devices means the router or beyond. Test two: does a wired connection work? Plug a laptop into the router with an Ethernet cable. Wired works but Wi-Fi doesn't — the router's wireless side (or your device) is the problem. Wired fails too — the problem is upstream of Wi-Fi entirely: modem, line, or provider. Test three: does your phone work on mobile data? If mobile data is fine and home Wi-Fi isn't, it's your home network, not the phone.

Read the symptoms against this map:

One more signal worth reading: when did it start? "After an update" points at the updated thing (Windows, the router's firmware, a phone). "After I changed the router" points at the change (a setting, a cable, the WAN port). "No idea, it just did" is the classic modem or line symptom, which is exactly why the power cycle and the outage check come early in every guide in this hub.

How to check for an internet service outage

Two minutes here saves an hour of resetting things that weren't broken. Providers maintain a status or outage page (linked from their website's footer or support section), most have an app that flags planned maintenance for your area, and their social media accounts usually announce major outages within minutes. Check the page for your region, not just the national status — outages are usually local: a street, a building, a cabinet.

The informal checks are almost as good. Ask a neighbor on the same provider whether their internet is up; if two independent households are both down, you've found your answer. And note one reassuring detail: if your landline phone still rings while the internet is dead, the physical line to your house is almost certainly fine — many outages sit on the provider's equipment or the internet side of a combined line, not in your wall.

Two outcomes. If there's a confirmed outage, there's nothing to fix at home — note the reference number if one's given and check back; everything you reset during the outage was unnecessary, but harmless. If there's no reported outage and your neighbors are fine, the problem is yours to solve: work back through the power cycle and the location tests, and when you eventually call the provider, "no outage is showing" becomes a useful fact in the conversation.

Wi-Fi won't connect

There are two distinct failures, and they have different fixes. The network isn't in your list at all — the device can't see the network — versus it's listed but won't join — password rejected, "connecting…" that never finishes, or a join that immediately drops. Start by confirming the basics: Wi-Fi is actually on (and Airplane mode off — the two are easily confused after a swiping accident), and a second device still sees the network. If no device sees it, the router's wireless side is the suspect: restart the router and check that wireless isn't disabled (its Wi-Fi light, if it has one).

If the network is visible but won't join, work in this order. Forget the network on the device and reconnect from scratch, typing the password fresh — saved copies go stale, and passwords are case-sensitive in ways that bite. Then restart the router, because a router that's half-recovered from a power blip can broadcast fine while refusing connections. If it started failing right after the network name or password was changed, make sure every device is rejoining with the new credentials — mixed old and new is a classic source of "it works on my phone." If exactly one device still fails while others join normally, the problem has moved to that device: follow its guide in the by-device section, and on Windows check the Wi-Fi driver.

Two less common branches, only if everything above is clean: a network set to a hidden name (the device must be told to connect to a name it can't see — a deliberate security choice, not a bug), and MAC filtering on the router (a list of allowed devices, which new or replaced devices fail silently against). Both are router settings you'd only touch with a clear reason — and changing router settings is a write-down-what-you-changed activity.

Connected to Wi-Fi but no internet

The Wi-Fi icon is full but nothing loads. That screen means your device reached the router — the wireless part is working — and the break is somewhere upstream: either the router isn't getting internet from the provider, or this one device has an address/DNS problem of its own. The separating question, again, is the second device: if other devices are also without internet, stop fiddling with your device and go to the router. If you're the only one affected, the router is fine and the fix is in your machine's network settings.

Everyone's-down branch: power cycle the modem and router in the right order — it clears the most common cause (a router holding a dead upstream session). Then check for an outage. Then read the router lights — an off or red internet light is a direct statement. If the lights say "connected" but nothing loads, the provider's line is the remaining suspect, and the pre-call checklist is your next step.

Your-device-only branch: the usual suspects are a stuck IP address or a stale DNS cache (DNS is the service that translates names like example.com into the numbers machines actually use). On Windows, from an administrator command prompt, renew the address and flush the cache — both are safe and reversible:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

A useful probe before anything else: with a command prompt open, run ping 1.1.1.1. If that succeeds but websites don't load, your connection is up and it's specifically a DNS problem — the fix is making the DNS setting automatic (it usually is by default) or, as a test, pointing the device at a public resolver. If the ping fails too, the device has no real connection, and the IP renewal or a network settings reset is the move. After a renewal, reconnect once and retest with a plain page — not the homepage you're used to.

Wi-Fi keeps disconnecting

Intermittent drops are the one symptom where the pattern does the diagnosing, so before touching settings, spend ten minutes noting three things: do all devices drop, or one? Does it happen under heavy use, at idle, or on a schedule? And does it happen in particular rooms? Each combination points somewhere different, and fixing without the pattern is how people change three router settings that were never the problem.

One device drops: the leading cause is power saving. On Windows, open Device Manager → Network adapters → your Wi-Fi adapter → Properties → Power Management, and uncheck "Allow the computer to turn off this device to save power" — it sounds too trivial to work, and it too often does. On other systems the equivalent is Wi-Fi power management in the device's settings. The second suspect on a single device is a flaky driver: update or reinstall the Wi-Fi driver (Windows) or reset the network settings (other platforms). All devices drop: think router state and heat — a power cycle first, then check the router isn't baked into a cupboard or under a blanket; sustained heat makes routers drop clients. A router firmware update from the manufacturer is the next step if drops persist with a cool, well-ventilated router. One room drops: that's signal, not malfunction — weak signal and dead zones cover it.

Two settings are worth knowing exist but changing only with a reason: the router's wireless channel (leave it on automatic unless you've actually measured interference — the coverage guide explains why) and the band (2.4 GHz vs 5 GHz). Random drops that survive the power cycle, the driver work, and a firmware update are worth raising with the provider, because a degrading line can show up as Wi-Fi flakiness before it shows up as anything else.

Wi-Fi is very slow

"Slow" is two different problems wearing the same complaint, and one test separates them: run a speed test wired into the router, right next to it, and another over Wi-Fi where you actually use the machine. If the wired number is close to your plan and the Wi-Fi number is far below, the internet is fine and the slowness is inside your home — distance, interference, band choice, congestion. If even the wired test comes in far below your plan, the provider side is the suspect, and the speed-test results (with timestamps) are exactly what the pre-call checklist tells you to bring.

The home-side causes, in frequency order. Distance and walls — the classic; the fix is the coverage guide, starting with where the router sits. Band choice — 5 GHz (or 6) is fast but short-range; 2.4 GHz reaches further but shares the air with half the neighborhood; a device that "is slow in the next room" is often on the wrong band, and dual-band routers let you pick per network name. Congestion on the network — a background update, a cloud backup, or a streamer on another device can eat most of a typical plan; check what's running before blaming the hardware. Age — an old router or an old laptop's Wi-Fi card may be a generation or two behind, capping real-world speeds regardless of the plan; this is the one cause where the honest answer is hardware, and it's worth knowing rather than discovering.

Work the cheap fixes in order: move closer and retest (isolates distance), put the device on the faster band if it's in range, restart the router (clears stuck sessions and half-finished transfers), and pause the background bandwidth hogs on other devices. If wired and wireless both stay slow at all hours, that's the provider conversation — including the fair question of peak-time congestion on your plan, which is sometimes a plan-tier issue rather than a fault. If slowness only appears in certain rooms, stop here and follow the weak signal guide instead, because that's a coverage problem, not a speed problem.

Wi-Fi signal is weak

Weak signal shows up as low bars, slow speeds in certain rooms, and connections that hold in the kitchen but give out in the office. The physics are unkind but simple: Wi-Fi is radio, distance weakens it, and walls — concrete, brick, metal, and anything full of water — absorb it. You can't make the signal stronger, but you can stop wasting it, and a surprising share of "weak Wi-Fi" is a router sitting in the worst possible spot: a ground-floor cupboard, a TV cabinet, or behind a metal appliance.

The placement fix, in priority order: central (the signal radiates outward; a corner puts two walls between it and half your house), raised (above furniture, off the floor — a floor between floors is the worst obstacle in a home), and unobstructed (not inside a cabinet, not behind a TV). Move it for a day before judging anything else — it's the only fix in this entire hub that costs nothing. Then the band question: if the weak spot still needs to work, a 2.4 GHz network will usually reach it where 5 GHz won't, because 2.4 penetrates better at the cost of speed — a fair trade for the far room, and dual-band routers let you run both.

When placement genuinely isn't enough — big house, thick walls, the router has to live in the utility room — the honest options are an extender (place it halfway, with a good signal of its own, not inside the dead spot), a mesh system (two or more units sharing one network name — the cleanest option for most homes), or a wired connection to the problem room where the work justifies it. All of that is in the dead zones guide. One expectation to set early: weak signal is a home problem, not a provider problem — the internet arrives fine at the router; getting it to the far room is yours, and it's worth knowing before you spend a call explaining "two bars" to a support line that can't see your living room.

Wi-Fi works on one device but not another

This is the most diagnostic symptom in the whole hub: if the phone streams fine while the laptop gives up, your internet and your router have just passed their tests. The problem is in the struggling device, or in the relationship between that device and the router. Everything from here on is about that one machine.

Work it in this order. One: forget and reconnect the network on the struggling device — stale saved settings are the most common single-device cause. Two: test the struggling device on a different network — your phone's hotspot is the lab. If it works on the hotspot, the device is healthy and the problem is its relationship with your router (a saved setting gone bad, or a router-side block); if it fails on the hotspot too, the problem is inside the device. Three: follow the device's own guide — Windows, macOS, Android, or iPhone/iPad — starting with the driver check on Windows, since a failing Wi-Fi driver is the classic "works on everything else" cause. Four: the device's network settings reset, as the device-side last resort.

Two router-side corners, only if the above is clean: MAC filtering (a deliberate allowlist the device isn't on) and, on newer phones and consoles, private MAC addresses — devices now randomize their MAC per network for privacy, and a router configured for strict MAC matching can silently reject them. Both are settings with a clear reason to exist; if you find yourself here, note what's configured before changing anything, per the safe-changes rule.

How to restart a router and modem correctly

The most common home-network fix is also the most commonly done wrong. The correct sequence: switch the modem and router off together (or the combined unit), wait at least 30 seconds — long enough for the capacitors to drain and the upstream session to fully drop — then power the modem back up first and wait for its internet light to stop flashing and steady (this can take a couple of minutes), and only then power on the router. The order matters because the router registers with a modem that's already online; booting both at once occasionally leaves the router holding a half-registration that looks exactly like the problem you're trying to fix.

What to expect afterwards: two to five minutes of nothing, then lights in the normal pattern, then devices reconnecting — sometimes with a brief "no internet" while they renegotiate, which is normal and not a failed fix. Test with a real page and, if the complaint was speed, a real speed test, before calling it fixed.

One warning that prevents the most common escalation error: a restart is not a reset. The pinhole button on the back — the one that needs a paperclip — is a factory reset, and pressing it during your "restart" erases your network name, password, and admin login. If that's already happened, the factory reset guide explains what it wiped and how to rebuild. If the power cycle doesn't fix it, don't repeat it three times — move to the lights and the outage check, which is where the actual diagnosis lives.

How to forget and reconnect to a Wi-Fi network

Every device keeps a saved copy of each network it's joined — the password, the security type, the band preference. That copy goes stale: the router's settings changed, an update half-migrated it, or the network was rebuilt. "Forget" deletes the device's copy so it can start fresh from what the network actually says today. It's the cheapest fix in the hub for "won't connect," and it only touches the one device doing it — nothing on the router changes.

Where the control is (menu names shift between versions — the destination is the same: find the saved network, choose Forget/Remove): Windows — Settings → Network & internet → Wi-Fi → Manage known networks → the network → Forget. macOS — System Settings (or Preferences) → Wi-Fi → the (i) button on the network → Forget This Network. Android — Settings → Network & internet → Wi-Fi → the network's ⓘ → Forget (on some makers, long-press the network). iPhone/iPad — Settings → Wi-Fi → the ⓘ next to the network → Forget This Network.

Then reconnect from the list, typing the password fresh and deliberately — it's case-sensitive, and a saved copy that was wrong is a common reason the "forget" was needed in the first place. Test with a page load, not just the icon. If the device still won't join after a clean reconnect, the problem has moved on from saved settings: follow the device's guide in the by-device section, or if every device fails to join, flip the direction and look at the router in won't connect instead.

How to reset network settings

A network settings reset is the device-side hammer: it rebuilds the machine's entire network configuration — adapters, saved networks, IP settings, protocol caches — from scratch. It does not touch the router, the modem, or the internet; it's what you do when one device's networking has accumulated something no single setting change will remove. Use it after the cheaper steps (restart, forget & reconnect, driver work) have failed, not instead of them.

Where it lives: Windows — Settings → Network & internet → Advanced network settings → Network reset (Windows 10: Status → Network reset); the machine reboots and networking comes back clean. A lighter, command-line cousin for targeted problems is netsh winsock reset from an administrator prompt (also reboots). macOS — there's no single button; the equivalent is removing and re-adding the Wi-Fi service (System Settings → Wi-Fi → Details, then the minus button and re-add) and, for deeper wedges, creating a fresh network location to test in. Android — Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth (wording varies by maker). iPhone/iPad — Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings.

What to expect: a reboot (on Windows), a few minutes of reconfiguration, then reconnecting to your network with the real password and re-pairing Bluetooth as needed. Test the original complaint specifically — if the device that kept dropping still drops after a clean reset, the configuration wasn't the cause, and the next suspects are the driver (Windows) or the hardware itself.

How to change Wi-Fi settings safely

Most home routers expose hundreds of settings; a typical household needs to touch maybe four: the network name (SSID), the Wi-Fi password (its security key), the band setup, and occasionally the channel. The rest — DHCP ranges, QoS, advanced wireless options — exist for reasons that aren't yours, and changing them "to see if it helps" is how a five-minute problem becomes a factory-reset afternoon. The rule for everything in this section: write down (or screenshot) the setting before you change it, change one thing at a time, and test after each change.

The two changes worth doing, and how to do them without pain. Changing the Wi-Fi password (you found it on a sticky note, or a neighbor's laptop is still in your guest list): log in to the router's admin page (the address is on the router's label), note the current password, set the new one, save, and reconnect devices — do it at a moment when you can sit with a laptop, because every device will need the new password, and the one you're working from will drop mid-save. Changing the network name is the same flow with more rejoining; it's rarely worth it on its own unless the old name has become a security problem (it advertised your surname and your plan speed). Both fall under the "note it first" rule, because the undo is "type the old value back in" and the old value is only available while you remember it.

What not to touch without a specific reason: DNS overrides (leave automatic unless a guide in this hub tells you to test otherwise — see connected but no internet), the DHCP address pool, QoS, and anything labelled "advanced." If a change goes wrong, the recovery ladder is: set the value back (you noted it), restart the router, and only then — if admin access itself is what's broken — the factory reset, which is exactly the situation it's for.

How to fix Wi-Fi on Windows

Work this ladder top to bottom — each rung is cheaper than the one below, and the order is the point. One: the obvious pair — Wi-Fi actually on, Airplane mode off (Settings → Network & internet, or the quick settings flyout; the two are a switch away from each other and both get flipped by accident). Two: restart the machine — a plain restart, which clears more stuck driver state than people credit. Three: forget and reconnect the network. Four: look at the adapter itself — Device Manager → Network adapters → your Wi-Fi adapter (names include "Wi-Fi," "WLAN," "Wireless," plus a vendor like Intel, MediaTek, Qualcomm or Realtek): is it disabled (right-click → Enable), does it carry a warning triangle (driver problem → update or reinstall the driver), or is it missing entirely (→ missing adapter)? Five: the address/DNS work from connected but no internet — ipconfig /release, ipconfig /renew, ipconfig /flushdns from an administrator prompt. Six: the network reset, which rebuilds the whole stack and reboots.

Two Windows-specific notes. "No internet, secured" versus "no internet access" on the tray icon is a useful distinction: secured means it's joined but the upstream is dead (router/provider side — check another device); no-access often means the device's own IP/DNS. And if Wi-Fi wedges right after a Windows Update, that's the driver branch — the update swapped the adapter driver, and a roll back or reinstall is the direct fix rather than a network reset.

If the ladder finishes and Wi-Fi is still broken, the remaining possibilities are hardware (the adapter itself — a USB Wi-Fi adapter is a ten-minute way to confirm) or a system-level problem that wants a repair install. At that point the pre-call checklist doubles as the note to bring to a technician.

How to fix Wi-Fi on macOS

macOS's ladder: one, Airplane mode and the Wi-Fi switch itself (menu bar), plus a plain restart — on a Mac that's been up for weeks, the restart fixes more than you'd expect. Two, forget the network and rejoin: System Settings (Ventura and later; "System Preferences" on older versions) → Wi-Fi → the (i) button on the network → Forget This Network, then rejoin with the password typed fresh. Three, the move that has no equivalent on Windows: remove and re-add the Wi-Fi service — System Settings → Wi-Fi → Details (or the Advanced button) → select the Wi-Fi service, press the minus button, then add it back. It rebuilds the service's configuration, which is where a surprising number of "Mac-only" Wi-Fi wedges live. Four, a fresh network location — macOS lets you define named locations with independent network configs; creating a new one and testing in it separates a corrupted config from a real fault. (The location control has moved between macOS versions — if you can't find it, skip this rung, it's the optional one.) Five, the DNS check: Wi-Fi → Details → DNS — it should be empty (automatic) or hold your provider's addresses; a leftover manual entry from an old network is a classic "everything connects, nothing loads" cause.

Know macOS's limits: there's no one-button "network reset" the way Windows has, so remove/re-add the service plus a fresh location is the closest equivalent, and it covers most cases. If the Wi-Fi option has vanished from the menu bar entirely across reboots, that's a hardware-level symptom — test another network (a phone hotspot) to be sure, then it's Apple Support territory, where they'll run the hardware diagnostics. Don't spend a week on menu settings the hardware has stopped reporting to.

How to fix Wi-Fi on Android

Android's ladder, with one standing caveat: manufacturers reskin these menus heavily, so follow the destination, not the exact labels. One: Airplane mode on, wait ten seconds, off — the cheapest radio reset there is. Two: restart the phone. Three: forget and reconnect — Settings → Network & internet → Wi-Fi → the network's ⓘ (or long-press) → Forget, then rejoin. Four: run the phone's built-in check — most Androids have a "Internet" or network-check entry on the connected network that reports whether the network itself is the problem; it's a genuinely useful triage tool. Five: the date and time — sounds odd, but a clock that's drifted off makes Wi-Fi handshakes and encrypted connections fail in confusing ways; set it to automatic. Six: Safe Mode (long-press the power-off option, then Restart in safe mode) — if Wi-Fi behaves in Safe Mode, an installed app is interfering, and you've found the culprit class without touching any network settings.

The big hammer is Reset network settings — Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth (wording varies; some makers call it "Reset network settings" and file it elsewhere). It wipes saved Wi-Fi passwords and Bluetooth pairings — the same warning as the general reset guide applies. Do it after the six rungs, not before.

If Wi-Fi is dead across networks — the phone can't join a hotspot either — that's hardware or a deep OS fault: the phone maker's support line, not your router, is the right destination. And if only your home network is the problem while the hotspot is fine, flip the investigation to the router with router, ISP, or device? — the phone has just done a useful diagnostic for you.

How to fix Wi-Fi on iPhone and iPad

Apple's ladder is short, which is both good and frustrating. One: Airplane mode on for ten seconds, off. Two: a real restart — power off and back on, not a lock-screen-and-unlock; iOS accumulates network state that only a full restart clears. Three: forget and rejoin — Settings → Wi-Fi → the ⓘ next to the network → Forget This Network, then rejoin and type the password fresh. Four: the date and time — Settings → General → Date & Time → Set Automatically; a wrong clock breaks secure connections in exactly the "connected, nothing loads" pattern. Five: the iOS version itself — Settings → General → Software Update. Network fixes ship in updates constantly, and "update first" is the least glamorous, most effective step in this guide.

Two triage notes. If the iPhone fails on your home network but works perfectly on a hotspot, the phone is cleared and the router takes the blame — works on one device, not another has the branch logic. If the Wi-Fi toggle itself is greyed out or the option has disappeared, that's hardware-level: a restart cycle, then Apple Support — don't burn the network-reset step on a device that isn't reporting a radio at all.

How to fix Wi-Fi on smart TVs

TVs are the least graceful Wi-Fi clients in the house, and they have one fix that works on almost all of them: the long power cycle — unplug the TV from the wall for a full minute (a minute, not a blink; TVs hold network state in capacitors that a quick off/on doesn't clear), plug back in, and reconnect. The remote's "off" is standby, not off — the wall socket is the real switch. If that doesn't do it: forget the network in the TV's network settings, reconnect with the password typed from a phone (typing a long password with a TV remote is a failure source of its own), then restart the router — TV problems and router state overlap more than you'd think.

Two TV-specific gotchas other devices don't have. Band support: many older TVs connect on 2.4 GHz only. If your home network was rebuilt as 5 GHz only — or the TV keeps dropping off a dual-band network — it's not a fault, it's a frequency mismatch, and the fix is a 2.4 GHz network (or letting the router's band-steering handle it). DNS caching: some TVs cache DNS aggressively, which is why "connected, nothing loads" on a TV is often cured by the unplug cycle plus a router restart rather than anything in the TV's menus. Most TVs also have a network test or diagnostics page — run it; it distinguishes "can't reach the router" from "can't reach the internet" with one button.

The escalation line: the TV has a network reset (in its settings, usually under network/general) that clears its network config without erasing apps and accounts — use that, not the TV's full factory reset, which wipes everything including your streaming logins. If the TV's Wi-Fi is dead across networks (it fails on a hotspot too), the TV's radio is the suspect and the manufacturer's support line is the right call.

How to fix Wi-Fi on gaming consoles

Consoles are actually the easiest Wi-Fi patients in the house, because both PlayStation and Xbox ship a built-in network test (Settings → Network → Test Internet Connection) that reports exactly where the chain breaks: console-to-router, or router-to-internet. Run it first; it turns a vague "online's acting up" into a specific hop, and the right half of this hub handles each hop. Then the ladder: restart the console and the router (router first, per that guide), check the console's system software is current — network bugs get fixed in system updates more often than in anything you can configure, and a console that's two updates behind is often a console with a known network bug. If the built-in test points at DNS, leave the DNS setting on automatic and resolve the upstream problem instead (per connected but no internet) rather than typing manual resolvers into a console that will forget them by the next update.

The wired test is the great equalizer: every console can run over Ethernet, and a console that works wired but not on Wi-Fi has just told you the internet is fine and the problem is the wireless hop — distance from the router (consoles in the far corner are a coverage story, not a console story; see weak signal), the 5 GHz/2.4 GHz question (some consoles prefer one band and let you pick), or the console's Wi-Fi module. Note one modern wrinkle: some newer devices randomize their MAC address per network ("private address" on phones, a similar setting on some consoles) — if your router uses strict MAC filtering, a console presenting a randomized MAC will be rejected, and that's the one router change with a clear reason to exist in this scenario.

When to stop configuring: the console fails on Wi-Fi at every network it tries (including a phone hotspot), while wired works — that's the console's Wi-Fi hardware, and it's the manufacturer's repair line, not another settings pass. For multiplayer, also remember the fair expectations: a perfectly healthy home network can still see high ping to a distant game server, and that's the internet doing what the internet does, not a fault in your setup.

Router has no internet light

Start with the honest caveat: light colors and labels are model-specific, so your manual (or the sticker on the unit) has the exact legend. But most home equipment follows a shared grammar — a power light, an internet/uplink light (sometimes labelled "Internet," "WAN," "Online," or "DSL"), a Wi-Fi light, and per-port activity lights — and the internet light is the one that tells you whether the router is actually receiving anything from upstream. Off or red on that light, with everything else normal, is the clearest statement a router can make: I am powered, I am running, and I have no internet to share.

When the internet light is the problem, the physical check takes two minutes: the cable between modem and router (Ethernet — seated at both ends, the right one; some setups use a second cable people unplug "temporarily"), and the modem's own lights (a modem with no line light is a line story, not a router story). Then the power cycle, modem first, giving the modem its full two minutes before the router comes up. If the light comes back steady, retest with a real page. If it stays dark or red after all of that, with no reported outage, the line itself is the suspect — and the pre-call checklist turns the light state into the first sentence of your call: "Internet light red after a full power cycle, neighbors online."

Router vs. modem — what's the difference

Two jobs, two boxes (or one box doing both). The modem is the translator: it converts the signal coming in from your provider — the cable, the phone line, the fiber — into something your home network can use. The router is the distributor: it takes that one internet connection and shares it across your home, as Wi-Fi and as the Ethernet ports in its back. Everything in this hub that says "restart the modem first" is about this division of labor — the router depends on the modem, not the other way round.

Then the complication that confuses everyone: most homes have one combined unit labelled "gateway" or "modem router," usually rented from the provider, doing both jobs in one box. That's fine — just treat it as the modem-first step: power-cycle the one box, wait for its lights, done. You can tell the difference by what's plugged in: a box with a coaxial (cable) or phone-style line coming straight from the wall is doing the modem job; a box that only receives an Ethernet cable from somewhere else is a router.

Why the distinction matters for troubleshooting: it tells you which lights to read (the modem's line light is the upstream story), which order to power on in, and — practically important — which box belongs to whom. Provider-supplied equipment is usually theirs to configure and replace; factory-resetting a rented gateway without the provider can leave your account unprovisioned, which is exactly the kind of thing the factory reset guide warns about. Your own router, your rules — with the write-it-down caveat from changing settings safely.

How to set up a new router

Before opening the box, gather the two things setups fail without: an Ethernet cable (keep your setup laptop wired to the router throughout — if you're setting up over the router's own Wi-Fi and get the password wrong, you're doing it twice), and the old router's setup details or your provider's account sheet. Some plans — certain fiber and DSL setups in particular — carry their own connection credentials (often called PPPoE) that the new router will ask for; if the old unit is a provider-supplied gateway, that information may live with the provider, and a five-minute call before setup saves an evening of it. Check your plan type first; most plain cable plans need nothing of the sort.

The setup itself: connect the modem's Ethernet output to the router's WAN/Internet port (the one that's a different color or physically separated — on most routers it's labelled), power the router up, and join its default network — the name and password are on a sticker on the unit, and yes, they're meant to be changed. Follow the router's setup wizard (its own page, or the manufacturer's app if one's bundled), and when it asks, set your own network name and a strong Wi-Fi password — the wizard's default of "keep the name and password from the old router" is the fastest path to a working house, while a fresh name is the fastest path to a clean one. Finish by testing on two devices: a laptop over Wi-Fi and something on a different band, ideally.

If the wizard dead-ends, the usual suspects are the PPPoE question (provider credentials — call with your account number), the WAN-port/cable swap, and, on provider-managed plans, the fact that the plan may be provisioned to the old gateway's serial number, in which case the provider has a re-provisioning step that's a phone call, not a settings page. The lights guide is the diagnostic reference for this whole section: if the internet light tells you where the setup is actually stuck, you're halfway to the fix.

How to factory reset a router

Say it plainly, because it's the step that scares people for good reason: a factory reset erases everything on the router. Network name, Wi-Fi password, admin login, custom settings, any provider-specific configuration living on the unit — all of it returns to the box state, and every device in the house reconnects from scratch. It is not a stronger restart. A power cycle keeps your settings and clears temporary state; a factory reset clears the settings themselves. If you haven't ruled out the power cycle, do that first — a reset as step one is how a ten-minute problem becomes a two-hour setup.

The legitimate reasons to do it: you've lost admin access (forgotten the login, and the label default no longer works); a misconfiguration persists after a normal restart and you can't find which setting is the culprit; or you're handing the unit back or on and want it clean. To perform it: the small pinhole button on the unit (labelled reset), a paperclip or similar, power on, hold for about ten seconds — the lights will cycle, and the exact duration varies by model, so the manual wins if you have it — release, and wait for a full reboot. The router now behaves like it did on the day it was unboxed: default network on the sticker, default login, no memory of your house.

After: set it up properly, per the new router setup guide, and — one scenario worth naming — if your plan's configuration lived on this router (the PPPoE case), you'll need the provider's credentials or app to bring the internet back, which is the moment to have the account number to hand. There's also a softer variant if you still have admin access: a "restore defaults" or "factory reset settings" option in the admin page, which does the same erasure without the paperclip — same consequences, easier button, equally final. In every case the rule from changing settings safely applies in reverse: you now own a blank slate, and the setup notes you wrote down are worth their weight in gold.

How to update or reinstall a Wi-Fi driver

The Wi-Fi driver is the piece of software that translates between Windows and the radio card; when it degrades — after an update, after a driver conflict, or just from age — the symptoms look like network faults: disconnecting, slow connections, the adapter warning in Device Manager, or Wi-Fi that simply stops appearing. The rule for sources, stated once and meant seriously: Windows Update first, then the manufacturer — never a random "driver updater" program. The updater genre is where good machines acquire bad drivers, and it has no place in this procedure.

The procedure. Open Device Manager (right-click the Start button → Device Manager) → Network adapters → find the Wi-Fi adapter — names include "Wi-Fi," "WLAN," "Wireless," plus a vendor: Intel, MediaTek, Qualcomm, Realtek, Broadcom. Right-click → Update driver → "Search automatically" — this pulls the current driver from Windows Update if a newer one exists. If the manufacturer's site has a newer one (the support page for your laptop model, or the adapter vendor for a desktop card), install that package instead and let it replace. Restart either way — driver changes complete on reboot, not on close. Expect: after the restart, the adapter re-registers, saved networks reconnect, and the original complaint (dropping, slowness, the warning icon) is the thing to retest specifically.

The branch that makes driver work worth doing at all: when a recent update is what broke things. If Wi-Fi was fine and died after a Windows Update or a driver install, the direct move is a rollback — Device Manager → the adapter → Properties → Driver tab → Roll Back Driver (available only while the previous version is still on disk). Roll back first, reinstall second, update third — in that order, because the update path can only move forward while the rollback path can take you home. If the adapter is missing rather than just misbehaving, stop here and follow the missing adapter guide, which handles the "the radio stopped reporting" case end to end. And if driver work leaves the problem intact, the next rung is the network reset, which rebuilds the software around the driver rather than the driver itself.

How to fix a missing Wi-Fi adapter

The Wi-Fi option is gone, or the adapter has vanished from Device Manager. The causes run from banal to hardware, and the order of checks is the order of likelihood. One: restart. A hung driver reports as a missing device more often than it should, and a reboot costs two minutes against a diagnosis that otherwise assumes the worst. Two: Device Manager, read carefully. Network adapters → is the adapter there with a warning (a yellow triangle — that's a driver fault, and the driver guide is the fix)? Or absent entirely (below)? Also check the View menu → "Show hidden devices" — a ghosted entry is a driver that uninstalled itself, and removing it (from the hidden list) then choosing "Scan for hardware changes" is a genuine reinstall cycle. Three: the radio switches. Laptops have made these rare, but some still carry a physical Wi-Fi switch or a keyboard shortcut (the F-row, often marked with an antenna) that disables the radio at the hardware level; and in the BIOS/UEFI, wireless can be disabled — if it was ever toggled off, Windows sees no adapter at all, which is exactly this symptom.

When it's not a switch: four, the power management setting — Device Manager → adapter → Power Management → uncheck "Allow the computer to turn off this device" (it's the setting behind the subtle version of this problem: the adapter vanishes overnight and returns after a restart). Five, the software side — netsh winsock reset and sfc /scannow from an administrator prompt, each followed by a reboot: the first rebuilds the network software stack, the second repairs corrupted system files that can include network components. Both are safe and repair rather than delete, and between them they clear a surprising share of "adapter gone" cases that survive the first three checks. Six, the Windows Update branch — a feature update occasionally ships a broken adapter driver; checking Windows Update for optional driver updates, or temporarily rolling the update back, is the move when the disappearance lines up with an update.

And the honest end of the ladder: if the adapter is gone across restarts, BIOS, driver reinstalls, and system repairs — and the machine is old enough to have soldered or card-based Wi-Fi — the radio hardware has likely failed. The confirmation test is a USB Wi-Fi adapter: if an external radio works immediately, the internal one is the confirmed culprit, and the decision is repair (a technician; a card swap on desktops and many laptops) versus living with the USB dongle versus wired. That's a hardware conversation, not a settings one — and knowing which side of that line you're on is the entire point of the checks above. A technician will want the note from the checklist: what was tried, in order, is what separates a fast diagnosis from a second one.

How to improve Wi-Fi coverage at home

Coverage problems are placement problems before they are equipment problems, and the placement fix is free. Wi-Fi radiates in all directions and decays with distance and every wall it crosses — concrete, brick, metal, and coated glass are the worst offenders — so a router in a ground-floor TV cabinet is starting each day about as badly as a router can start. The target position: central to the rooms that use it, raised (a shelf, a high wall mount, the top of a bookcase), and in the open — not in a cabinet, not behind a TV, not on the floor. Move it for 24 hours and retest the rooms that complained before judging any other option; in a typical home this single change is the difference between "the Wi-Fi's weak" and "solved."

Then the settings that actually matter, and only those. The band: modern routers run 2.4 GHz and 5 GHz (Wi-Fi 6/6E add 6 GHz) — either as two separate networks or blended under one name. 5 reaches less far but carries much more; 2.4 reaches further and shares the air with the neighborhood. If your router separates the bands, a far-room device on the 2.4 network is usually the right choice, and a near-room device on 5. The channel: leave it on automatic unless you've measured a reason to change it — modern routers' auto-selection handles most interference, and manually picking a channel without a measurement is how people create the congestion they're trying to fix (and per the safe-changes rule, note whatever you do change). Everything else on the advanced wireless pages — transmit power, channel width, the named modes — is for problems with a measured cause, not for "make it better."

When placement genuinely can't reach — the router must live where the line enters, the house is big, the walls are thick — the honest options, in rough order of cost: a Wi-Fi extender, placed halfway between the router and the dead area with a good signal of its own (not inside the dead spot, where it has nothing to repeat); a mesh system, two or three units sharing one network name and handing devices between them, which is the clean answer for most larger homes; powerline adapters, which carry the network over your electrical wiring to a second Wi-Fi point — effective where the wiring is good, unpredictable where it isn't, worth knowing both; and a plain Ethernet run to the problem room, which is the engineering-correct answer for the room that must never drop. One expectation to keep: none of this is the provider's concern. The internet arrives at your router intact; what happens between the router and the far room is entirely home-side, and it's worth knowing before a support call spends ten minutes explaining that "signal strength" isn't on their dashboards.

How to fix Wi-Fi dead zones

A dead zone is specific: a room, a floor, a hallway where the signal dies. The first move costs nothing and changes every later decision — map it. Walk the house with a phone, note where the signal drops: one room or an entire floor? The upstairs or the garden? One corner or the far wall of every room? The map decides the fix, because "one corner" and "the whole second floor" are different purchases. If the map shows a single weak corner and everything else is strong, you likely don't need to buy anything at all — the coverage guide's placement and band advice may close the gap.

The fixes, in order of escalation. Relocate the router — if the dead zone exists because the router lives in the opposite corner of the house, moving it is the fix, full stop. Switch the distant device to 2.4 GHz — the band that trades speed for reach; a dead zone that's "almost alive" often becomes workable with the slower band and no equipment. A single extender, placed correctly — the classic mistake is putting it in the dead zone itself, where it repeats a signal it can barely hear; it belongs halfway, in a spot with a solid signal, aimed at the dead area. A mesh system — for whole floors and large homes, two or three nodes sharing one network name, with the extra node placed to cover the dead zone; it's the option most homes land on once the free options are exhausted. A wired solution — an Ethernet run (or powerline, where the wiring cooperates) feeding a small access point in the problem room, for the room where the work must simply not drop: video calls, the office, the console.

Two checks that keep dead-zone fixes honest. Retest where it was dead — a speed test in the living room after installing a node tells you nothing; the test is in the room that failed, on the device that failed, doing the thing it failed at. And rule out the non-coverage causes first: a "dead zone" that's really a 5 GHz distance limit is fixed by a band change, and a dead zone that appeared after a router swap may be a router configured for a narrower channel than its predecessor. The weak signal guide covers that diagnostic half; this one is for when the map says the signal genuinely isn't arriving.