Fix “Windows Can’t Connect to This Network” (Wi‑Fi) in Windows 10/11: Step-by-Step

  • Thread Author

Fix “Windows Can’t Connect to This Network” (Wi‑Fi) in Windows 10/11: Step-by-Step​

Difficulty: Intermediate | Time Required: 20 minutes
When Windows shows “Can’t connect to this network” while joining Wi‑Fi, it usually means something in the connection chain is mismatched or stuck—saved Wi‑Fi credentials, adapter drivers, DHCP/IP settings, router security mode, or the Windows networking stack. The steps below walk you through the most reliable fixes in a safe order, from least disruptive to most thorough, and apply to both Windows 10 and Windows 11.

Prerequisites​

Before you begin, have the following ready:
  • The Wi‑Fi password (and the exact network name/SSID if there are multiple similar ones)
  • Admin access to your Windows PC (needed for network reset commands)
  • Optional but helpful: access to the router (or someone who can restart it / confirm settings)
  • If possible, a backup internet method (Ethernet or phone hotspot) in case you need a driver update
Note (Windows versions):
Steps and menu names are nearly identical across Windows 10/11, but Windows 11 uses “Settings > Network & internet”, while Windows 10 uses “Settings > Network & Internet.”

Step-by-step: Fix the Wi‑Fi connection error​

1) Confirm the basics (quick checks that save time)​

  1. On your PC, click the Wi‑Fi icon in the taskbar.
  2. Toggle Wi‑Fi Off, wait 5 seconds, then toggle it On.
  3. Make sure Airplane mode is Off.
  4. Try connecting again.
If you can see the network but it fails instantly, continue to Step 2.

2) “Forget” the Wi‑Fi network and reconnect (fixes most credential issues)​

Saved profiles can become corrupted or have the wrong security key.
Windows 11
  1. Go to Settings > Network & internet > Wi‑Fi.
  2. Click Manage known networks.
  3. Select your Wi‑Fi network > Forget.
  4. Return to the Wi‑Fi list, select the network, click Connect, and re-enter the password.
Windows 10
  1. Go to Settings > Network & Internet > Wi‑Fi.
  2. Click Manage known networks.
  3. Select the network > Forget.
  4. Reconnect and enter the password.
Tip: If the network name appears twice (e.g., “MyWiFi” and “MyWiFi 2”), try both 2.4 GHz and 5 GHz variants. Some adapters struggle with certain bands or channel widths.

3) Restart the router/modem (clears stuck sessions and DHCP leases)​

  1. Power off your router (and modem if separate).
  2. Wait 30 seconds.
  3. Power them back on.
  4. Wait 2–3 minutes for the Wi‑Fi to fully come up.
  5. Try connecting again.
Warning: Don’t press “Reset” (factory reset) unless you intend to reconfigure your router from scratch.

4) Run the built-in Windows network troubleshooter​

It won’t fix everything, but it can automatically correct some misconfigurations.
Windows 11
  1. Settings > System > Troubleshoot > Other troubleshooters
  2. Run Network and Internet (and optionally Wi‑Fi if present).
Windows 10
  1. Settings > Update & Security > Troubleshoot
  2. Select Additional troubleshooters
  3. Run Internet Connections and Network Adapter

5) Disable/enable the Wi‑Fi adapter (quick driver/stack refresh)​

  1. Right-click Start > Device Manager.
  2. Expand Network adapters.
  3. Right-click your Wireless/Wi‑Fi adapter > Disable device.
  4. Wait 10 seconds.
  5. Right-click it again > Enable device.
  6. Retry the connection.
Note: The adapter name often includes Intel, Realtek, Qualcomm, MediaTek, or “Wireless-AC/AX.”

6) Update (or roll back) your Wi‑Fi driver​

A recent Windows Update or vendor update can cause compatibility issues—especially with WPA2/WPA3 or 802.11ax (Wi‑Fi 6).
  1. Open Device Manager > Network adapters.
  2. Right-click your Wi‑Fi adapter > Properties.
  3. Go to the Driver tab:
    • Click Update Driver > Search automatically for drivers.
  4. If the problem started recently, try Roll Back Driver (if available).
Tip: For laptops, the most stable driver is often from the laptop manufacturer’s support page (Dell/HP/Lenovo/ASUS), not Windows Update.

7) Reset the Windows networking stack (Winsock/IP reset)​

This fixes many “can’t connect” errors caused by corrupted network settings.
  1. Right-click Start > Windows Terminal (Admin) or Command Prompt (Admin).
  2. Run these commands one by one:
Code:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
  1. Restart your PC.
  2. Try connecting again.
Warning: If you use VPN clients or advanced firewall tools, this may reset some of their network components. Usually reinstalling/updating the VPN client resolves any side effects.

8) Check IP settings (DHCP vs. manual IP conflicts)​

Most home networks should use automatic (DHCP).
Windows 11
  1. Settings > Network & internet > Wi‑Fi
  2. Click your connected/target network (or Hardware properties depending on build)
  3. Check IP assignment and DNS server assignment
  4. Set both to Automatic (DHCP) where possible.
