Quick answer
Start with the least destructive check, confirm the device state, and only then change settings. For this problem, the fastest route is usually: Test another device on the same Wi-Fi. Forget and reconnect to the network. Restart the router before changing advanced settings.
Before you start
- Test another device on the same Wi-Fi.
- Forget and reconnect to the network.
- Restart the router before changing advanced settings.
- Reset DNS and network adapter only after basic checks.
Decide whether it is the PC or network
If every device is offline, focus on the router or provider. If only Windows has the issue, focus on the adapter and IP settings.
Open a browser and try a plain HTTP site if you are on hotel or public Wi-Fi. A captive portal may be waiting for sign-in.
Refresh the connection
Turn Wi-Fi off and on, forget the network, then reconnect with the correct password. This rebuilds the local profile.
Restarting the router can clear DHCP problems that leave Windows connected without a valid route.
Reset advanced network state
If basic refreshes fail, run Windows Network Reset or reset the adapter from Settings. This may remove saved networks and VPN adapters.
Update the Wi-Fi driver after internet returns, especially if the issue follows sleep or a Windows update.
Symptom checklist
| What you see | Most likely cause | First safe action |
|---|---|---|
| The device reacts, but the result is wrong | Wrong input, profile, mode, or account state | Confirm the visible setting before resetting anything |
| Nothing reacts at all | Power, cable, port, battery, or button issue | Test with a known good power source or cable |
| The problem comes back after reboot | Saved setting, weak signal, low storage, or failing accessory | Change one variable and write down what changed |
FAQ
- Does connected mean the internet is working?
- No. It only means the PC joined the Wi-Fi network. The router may still have no internet connection.
- Can DNS cause no internet?
- Yes. If IP addresses load but websites do not, DNS settings or provider DNS may be failing.