How to Fix a Wi-Fi Connection That Keeps Dropping

There are two answers to this: the one that sounds good in a blog post, and the one that holds up when you actually sit down to do it. This guide is about the second one. A working diagnostic sequence for a Wi-Fi connection that drops randomly — from the free fixes to the last resort.

The best time to think through this was probably yesterday. The second-best time is right now, before another decision locks you in. That’s why we put together this guide on “how to fix a wi-fi connection that keeps dropping” — to give you the version we wish we’d had when we first worked through it ourselves.

This guide is for anyone who wants a practical answer, not a marketing tour. No prior expertise required — we explain the terms as we go — but we won’t insult your intelligence either. Read the key takeaways for the two-minute version, then dive into the sections that matter to your setup. The FAQ at the end covers the follow-up questions we hear most often.

Key takeaways

Here’s the short version, if you’re skimming:

Restart the router, then the modem — one of the parts you’ll want to pay closest attention to as you work through this guide.
Move to 5GHz where possible — one of the parts you’ll want to pay closest attention to as you work through this guide.
Update the router firmware — one of the parts you’ll want to pay closest attention to as you work through this guide.
When to blame the ISP — one of the parts you’ll want to pay closest attention to as you work through this guide.
The order of the sections matters — later steps often assume earlier ones are done.
The mistakes section near the end is worth reading first if you’ve already tried the basics without success.

Why this matters in troubleshooting today

The troubleshooting landscape moves fast, and the advice you’ll find in older articles frequently no longer applies. We keep this guide current because the underlying question — captured neatly by the title, “How to Fix a Wi-Fi Connection That Keeps Dropping” — is one people search for month after month, and the correct answer keeps quietly shifting as tools, products, and best practices evolve.

The good news is that once you’ve read this through, you’ll have a mental model that adapts even when a specific version or product changes. Concrete steps are useful, and we’ll give you plenty of them; but the framing behind those steps is what actually lasts. That’s the framing we’ve tried to build into every section of this guide.

We’ve also been careful to flag where the advice depends on your specific situation — the setup you already have, the budget you’re working with, the trade-offs you personally care about most. There is very little “one right answer” in troubleshooting; there are many good answers, and the goal here is to help you find the one that fits you.

Restart the router, then the modem

Unplug, wait 30 seconds, plug back in. Router first, modem second. This fixes about half of intermittent Wi-Fi issues.

This is the part of the process where a little care compounds into a much smoother experience later. Give it the attention it deserves now and the rest of the guide will feel like it’s flowing downhill.

If you take nothing else from this section, take the framing: the effort here is small, and the payoff shows up every time you use the setup afterwards. Investments that repay themselves daily are the kind worth making early and never revisiting except to confirm they still work.

The best test of whether this is set up correctly is boring: nothing weird happens, and you stop thinking about it. Excitement in this area is almost always a warning sign, not a feature.

Move to 5GHz where possible

The 2.4GHz band is crowded by microwaves, baby monitors, and neighbors’ networks. 5GHz is faster and much more stable at short range.

It’s worth taking a beat here, because this is where a lot of otherwise-solid setups quietly go wrong. The mistake is rarely dramatic — it’s a small default left unchanged, a checkbox unticked, a step deferred until later that later never comes.

The reason experienced users treat this as non-negotiable isn’t dogma — it’s that they’ve all been burned once and don’t intend to be burned twice. Learning from other people’s mistakes is cheaper than making your own, and this is one of the cheapest lessons on the whole subject.

If you’re troubleshooting an existing setup rather than building a new one, this is where you should look first. In our reader mail, nine out of ten “why isn’t this working” questions trace back to a decision made — or skipped — in this exact area.

Update the router firmware

Firmware updates fix real bugs. Log into the router admin page and check for updates once every couple months.

If you’re skimming, don’t skim this bit. The rest of the article assumes you’ve made a considered choice here, and skipping it tends to be the reason later steps produce surprising results.

Most people we hear from who ran into problems in this area skipped one of the specifics above. It looks small on paper; it’s the difference in practice. Once you’ve done it the correct way twice, the correct way becomes the default and the shortcut stops feeling attractive at all.

Take a screenshot or a note of your final settings here. Six months from now, when you need to reproduce the setup on a new device, you’ll be very glad you did.

When to blame the ISP

If a wired connection also drops, it’s the ISP, not your Wi-Fi. Time to call — with dates and times of outages ready.

This is a step where the correct default is different from the obvious one — worth pausing on before you continue. The obvious choice will work; the correct one will keep working when the obvious one starts to show its limits.

The temptation is to skip this step when you’re in a hurry — which is exactly when it costs the most. Two minutes here saves an evening later, and the discipline of doing it every time is what turns an occasional shortcut into a reliable habit you no longer have to think about.

In our experience, readers who work through this section carefully rarely have to come back to it — the setup holds up over time, survives updates, and continues to make sense even as the surrounding tools evolve. That’s the standard worth aiming for.

What’s changed recently — and what hasn’t

