UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Wi-Fi Won't Connect to Any Network? Fix It Now: hero illustration
Fix It Yourself · Troubleshooting

Wi-Fi won't connect

Published 19 August 202612 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

You know that particular kind of frustration where your laptop can see every network on the street but refuses to join any of them? Yeah. Wi-Fi won't connect is probably the single most common call we get at Vivid Repairs, and honestly, after years of fixing this remotely, it almost always comes down to the same handful of culprits. The good news is that most of them are fixable in minutes, without touching a single piece of hardware.

TL;DR

Wi-Fi won't connect even though networks are visible? Start by toggling Wi-Fi off and on, forgetting the saved network profile and reconnecting. If that doesn't work, update or reinstall the Wi-Fi adapter driver in Device Manager. Still stuck? Run netsh winsock reset from an elevated Command Prompt, then reboot. Full Windows Network reset is the nuclear option if everything else fails.

⏱️ 13 min read ✅ 80% success rate 📅 Updated August 2026

Key Takeaways

  • Wi-Fi won't connect is almost always a software or configuration fault, not broken hardware.
  • Forgetting the saved network profile and reconnecting fixes the majority of cases.
  • Driver issues and corrupted network stacks are the next most common causes.
  • The netsh winsock reset command sequence clears deep network corruption that Settings tools can't touch.
  • If the problem is on every network, it's your PC. If it's just one network, it's probably the router.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 10 to 30 mins
  • Success Rate: 80% of cases sorted without reinstalling Windows

What Actually Causes Wi-Fi Won't Connect?

Before you start clicking things at random, it's worth spending sixty seconds working out which category your problem falls into. Because Wi-Fi won't connect means different things depending on what's happening on screen. Are you getting a spinning circle that times out? A message saying 'Can't connect to this network'? Or does it just sit there doing nothing? Each of those points to a slightly different cause.

The most common culprit by a long way is a corrupted saved Wi-Fi profile. Windows stores your network credentials and settings in a profile, and if that profile gets corrupted (after a Windows update, a router settings change, or even just a rough shutdown) it'll try to connect using bad data and fail every single time. The password might even be correct, but the profile itself is the problem. This is why Forget Network fixes so many cases.

Next up is the Wi-Fi adapter getting itself into a bad state. This happens more than you'd think, especially after sleep or hibernate cycles. The radio is technically on, Windows can scan for networks just fine, but the adapter won't actually negotiate a connection. A driver update or a simple disable/enable cycle in Device Manager usually kicks it back into life.

Then there's the deeper stuff. Windows has a networking stack underneath everything, made up of components like Winsock and TCP/IP. If that gets corrupted (again, often after updates or dodgy software installs) you'll see Wi-Fi won't connect across every network you try. That's when the command-line fixes become necessary. And finally, sometimes it's the router itself: wrong security mode, band steering issues, or a firmware glitch that needs a power-cycle to clear.

One quick way to narrow it down before you start: try connecting to a completely different network, like your phone's hotspot. If Wi-Fi won't connect there either, the problem is definitely on your PC. If your phone hotspot works fine but your home router doesn't, the router is the more likely culprit. Simple test, saves a lot of time.

For context on how Windows handles Wi-Fi connections under the hood, Microsoft's own Wi-Fi troubleshooting page is actually pretty useful as background reading.

Wi-Fi Won't Connect: Quick Fixes to Try First

Right, let's start with the stuff that takes under ten minutes and fixes the problem more often than you'd expect. Don't skip these just because they sound obvious. The number of times I've jumped straight to command-line fixes only to realise Airplane mode was half-on in the background... it happens.

1

Toggle Wi-Fi, Check Airplane Mode, Restart Easy

  1. Toggle Wi-Fi off and on
    Click the network icon in the taskbar, turn Wi-Fi off, wait a full 10 seconds, then turn it back on. Don't rush this. Give the radio time to fully reset.
  2. Check Airplane mode
    Go to Settings, then System, then Notifications (or just search 'Airplane mode' in the Start menu). Make sure it's firmly set to Off. Sometimes it gets stuck in a halfway state after waking from sleep.
  3. Restart the PC
    A proper restart, not just sleep. This clears the adapter state and reloads the driver cleanly.
  4. Power-cycle the router
    Unplug the router from the wall socket. Wait 30 seconds (not 5, actually 30). Plug it back in and wait for all the lights to settle before trying to connect. This one's underrated.
If Wi-Fi connects after this, you're done. The adapter or router was just in a stuck state.
2

Forget the Network and Reconnect Easy

  1. Open Wi-Fi settings
    Go to Settings, then Network and internet, then Wi-Fi, then Manage known networks.
  2. Forget the problem network
    Find your network in the list, click it, then click Forget. This wipes the saved profile completely, including any corrupted credential data.
  3. Reconnect from scratch
    Click the network in the taskbar Wi-Fi list, enter your password carefully (check for caps lock), and connect. Windows builds a fresh profile.
