DEV Community: FixsFlow Team

Wi-Fi Connected but No Internet? A Beginner's Step-by-Step Fix Guide

FixsFlow Team — Wed, 14 Oct 2026 07:17:13 +0000

You've seen it before: the Wi-Fi icon looks perfectly happy — full bars, "Connected" — yet nothing loads. No websites, no videos, no messages. It's one of the most frustrating problems in home computing because everything looks fine.

The good news: this error almost always has a boring, fixable cause. Work through the steps below in order, and test your connection after each one. You don't need to be technical — just patient.

Step 1: Find out if it's your device or your whole network

Before touching any settings, grab another device — your phone, a tablet, anything — and try loading a website on the same Wi-Fi.

If no device can get online, the problem is your router, modem, or internet provider. Skip ahead to the router steps.
If only one device fails, the problem lives on that device, and the steps below will walk you through fixing it.

This single check saves you from "fixing" the wrong thing.

Step 2: Give your router and modem a proper reboot

This really does fix a surprising number of cases. Routers run for months without a restart, and their memory fills up with stale connections.

Unplug the power cable from both your router and your modem (the box your internet line plugs into).
Wait a full 60 seconds. Don't shortcut this — the hardware needs time to fully discharge.
Plug the modem back in first and wait until its lights settle (usually 1–2 minutes).
Plug the router back in and wait another minute.
Try loading a website again.

Step 3: Forget the network and reconnect from scratch

Saved Wi-Fi profiles can get corrupted — especially after router firmware updates or password changes. Forgetting the network forces your device to build a fresh connection.

On Windows:

Open Settings → Network & Internet → Wi-Fi.
Click Manage known networks.
Select your network and click Forget.
Reconnect by selecting the network again and typing the password carefully.

On a phone, the same option lives under the Wi-Fi settings for the network (usually "Forget this network").

Step 4: Check the easy stuff first

It sounds silly, but these catch people every day:

Make sure Airplane Mode is off.
Toggle Wi-Fi off and back on.
Check that your system date and time are correct — a wrong clock breaks secure (HTTPS) connections because certificates can't be validated.
If you're on a laptop, check for a physical Wi-Fi switch or a function-key (Fn) toggle.

Step 5: Reset the network stack on your device

When a device connects to Wi-Fi, it quietly negotiates three things in the background: an IP address (DHCP), name resolution (DNS), and a route out to the internet (the gateway). If any of these stall, you get the classic "connected, no internet" symptom — and normal browsing gives you zero clues about which one failed.

On Windows, the simplest fix is a network reset:

Open Settings → Network & Internet → Advanced network settings.
Click Network reset, then Reset now.
Restart your computer when prompted. You'll need to re-enter your Wi-Fi password afterward.

If you'd rather try a lighter touch first, you can renew the connection manually. Open Command Prompt as administrator and run:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

If you want to understand what's actually happening under the hood, this step-by-step guide walks through each fix with the exact settings to check.

Step 6: Switch to a public DNS server

Sometimes your provider's DNS servers are the bottleneck. Switching to a well-known public DNS is quick and reversible:

Open Settings → Network & Internet → Wi-Fi, click your connection, then Edit next to DNS server assignment.
Switch to Manual, enable IPv4, and enter 1.1.1.1 as preferred and 1.0.0.1 as alternate (or 8.8.8.8 and 8.8.4.4).
Save and test.

Step 7: Update or reinstall your Wi-Fi driver (Windows)

A buggy or outdated wireless driver can connect to the router yet fail to pass traffic:

Press Windows + X and open Device Manager.
Expand Network adapters, right-click your Wi-Fi adapter, and choose Update driver → Search automatically.
If that doesn't help, choose Uninstall device, restart your PC, and Windows will reinstall a fresh driver automatically.

Step 8: Know when it's your internet provider