Every twelve months brings a wave of new features, new products, and new opinions in this corner of technology. Some of it genuinely changes the right answer; a lot of it is noise dressed up as news. Part of our job on this guide is separating the two so you don’t have to.

The genuinely new: the tooling around wifi has matured significantly in the past year, cross-platform support has improved almost everywhere, and defaults are — for the most part — finally set to sensible values out of the box. That last point in particular means new users have a much easier time than they did a few years ago.

What hasn’t changed: the fundamentals. The habits and decisions that separated a solid setup from a fragile one three years ago separate them today. Attention to detail, willingness to spend a few minutes on setup, and a healthy skepticism about advice that sounds too good to be true — those never go out of style, and they matter here as much as anywhere else in technology.

Common mistakes to avoid

A few pitfalls come up repeatedly when readers tell us how they approached how to fix a wi-fi connection that keeps dropping. Watching for these saves more time than any single tip we could offer, and they’re worth reviewing even if you’re an experienced hand — the small ones are the ones that catch experienced people, precisely because they look too obvious to be worth checking.

Jumping to the nuclear option first

Factory resets, format-and-reinstall, and driver rollbacks are last resorts. Most problems fix with a targeted change in under ten minutes; try those first. If any of that sounds familiar from your own past attempts, you’re in good company — it’s the most common failure mode we see, and it’s fixable in a single sitting.

Skipping the backup

Whatever fix you try, back up first. “It’ll be fine” is the most expensive sentence in troubleshooting. It’s the kind of thing that feels like a small compromise at the time and looks obvious in hindsight — the whole point of listing it here is to give you the hindsight up front.

Ignoring the error message

The exact wording of an error is the shortest path to a solution. Copy it into a search engine verbatim before doing anything else. The fix, in almost every case, is less work than the fix for the problem it causes when left unaddressed.

Changing multiple things at once

If you change three settings and the problem goes away, you don’t know what fixed it — and you can’t fix it again next time. Change one thing at a time. None of this is unique to any one product or platform; it’s a pattern of behavior that shows up wherever this kind of decision has to be made.

Pro tips from our editors

These are the habits that separate a workable setup from one that keeps paying you back years later. None require special software or expensive gear — just a little intention.

Restart before you diagnose. A full power-cycle solves an embarrassing percentage of problems. Give it that chance before spending an hour on root cause.
Note what changed recently. New update, new driver, new hardware, new app. The last change is almost always the culprit for a new problem.
Screenshot before you fix. Future-you will thank you. A screenshot of a broken settings screen is worth ten minutes of trying to remember what it looked like.
Isolate the variable. Test with a different cable, a different network, a different account. Isolating the failure narrows the search dramatically.
Search the exact error text in quotes. Search engines love context. Quoting the error narrows results to people with the same problem instead of the general category of the problem.

Tools and resources worth knowing about

A few tools we lean on for this kind of work — none are strictly required, but all are worth knowing about:

A reliable notes app — Whether it’s Obsidian, Notion, or Apple Notes, keeping a written record of settings and steps pays off the moment something goes wrong.
A trusted password manager — 1Password and Bitwarden are the two we recommend most. Both are dramatically better than reusing anything.
A backup routine — Cloud backup for convenience (Backblaze, iCloud, OneDrive), plus one local backup you can grab if the internet goes down.
A saved bookmarks folder — Screenshot the settings screens or bookmark the docs pages you’ll want again. Small effort, big future payoff.

Frequently asked questions

How do I know when to call support?

If you’ve tried the free fixes (restart, update, reinstall) and the problem persists on a different account or fresh install, it’s likely hardware or an account-side issue that support can resolve faster than you can.

Should I factory reset?

Only as a last resort, and only after a verified backup. A factory reset trades a fixable problem for a guaranteed weekend of reconfiguration.

Is it worth paying for a repair on old hardware?

Rule of thumb: if the repair costs more than 50% of the used replacement price, replace it. Below that, the repair usually makes sense — especially if your data and setup are already there.

The bottom line

There isn’t a single right way to approach this, but the approach in this guide has worked reliably for our editors and readers for years.

The goal wasn’t to give you an exhaustive reference — those exist and they’re a poor way to learn. The goal was to give you the shape of the problem, a working set of steps, and enough context that you can adapt the advice when your specific situation doesn’t match ours exactly. If we’ve done that, you’re set.

If you’d like to go deeper on Troubleshooting, we publish new guides in this category regularly — browse the archive to find the ones most relevant to your setup. Related articles are linked at the bottom of every post, and our search bar is a good way to jump straight to a topic if you already know what you’re after.

Have a question this article didn’t answer, a scenario we missed, or a correction to suggest? Drop us a line via the contact page. Reader questions genuinely shape what we write next — a fair number of our most-read guides started life as a single reader email that made us realize we hadn’t covered something important. Yours could easily be the next.

Thanks for reading, and good luck with your next step on “how to fix a wi-fi connection that keeps dropping”. If this guide helped, the single best way to support the site is to share it with someone who’d find it useful — a link in a group chat, a bookmark, a mention on your favorite forum. That’s how HighTechBee grows, one considered recommendation at a time.