This fixes the majority of 'Can't connect to this network' errors where the password or profile has gone wrong.
If you're not sure what your current Wi-Fi password is, you can find it by going to Control Panel, then Network and Sharing Centre, clicking your connection name, then Wireless Properties, then the Security tab, and ticking Show characters. That shows the stored password, assuming you connected successfully at some point in the past.

More Wi-Fi Won't Connect Solutions: Intermediate Fixes

Still no luck? These next steps go a bit deeper into Windows settings and the adapter itself. They're still well within reach for most people, you just need to be comfortable clicking around in Device Manager and Settings. Nothing scary here.

3

Run the Windows Network Troubleshooter Easy

  1. Open the troubleshooter
    Go to Settings, then System, then Troubleshoot, then Other troubleshooters. Run 'Internet Connections' first, then 'Network Adapter' if the first one doesn't find anything.
  2. Let it run and apply fixes
    Windows will scan for common faults and offer to apply fixes automatically. Accept them. It's not magic, but it does catch things like the WLAN AutoConfig service being stopped.
  3. Reboot after
    Even if the troubleshooter says it fixed something, reboot before testing. Some fixes don't fully apply until after a restart.
The troubleshooter is hit and miss, but when it works it's the fastest path to a fix.
4

Update or Reinstall the Wi-Fi Adapter Driver Medium

  1. Open Device Manager
    Right-click the Start button and choose Device Manager. Expand 'Network adapters'. You should see your Wi-Fi adapter listed (something like Intel Wi-Fi 6 AX201 or Realtek RTL8821CE).
  2. Try updating the driver first
    Right-click the Wi-Fi adapter and choose 'Update driver', then 'Search automatically for drivers'. If Windows finds a newer version, install it and reboot.
  3. If updating doesn't help, uninstall the device
    Right-click the adapter and choose 'Uninstall device'. Tick the box to remove the driver software if it appears, then click Uninstall. Reboot. Windows will detect the adapter on startup and reinstall the driver automatically. This one often needs a second reboot before it sticks, so don't panic if it's still broken after the first restart.
  4. Check Windows Update
    Go to Settings, then Windows Update, and install any pending updates. Driver updates often come through here, especially for Intel and Realtek adapters.
After the driver reinstalls and you've rebooted, try connecting again. A fresh driver clears a lot of adapter state issues.
If your Wi-Fi adapter disappears from Device Manager entirely after uninstalling, don't panic. Shut down fully (not restart), wait 10 seconds, then power back on. This forces a full hardware re-detection on boot.

Driver problems are particularly common after major Windows updates. If Wi-Fi won't connect and the issue started right after a Windows update, the driver route is almost certainly the right one to try. You can also check your PC manufacturer's support page directly (Dell, HP, Lenovo, ASUS all have driver download sections) and grab the Wi-Fi driver from there rather than relying on Windows Update. Manufacturer drivers are sometimes more stable than the generic ones Windows installs automatically.

While you're in this area, it's also worth checking whether the issue is affecting other things on your PC. If you're also having Bluetooth connection problems at the same time, that's a strong sign the wireless adapter itself is struggling, since many laptops use a combined Wi-Fi and Bluetooth chip. A full driver reinstall is the right move in that case.

Advanced Wi-Fi Won't Connect Fixes: Command Line and Network Reset

If you've got this far and Wi-Fi still won't connect on every network you try, the problem is almost certainly in the Windows network stack itself. This is where things got corrupted at a level that the Settings app can't reach. The good news is the command-line tools that fix this are well-documented and very reliable. They just look a bit intimidating if you haven't used them before.

5

Reset the Network Stack with netsh winsock reset Advanced

  1. Open Command Prompt as administrator
    Search for 'cmd' in the Start menu, right-click 'Command Prompt', and choose 'Run as administrator'. You need the elevated version or these commands won't work.
  2. Run the reset commands in order
    Type each line below and press Enter after each one. Wait for each to complete before moving to the next:

    netsh winsock reset
    netsh int ip reset
    ipconfig /flushdns
    ipconfig /release
    ipconfig /renew

    The first two are the important ones. netsh winsock reset rebuilds the Winsock catalogue, which handles how Windows applications talk to the network. netsh int ip reset resets the TCP/IP stack back to defaults. The ipconfig commands clear and refresh your IP and DNS settings.
  3. Reboot
    This is non-negotiable. The Winsock reset doesn't fully apply until after a restart. Try connecting once the PC is back up.
This sequence fixes a surprisingly high percentage of cases where Wi-Fi won't connect on every network. If it works, you'll connect first try after the reboot.

For more context on what these commands actually do under the hood, HowToGeek has a solid breakdown of the Windows network reset process that's worth a read if you want to understand why this works.

6

Check the WLAN AutoConfig Service Medium

  1. Open Services
    Press Win+R, type services.msc and press Enter.
  2. Find WLAN AutoConfig
    Scroll down to 'WLAN AutoConfig' in the list. This is the Windows service that manages Wi-Fi connections. If it's stopped or disabled, Wi-Fi won't connect no matter what else you try.
  3. Restart the service
    Right-click WLAN AutoConfig and choose Restart. If the status shows 'Stopped', choose Start instead. Also check that the Startup type is set to 'Automatic', not 'Manual' or 'Disabled'.
