Practical computer help for real-world problems.
Menu

Internet & Network / Wi-Fi

Home Wi-Fi Troubleshooting Flowchart

Quick answer

Start with one question: does another device on the same Wi-Fi work? If no device works, check router/ISP. If other devices work, this PC is the focus. Then decide whether Windows is disconnected, connected with no internet, using a 169.254 address, failing DNS, blocked by VPN/proxy, or simply too far from the router.

Practical PC editorial teamUpdated November 2, 202615 min readBeginner-friendlyAbout 15 to 45 minutes

Quick diagnosis

If several of these match what you see, you are in the right guide.

  • Wi-Fi is connected but there is no internet
  • Some devices work while one Windows PC does not
  • The connection drops, slows down, or fails after sleep
  • You need to decide whether to restart the router, fix Windows, or check DNS

Possible causes

  • Router or ISP outage
  • Windows adapter, DHCP, DNS, VPN, or proxy problem
  • Weak Wi-Fi signal or interference
  • A sleep/wake power-management issue
  • A site-specific outage being mistaken for Wi-Fi failure

What you need

  • A second device if available
  • Router or modem access
  • Settings
  • Command Prompt

What this problem usually means

Most Wi-Fi mistakes happen because people skip the isolation step. A router outage, a single Windows adapter problem, a DNS failure, and weak signal can all look like "the internet is broken." The fix changes once you know which branch you are on.

Before you start

  • Test the exact same website on a phone using the same Wi-Fi, not mobile data.
  • If Ethernet is available, plug one device into the router. That separates wireless signal from internet service.
  • Do not run network reset until you know the problem is local to the Windows PC.
  • Use the Internet Connection Troubleshooter if you prefer a guided version.

Quick fixes

1. Flowchart overview

  1. Another device on the same Wi-Fi works? If no, router/ISP branch.
  2. Ethernet works from the router? If yes, wireless signal/router Wi-Fi branch. If no, modem/ISP branch.
  3. Only this Windows PC fails? Check Wi-Fi adapter, IP address, DNS, VPN, and proxy.
  4. IP starts with 169.254? DHCP failed; router did not lease an address.
  5. IP looks normal but websites fail by name? DNS branch.
  6. Browser works but apps do not? Proxy, VPN, firewall, or WinHTTP branch.
  7. Only far rooms fail? Signal/interference branch.

2. Router restart only when the evidence points there

Restart the router when multiple devices fail, the router admin page is unreachable from multiple devices, or Ethernet from the router also fails. If only one PC is affected, restart is harmless but usually not the real fix.

Step-by-step troubleshooting

Device problem branch

Router or ISP branch

  • No devices work on Wi-Fi and Ethernet does not work either: restart modem/router and check provider outage status.
  • Ethernet works but Wi-Fi does not: router wireless settings, signal, interference, or a bad access point are likely.
  • Do not change Windows DNS on one PC to fix a whole-home outage.

IP address and DHCP branch

ipconfig
What this does
Shows the current IP address for Wi-Fi and Ethernet adapters.
Why run it
A 169.254 address means Windows made its own local address because it did not get one from the router.
What you should see
A normal home IP often starts with 192.168.x.x or 10.x.x.x. 169.254.x.x points to DHCP failure.
If it fails
Open Command Prompt or Terminal, then type ipconfig exactly. If no Wi-Fi adapter appears, use the missing adapter guide.

For Ethernet APIPA or unidentified network, use Ethernet unidentified network. For Wi-Fi that is connected but cannot reach the internet, use the Wi-Fi no-internet guide.

DNS, VPN, and proxy branch

Signal and sleep branch

Wi-Fi isolation flow

Choose an answer. The next question appears below, no account or download required.

Does another device work on the same Wi-Fi?
Does Ethernet from the router work?

The internet service probably works. Focus on router Wi-Fi signal/settings or wireless interference.

Router, modem, or ISP branch. Restart network equipment and check outage status.

What does the Windows PC show?

Use the Wi-Fi adapter missing guide.

Use Wi-Fi connected but no internet. Check IP, DNS, VPN, and proxy.

Use Wi-Fi keeps disconnecting, or sleep-disconnect if it happens after wake.

Check this first. It is the fastest way to avoid fixing the wrong thing.

How to know the problem is fixed

  1. Open two previously failing websites.
  2. Confirm another app, such as Store or mail, can connect if it failed before.
  3. If signal was the issue, test in the room where the problem happened, not only beside the router.

If the problem continues

If every branch seems to fail, document which devices work, whether Ethernet works, the PC's IP address, DNS behavior, VPN/proxy state, and router lights. That evidence is more useful than running reset commands repeatedly.

When this may be hardware failure

Suspect hardware when this PC fails on every network, the Wi-Fi adapter disappears from Device Manager, Ethernet works through a USB adapter but not the built-in port, or the router fails with multiple known-good devices.

Common mistakes to avoid

  • Changing DNS before checking whether other devices have internet.
  • Resetting Windows because one website is down.
  • Buying a Wi-Fi extender for a PC adapter that is missing in Device Manager.
  • Calling every Wi-Fi problem an ISP outage.

Frequently asked questions

Is 169.254 always a router problem?

No. It means DHCP failed. That can be the router, cable, adapter, blocked network, or a bad port. It is a clue, not a final diagnosis.

Should I use 2.4 GHz or 5 GHz?

2.4 GHz reaches farther but is often crowded. 5 GHz is usually faster nearby but fades sooner through walls. Test in the room where the problem happens.

Written by Practical PC editorial team. We write practical Windows and PC troubleshooting guides for home users, students, and office workers. Guides are researched from official documentation and widely observed support patterns, then reviewed for safety and plain language. We do not invent lab tests, certifications, or first-hand repair experience we do not have.