A computer not connecting to WiFi is one of the most frustrating tech problems because it can come from a dozen different causes — a bad driver, a router setting, a corrupted network profile, or even a physical switch you forgot you flipped. Most guides throw every fix at you in one long list and hope something sticks. This guide works differently: it starts with your exact symptom, then walks you through the real fix for that symptom, on your actual operating system.
Identify Your Exact Symptom First
Before touching any settings, figure out which version of the problem you actually have. A computer not connecting to WiFi because the network doesn’t even appear needs a completely different fix than a computer that connects but shows “no internet.”
| Symptom | Likely Cause | Where to Look First |
|---|---|---|
| No WiFi networks show up at all | Adapter disabled, driver missing, hardware switch off | Device Manager / Airplane Mode |
| Connects but shows “No Internet” | IP conflict, DNS issue, router problem | ipconfig / Network Reset |
| Keeps disconnecting repeatedly | Power management settings, weak driver, router interference | Adapter Power settings |
| Says “Wrong Password” repeatedly | Saved network profile is corrupted | Forget network, reconnect |
| WiFi adapter missing entirely | Driver corruption, hardware failure, BIOS setting | Device Manager, BIOS |
Once you know your symptom, jump to the matching section below.
Quick Fixes to Try First
These basic steps solve a surprising number of cases where a computer not connecting to WiFi issue is just a temporary glitch rather than a deeper fault.
- Restart your computer and your router — power off the router, wait 30 seconds, then power it back on
- Turn Airplane Mode off (Settings > Network & Internet)
- Forget the WiFi network and reconnect with the password entered fresh
- Move closer to the router to rule out signal strength
- Try connecting a different device to confirm whether the problem is the router or the computer
If none of these solve it, the cause is likely something specific to your machine — which is where most generic guides stop and this one keeps going. chromebook not connecting to wifi
Windows 10 and Windows 11 Fixes
Windows is the most common platform searched for this problem, and the fixes differ slightly depending on your version, so check both sections carefully.
Run the Built-In Network Troubleshooter
Windows has a built-in diagnostic tool that identifies common causes of a computer not connecting to WiFi, including disabled adapters and IP conflicts.
- Go to Settings > System > Troubleshoot > Other Troubleshooters
- Select Internet Connections and run it
- Follow any prompts it gives — it often fixes adapter and DNS issues automatically
Check and Reset the Network Adapter
If the adapter itself is disabled or corrupted, no amount of password-retyping will fix it.
- Right-click the Start button and open Device Manager
- Expand Network Adapters
- Right-click your WiFi adapter (usually labeled Intel, Realtek, Broadcom, or Qualcomm)
- Select Disable device, wait 10 seconds, then select Enable device
- If that doesn’t help, right-click again and choose Uninstall device, then restart — Windows will reinstall the driver automatically
Understand Why the Driver Matters
A large share of computer not connecting to WiFi complaints trace back to an outdated or corrupted driver, especially right after a Windows Update. The update process sometimes overwrites a manufacturer’s driver with a generic one that doesn’t fully support your hardware. Identifying your exact adapter model (from Device Manager > Properties > Details tab > Hardware IDs) lets you download the correct driver directly from the manufacturer’s site instead of relying on Windows’ generic version.
Reset the Network Stack with Command Prompt
When the adapter looks fine but the connection still fails, the underlying network stack may be corrupted. This is the fix behind most “connects but no internet” situations.
Open Command Prompt as Administrator and run these in order:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Restart your computer after running these. Each command does something specific:
- netsh winsock reset — repairs corrupted network communication settings
- netsh int ip reset — resets TCP/IP stack to default
- ipconfig /release and /renew — forces your computer to request a fresh IP address from the router
- ipconfig /flushdns — clears cached DNS data that may be pointing to bad addresses
Fix the Power Management Setting That Causes Random Disconnects
If your computer not connecting to WiFi problem is really about it dropping the connection repeatedly rather than failing outright, this is almost always the culprit.
- Open Device Manager > Network Adapters
- Right-click your WiFi adapter and select Properties
- Go to the Power Management tab
- Uncheck Allow the computer to turn off this device to save power
Windows aggressively powers down WiFi adapters to save battery, and on many laptops this setting is the single biggest cause of intermittent drops.
Mac Fixes for WiFi Connection Problems
macOS handles networking differently, and most competing guides skip Mac users entirely.
- Click the Apple menu > System Settings > Wi-Fi
- Turn Wi-Fi off, wait 15 seconds, turn it back on
- Click the info icon next to your network and select Forget This Network, then reconnect
- Open System Settings > General > Transfer or Reset > Reset Network Settings (on newer macOS) to clear corrupted network profiles
- Reset the SMC and NVRAM on older Intel Macs if the WiFi hardware seems unresponsive (Shift + Control + Option + Power for SMC)
Chromebook WiFi Troubleshooting
Chromebooks are lightweight but not immune to connection failures.
- Click the status area, select the WiFi icon, and toggle it off and back on
- Click the network name, select Forget, then reconnect with the password
- Go to Settings > Network > Wi-Fi > Reset network settings
- Run a Powerwash only as a last resort, since it erases local settings
How to Read Your IP Address for Real Diagnosis
This is the step most articles about a computer not connecting to WiFi skip entirely, but it tells you exactly where the failure is happening.
Open Command Prompt and type ipconfig /all. Look at the IPv4 Address:
| IP Address Pattern | What It Means |
|---|---|
| 192.168.x.x or 10.x.x.x | Normal — your computer is getting an address from the router |
| 169.254.x.x | APIPA failure — your computer couldn’t reach the router’s DHCP server at all |
| 0.0.0.0 | No connection established |
A 169.254.x.x address specifically means your computer gave up waiting for the router to assign it an address. That points the problem toward either the router’s DHCP settings or a driver that isn’t communicating properly — not your WiFi password.
Router-Side Causes You Can’t Fix on the Computer Alone
Sometimes a computer not connecting to WiFi issue isn’t about the computer at all. Check these router-side settings before assuming your PC is broken:
- MAC address filtering — the router may be set to block unrecognized devices
- Band steering conflicts — some routers force devices onto 5GHz only, which older adapters can’t see
- DHCP lease pool exhausted — too many connected devices can prevent new ones from getting an IP
- Outdated router firmware — check the manufacturer’s app or admin page for pending updates
- Guest network restrictions — accidentally connecting to a guest network with limited access
Physical and Hardware Causes
If software fixes haven’t worked, the issue could be physical rather than a settings problem.
- Check for a physical WiFi kill switch or function key (often Fn + F2 or similar) on laptops
- Enter BIOS/UEFI setup and confirm the wireless adapter isn’t disabled at the firmware level
- If you recently opened the laptop for a RAM or SSD upgrade, check that the antenna cables are still seated on the WiFi card
- Test with a USB WiFi adapter — if that connects fine, your internal card has likely failed
When to Call a Professional
Most computer not connecting to WiFi problems are solvable with the steps above, but a few signs point to something you shouldn’t troubleshoot alone:
- The WiFi adapter doesn’t appear in Device Manager at all, even after driver reinstalls
- A laptop recently had liquid damage or was dropped
- Multiple driver reinstalls and a clean Windows install still don’t restore the adapter
- The issue only happens on one specific network you don’t control (like a workplace with 802.1X authentication)
In these cases, a hardware technician can confirm whether the wireless card itself has failed, which is a $20–$40 part on most laptops but requires opening the case.
Frequently Asked Questions
Why does my computer say connected but I have no internet?
This usually means your computer has an IP address but can’t reach the router or the wider internet — try ipconfig /release and /renew, or restart the router.
Why did my WiFi stop working after a Windows Update?
Updates sometimes replace your manufacturer’s WiFi driver with a generic one; rolling back or reinstalling the correct driver from the manufacturer’s website usually fixes it.
Can a bad router cause my computer specifically to fail while other devices connect fine?
Yes — check MAC address filtering, band steering settings, or DHCP lease limits on the router, since these can block one device while allowing others.
How do I know if the problem is my computer or my router?
Try connecting a different device to the same network; if it also fails, the router is the problem, and if it connects fine, the issue is isolated to your computer.
Is it safe to run netsh winsock reset?
Yes, this command only resets network configuration settings and does not delete files or affect other software.
Why does my WiFi keep disconnecting every few minutes?
This is most often caused by a power management setting that lets Windows turn off the adapter to save battery — disabling that setting usually resolves it.
Do I need a new router if nothing else works?
Only after confirming the computer itself isn’t the fault via a USB adapter test — if the USB adapter also fails to hold a connection, the router or ISP is more likely the cause.