If WLAN AutoConfig was stopped, starting it should let you connect immediately without a reboot.
7

Full Windows Network Reset Advanced

  1. Open Network reset
    Go to Settings, then Network and internet, then Advanced network settings, then Network reset.
  2. Read the warning first
    Network reset removes and reinstalls every network adapter and resets all networking components to defaults. You will lose all saved Wi-Fi passwords and VPN configurations. Make a note of any passwords you'll need before clicking.
  3. Click Reset now
    Windows will restart automatically. After it comes back up, reconnect to your Wi-Fi network and re-enter the password.
Network reset is the nuclear option. It works, but you'll need to reconfigure everything afterwards including VPNs, saved networks and any custom DNS settings.
After Network reset, Wi-Fi won't connect issues caused by deep system corruption are almost always cleared.
8

Test in Safe Mode with Networking Medium

  1. Boot into Safe Mode with Networking
    Hold Shift and click Restart from the Start menu. Choose Troubleshoot, then Advanced options, then Startup Settings, then Restart. Press F5 to boot into Safe Mode with Networking.
  2. Try connecting in Safe Mode
    If Wi-Fi connects fine in Safe Mode but not normally, a third-party application (VPN software, firewall, or security tool) is interfering with the connection in normal Windows. You'll need to identify and uninstall or update that software.
Safe Mode with Networking loads only essential Windows components, so if Wi-Fi works there, the fault is definitely in something that runs at normal startup.

If you've also been having general Windows stability issues alongside this, it's worth running a System File Checker scan too. Open an elevated Command Prompt and run sfc /scannow. This checks for corrupted Windows system files and repairs them automatically. Microsoft's guide to System File Checker explains what it does and what to expect.

And if you're dealing with other connection headaches alongside this, like a wired Ethernet connection that's also playing up, that's a stronger signal that the network stack corruption is the root cause, and the netsh reset sequence above is definitely the right place to focus.

Preventing Wi-Fi Won't Connect in the Future

Most of these fixes work brilliantly, but it's even better if you don't end up back here in three months. Here's what actually helps, in order of importance.

Keep Windows Update running. A huge proportion of Wi-Fi won't connect cases we see are triggered by a Windows update that broke a driver, or a driver update that fixed a known bug. Staying current means you get the fixes as well as the occasional breakages, and the fixes outweigh the breakages by a long margin.

Forget old networks you no longer use. Every time you change your router password or get a new router, go into Manage known networks and remove the old profile. Stale profiles with wrong passwords cause more grief than most people realise. Takes thirty seconds.

Restart your router regularly. Not daily, but once a week or after any power outage is a good habit. Routers accumulate connection state over time and a fresh boot clears a lot of minor issues before they become actual problems. If your router has been running for months without a restart, that's worth doing tonight.

Note whether the issue is one network or all networks. This sounds obvious but most people don't think to test it in the moment. If Wi-Fi won't connect on every network including mobile hotspots, it's your PC. If it's just your home router, it's probably the router or the saved profile. Knowing this before you start troubleshooting cuts the fix time in half.

Wi-Fi Won't Connect: Summary

So, Wi-Fi won't connect is annoying, but it's almost never a hardware problem. In the vast majority of cases it's a corrupted saved profile, a driver that's got itself into a bad state, or a Windows network stack that needs resetting. Start with the quick fixes, forget the network and reconnect, toggle the adapter, power-cycle the router. If those don't work, update or reinstall the driver in Device Manager. And if Wi-Fi still won't connect after that, the netsh winsock reset sequence or a full Network reset will almost certainly sort it. You've got this.

Quick Reference

  • Wi-Fi won't connect but networks are visible: start with Forget Network and reconnect.
  • Failing on every network: driver reinstall or netsh winsock reset.
  • Failing on one network only: router or saved profile issue.
  • WLAN AutoConfig stopped: restart it in services.msc.
  • Nothing else works: full Network reset in Settings, then re-enter passwords.

Frequently Asked Questions

The most common causes are a corrupted saved profile or wrong password, a Wi-Fi adapter stuck in a bad state, a driver or WLAN AutoConfig service problem, or a corrupted network stack. Forgetting the network and reconnecting is the standard first step.

Toggle Wi-Fi off and on, confirm Airplane mode is off, forget the network and re-enter the password, restart the PC, and power-cycle the router. This clears most simple profile and transient radio issues in under five minutes.

Network reset removes and reinstalls all network adapters and resets networking components to their defaults. Use it when Wi-Fi won't connect on multiple networks and simpler fixes have failed. You will need to re-enter saved Wi-Fi passwords afterwards.

From an elevated Command Prompt, run: netsh winsock reset, then netsh int ip reset, then ipconfig /flushdns, then ipconfig /release, then ipconfig /renew. Reboot after. These reset Winsock and TCP/IP and refresh your DNS and IP configuration.

Check whether the failure happens on every network or just one. Failing on all networks points to the adapter, driver or Windows stack. Failing on only one network usually means a router security setting, band mismatch or password problem.