Call your ISP (or check their outage page from your phone's mobile data) if:

The modem's "Internet" or "WAN" light is red or off after the reboot.
Every device fails, even with a cable plugged directly into the modem.
The problem started right after a storm or a provider maintenance window.

Wrapping up

"Connected, no internet" feels mysterious, but it's almost always one of these: a tired router, a stale network profile, a stalled DHCP/DNS handshake, or a driver hiccup. Start with the router reboot, work your way down the list, and resist the urge to change five settings at once — testing after each step tells you exactly what fixed it.

My client's card expired — and so did their domain

FixsFlow Team — Tue, 13 Oct 2026 07:00:14 +0000

A friend runs a small dental clinic. Last year her website went dark on a Tuesday morning and she called me in a panic. The domain had expired. Not because she forgot to pay for it — she had auto-renew switched on for years. The card on file had expired two months earlier, the renewal charge bounced, and the reminder emails went to an old Gmail she hadn't opened since 2022.

By the time we noticed, the domain was already in the redemption period. Recovering it cost her $180 on top of the renewal fee, plus three days of a dead website and a week of missed appointment emails.

That experience changed how I think about auto-renew. It's genuinely useful — I'd never tell anyone to turn it off — but it's not a safety net on its own. The single point of failure is almost always the payment method or the contact email, and both of those go stale silently.

What actually works is a second, independent pair of eyes on your expiry dates. I wrote up the full trade-offs here — when auto-renew is great and the three specific cases where it quietly fails: auto-renew's pros and cons.

These days I keep every domain I manage in a monitor that pings me well before anything expires. DomainPings handles that for me, and the free tier covers the handful of domains I look after. One alert, thirty seconds to fix the card, crisis avoided.

Auto-renew is a good servant and a terrible master. Trust it, but verify it — with something that doesn't depend on the same card and the same inbox.

USB Device Not Recognized on Windows? 9 Fixes That Actually Work

FixsFlow Team — Mon, 12 Oct 2026 07:23:19 +0000

That "USB device not recognized" pop-up is one of the most annoying Windows errors because it tells you nothing about the actual cause. Before you assume your drive is dead, work through these fixes — in my experience, fix #3 alone solves it for most people.

1. Try a different port (and skip the hub)
Front-panel ports and cheap USB hubs cause half of these errors. Plug the device directly into a rear motherboard port.

2. Restart with the device plugged in
Unplug it, shut down fully (not sleep), plug it back in, then boot. This forces Windows to re-enumerate the device.

3. Reinstall the USB controllers
Open Device Manager, expand "Universal Serial Bus controllers", right-click each "USB Root Hub" and "Generic USB Hub", choose Uninstall device, then restart. Windows reinstalls them automatically. This is the fix that works most often.

4. Disable USB selective suspend
Control Panel > Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend > set to Disabled. This stops Windows from cutting power to "idle" ports.

5. Update the chipset drivers
Generic Windows drivers misidentify controllers. Grab the chipset driver from your motherboard or laptop maker's site (Intel, AMD, or the OEM).

6. Check for the yellow warning in Device Manager
If the device shows as "Unknown USB Device" with a yellow triangle, right-click it > Update driver > Search automatically. If that fails, note the error code — code 43 often means a hardware handshake failure, not a dead device.

7. Test on another computer
If it fails on two machines with different cables, the device itself is likely the problem — not Windows.

8. Run the hardware troubleshooter
Settings > System > Troubleshoot > Other troubleshooters, or press Win+R and run: msdt.exe -id DeviceDiagnostic

9. Check USB settings in BIOS
On some desktops, USB legacy support or xHCI handoff settings cause detection flakiness. If you recently changed BIOS settings, reset to defaults.

I wrote a longer step-by-step version of this with all 10 methods in one place here: Fix 'USB Device Not Recognized' Error: 10 Solutions

What fixed it for you? The controller reinstall (fix #3) is my usual winner.

How to Fix Windows Update Error 0x800F081F (4 Methods That Actually Work)

FixsFlow Team — Fri, 09 Oct 2026 10:53:17 +0000

Windows Update error 0x800F081F usually means Windows can't find the source files it needs to install an update or .NET Framework component. The full error reads "the source files could not be found." Here are the fixes that resolve it most often:

1. Run the Windows Update troubleshooter first. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It clears the most common update-service glitches.

2. Reset the update components manually. Open Command Prompt as administrator and stop the update services (wuauserv, cryptSvc, bits, msiserver), rename the SoftwareDistribution and Catroot2 folders, then restart the services. This forces Windows to rebuild the update cache from scratch.

3. Run DISM and SFC. DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow repairs the component store that 0x800F081F is complaining about. If DISM fails, it usually needs an install-media source — that's covered in the full guide.

4. Install .NET Framework manually. If the error appeared during a .NET install, download the offline installer from Microsoft and install it directly instead of going through Windows Update.

For more Windows Update troubleshooting walkthroughs, FixsFlow has step-by-step guides — for example this one on fixing the Windows Update service when it fails to download patches: https://fixsflow.com/windows/dell-pc-windows-10-pro-windows-3

That guide is part of a whole error-code database on the site if you hit a different code next time.