Windows 10
  1. Settings > Network & Internet > Wi‑Fi
  2. Click the network > ensure IP/DNS are not set to an incorrect static value.
Troubleshooting clue: If other devices connect fine but your PC won’t, a bad saved static IP or incorrect DNS can be the culprit.

9) Ensure your router security mode is compatible (WPA2/WPA3)​

If you recently changed router settings (or received a firmware update), Windows may fail to authenticate.
  1. Log into your router/admin interface.
  2. Locate Wireless Security settings.
  3. Prefer:
    • WPA2-Personal (AES) for widest compatibility, or
    • WPA2/WPA3 mixed mode if all devices support it.
  4. Avoid legacy modes like WEP or WPA (TKIP) (insecure and can cause connection issues).
  5. Save changes and reconnect from Windows (you may need to “Forget” the network again—see Step 2).
Note: Some older Wi‑Fi adapters have trouble with WPA3-only networks and will throw “Can’t connect” even with the correct password.

10) Use “Network reset” (most thorough Windows-side fix)​

If the above steps fail, a full network reset often resolves stubborn problems.
Windows 11
  1. Settings > Network & internet > Advanced network settings
  2. Select Network reset
  3. Click Reset now
  4. Restart when prompted, then reconnect to Wi‑Fi.
Windows 10
  1. Settings > Network & Internet > Status
  2. Scroll down to Network reset
  3. Click Reset now
  4. Restart and reconnect.
Warning: This removes saved Wi‑Fi networks and may reset VPN/virtual adapters. Plan to re-enter Wi‑Fi passwords afterward.

Tips and troubleshooting notes (when it still won’t connect)​

  • Try another network (phone hotspot). If your PC can connect elsewhere, the issue is likely router settings (security mode, channel width, MAC filtering, DHCP).
  • Check date/time: Incorrect system time can break authentication on some networks.
    Go to Settings > Time & language and enable Set time automatically.
  • 802.11ax / Wi‑Fi 6 quirks: If your router is set to Wi‑Fi 6 only, older adapters may fail. Try mixed mode (802.11ac/n) temporarily.
  • Signal quality matters: “Can’t connect” can occur when the signal is marginal and the handshake fails. Test closer to the router.
  • Captive portals: On some public networks, it may “connect” but not allow internet until you sign in. Open a browser and try visiting [NeverSSL - Connecting ...](http://neverssl.com).
  • Last resort hardware check: If Wi‑Fi is consistently failing, test with a known-good USB Wi‑Fi adapter. If that works, your internal adapter may be failing.

Conclusion​

By forgetting the saved Wi‑Fi profile, restarting networking components, updating drivers, and resetting the Windows network stack, you can fix the vast majority of “Windows can’t connect to this network” errors in Windows 10 and Windows 11—without reinstalling Windows. The key is working from simple causes (bad saved credentials) to deeper fixes (Winsock/IP resets and network reset), and verifying router security compatibility when needed.
Key Takeaways:
  • Forgetting and reconnecting to the Wi‑Fi network fixes many authentication/profile issues.
  • Driver updates (or rollbacks) and adapter resets resolve common compatibility problems.
  • Winsock/IP resets and Network Reset repair corrupted Windows networking components.
  • Router security mode (WPA2/WPA3) and band compatibility can directly cause “can’t connect” errors.

This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.
 

Does the error happen only on this one Wi-Fi network, or do you see the same “Can’t connect to this network” message when you try a phone hotspot or a different Wi-Fi as well?
 

Good question — that’s the first thing to check.
Quick answer: please try connecting to another Wi‑Fi network (your phone’s hotspot or a neighbour’s/public Wi‑Fi) and tell me whether you get the same “Can’t connect to this network” message or whether the phone hotspot works.
What to test and why (two minutes)
1) Try a phone hotspot (or a different Wi‑Fi).
  • If the hotspot connects OK → problem is likely with that specific router/SSID (DHCP/security/MAC filter or router firmware).
  • If the hotspot also fails → problem is likely with the PC (driver, Windows profile, services, hardware).
If it still fails, please run these commands in an elevated Command Prompt and paste the outputs (they help me pinpoint the issue):
  • netsh wlan show interfaces
  • netsh wlan show drivers
  • netsh wlan show profiles
  • ipconfig /all
  • ping 8.8.8.8 -n 4
  • route print | findstr /i "0.0.0.0"
Quick things you can try right now
  • Forget the problem SSID: Settings → Network & internet → Wi‑Fi → Manage known networks → Forget → reconnect and retype the password.
  • Reboot the router and the PC.
  • Update the Wi‑Fi adapter driver from Device Manager or your PC maker’s website.
  • Temporarily disable any VPN/third‑party firewall/antivirus and test.
  • Check the router: is MAC filtering, enterprise/WPA‑Enterprise, or hidden SSID enabled? Try enabling WPA2‑Personal with a simple password just to test.
Tell me:
  • Result of hotspot test (works or fails).
  • Your OS (Windows 10 or 11) and build, and the Wi‑Fi adapter model from Device Manager (or paste the netsh/net output).
I’ll then give the exact next steps (router checks, driver commands, or profile fixes) based on what you find.
 

Back
Top