Windows 11 Won’t Connect to Wi-Fi: Profile, Driver, Protocol

Windows 11 not connecting to Wi-Fi — the network not appearing in the list, the connection attempting then failing, or the machine connecting but internet not working — each symptom points to a different part of the stack. Spending a minute identifying which you have is more valuable than trying fixes randomly. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.

Quick classification: can you see your Wi-Fi network in the available list? If yes, and connection fails: authentication or profile issue. If no, but other networks appear: your specific router or band isn’t visible. If no networks appear at all: the Wi-Fi adapter isn’t working. Start from whichever of these matches your situation.

No networks visible — adapter and driver check

If the Wi-Fi icon shows no networks at all: check that Wi-Fi is physically on. Settings → Network & internet → Wi-Fi → the toggle must be On. Also check: Airplane mode (the quick settings panel via the Wi-Fi icon in the taskbar). Airplane mode off + Wi-Fi on is the required state.

If Wi-Fi is on but still no networks: Device Manager → Network adapters → look for your Wi-Fi adapter. If it has a yellow warning triangle: driver issue. If it’s not listed: the adapter isn’t detected. Right-click → Scan for hardware changes → see if it appears. If not:

• Restart the machine (not shut down + power on — an actual Restart)
• Check BIOS: reboot → F2/Delete during POST → look for wireless LAN enable/disable setting → ensure Enabled
• Update the Wi-Fi driver: Device Manager → the adapter → Update driver → or download from the manufacturer’s site

Your network not appearing — 2.4 GHz vs 5 GHz

If other networks appear but yours doesn’t: the likely causes are the router hiding the SSID, the laptop not supporting the frequency band the router uses, or signal too weak. Check:

Router admin → Wireless settings → “SSID Broadcast” or “Visible” → if disabled, the network is hidden and won’t appear in the scan list. You’d need to manually add it: Settings → Network → Wi-Fi → “Manage known networks” → “Add a new network” → enter the SSID, security type, and password.

Band mismatch: older Wi-Fi adapters don’t support 5 GHz. If your router broadcasts a 5 GHz network with a different name than the 2.4 GHz one, and your adapter only sees 2.4 GHz: you’d see neighbouring 5 GHz networks from other routers but not your own. Check the adapter’s supported bands in Device Manager → the adapter → Properties.

Connection attempts failing — the profile fix

The most common cause of “connection fails” on a network you’ve connected to before: the saved profile has an incorrect password (you changed the router password and the old one is cached). Fix: “Forget” the network → reconnect → enter the current correct password.

Settings → Network & internet → Wi-Fi → “Manage known networks” → find your network → “Forget” → click the network in the taskbar → Connect → enter password. This is the most-overlooked fix for a network that shows as available but fails to connect.

Also try: running the network troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Internet Connections → Run. For simple profile and adapter state issues, this resolves them automatically.

Network stack reset — for connected but no internet

If Wi-Fi connects (shows “Connected” status) but internet doesn’t work: the connection is established but the network configuration is wrong — IP, DNS, or the routing table got corrupted.

Admin Command Prompt:

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

Restart after running all five. These commands reset the Windows networking stack, force a fresh IP lease from your router, and clear stale DNS entries. After restart: Wi-Fi reconnects with clean configuration. This resolves the majority of “connected but no internet” scenarios.

Our guide on Wi-Fi keeps disconnecting covers the intermittent drop situations, and our DNS troubleshooting covers the specific case where connected but internet fails due to DNS specifically. For advanced Wi-Fi adapter configuration and driver management, Microsoft’s Wi-Fi troubleshooting documentation covers network reset procedures and adapter diagnostics.

Authentication type mismatch

If the router recently changed security mode (WPA2 to WPA3, or from mixed mode to WPA3-only) and older devices can’t connect: the laptop’s saved profile specifies a different security type than what the router now requires. “Forget” the network → reconnect → Windows negotiates the correct security type fresh.

For Windows 11 specifically: WPA3 (SAE) is supported. But older drivers may not support it reliably. If you’ve switched your router to WPA3-only and Windows 11 can’t connect: either set the router to WPA2/WPA3 mixed mode, or update the Wi-Fi driver to the latest version which typically has better WPA3 support.

MAC address filtering on the router

Some routers have MAC filtering enabled — they only allow connections from devices whose hardware addresses are pre-approved. If you replaced a network adapter or got a new laptop: the new MAC address isn’t in the allowed list.

Check: router admin → Wireless → MAC Address Filter → see if your laptop’s MAC is listed. Your laptop’s MAC: Settings → Network → Wi-Fi → your connection → scroll down → “Physical address (MAC)” — add this to the router’s allowed list. Or disable MAC filtering (it provides minimal security while adding administrative overhead).

Note: Windows 11 uses “Random hardware addresses” by default to protect privacy — it presents a different MAC address to each Wi-Fi network rather than the real hardware MAC. If your router has MAC filtering: this random MAC won’t be in the allowed list. Turn off random addresses for your home network: Settings → Network → Wi-Fi → hardware properties → “Random hardware addresses” → Off.

IP address conflicts

If the router’s DHCP server assigns an IP that’s already in use by another device: connection fails silently or the laptop gets an APIPA address (169.254.x.x) instead of the expected 192.168.x.x range.

Check: if ipconfig shows an IP starting with 169.254: DHCP failed. Either no IP was available (DHCP pool exhausted) or the renewal failed. Restart the router → reconnect. If the pool is genuinely exhausted (all IPs assigned): router admin → DHCP → expand the IP range or increase the lease time so expired leases free up faster.

Windows 11 network profile type

When you first connect to a network, Windows asks if it’s public or private. Public networks get stricter firewall rules. Some home network setups require features (file sharing, network discovery) that public profile blocks — but more relevantly, the network profile type affects some connectivity scenarios.

Settings → Network & internet → your Wi-Fi connection → Properties → Network profile type. For home networks: Private. For untrusted networks: Public. Switching from Public to Private on a home network sometimes resolves connectivity issues where the firewall rules were too restrictive.

Fresh driver for the Wi-Fi adapter

If the adapter exists in Device Manager without warnings but won’t connect to anything: the driver may be functioning but producing incorrect connection behaviour. A complete driver reinstall often fixes this:

1. Device Manager → Network adapters → your Wi-Fi adapter → right-click → Uninstall device → check “Delete the driver software” → confirm
2. Restart Windows
3. Windows reinstalls a generic driver
4. Test if Wi-Fi connects
5. If yes: continue with the generic driver or install the manufacturer’s specific version for better performance

The manufacturer’s specific driver (Intel, Realtek, Qualcomm — from intel.com or your laptop maker’s support page) usually performs better than the generic one. After a fresh install: reconnect to the network by entering the password fresh rather than using a saved profile.

The “forget and reconnect” step resolves more Wi-Fi connection failures than any other single action — it eliminates stale profile data that Windows sometimes holds onto even when the underlying cause has changed. Always worth trying before driver reinstalls or advanced configuration changes.

Corporate and enterprise Wi-Fi

Connecting to WPA2-Enterprise or WPA3-Enterprise networks (common in offices, universities, and organisations) requires certificate-based authentication rather than a simple password. If connecting to a corporate network that prompts for username/password rather than just a password: you’re connecting to an enterprise network.

These networks often require your Active Directory or Microsoft 365 credentials and a computer certificate. On domain-joined Windows 11 machines: the certificate and credentials are provisioned automatically. On personal devices trying to connect to a corporate network: IT needs to provide a configuration profile or walk you through the manual EAP configuration. Settings → Network → Wi-Fi → Manage known networks → Add a new network → configure EAP type, inner authentication, and certificate settings according to IT’s instructions.

Certificate errors during enterprise Wi-Fi connection: usually a certificate mismatch or an expired device certificate. On managed devices: running Group Policy update (gpupdate /force in admin Command Prompt) refreshes certificates. On unmanaged devices: a certificate from IT may need to be manually installed.

Captive portals not loading

Hotel, café, and airport Wi-Fi often use captive portals — after connecting, you see a login or terms-of-service page before internet access is granted. Sometimes this portal page doesn’t appear automatically.

Fix: after connecting, open a browser → navigate to any HTTP (not HTTPS) page → the portal redirect should trigger. Try http://neverssl.com specifically — it’s a simple HTTP page that always stays HTTP, designed to trigger captive portal redirects. If no redirect: the portal detection may have failed. Check: Settings → Network → Properties → see if “Limited” connectivity is shown (indicating captive portal presence).

After Windows Update connection issues

Windows Updates occasionally reset network adapter settings, introduce driver regressions, or change network profile classifications. If Wi-Fi stopped connecting after a Windows Update: check Update history → identify the specific KB update → run the network stack reset commands above. If that fails: Device Manager → Wi-Fi adapter → Driver tab → Roll Back Driver if available. The roll-back restores the previous driver that was working correctly before the update.

Router-side vs PC-side

The definitive test for whether the problem is the PC or the router: try connecting a different device (phone, tablet, another laptop) to the same network. If others connect fine and this PC doesn’t: it’s a PC-side issue, and the fixes above apply. If no devices can connect: it’s the router or internet service — restart the router, check the ISP status, or contact support.

This test takes 30 seconds and saves significant troubleshooting time by immediately confirming which side of the connection is broken. Many people spend an hour on PC-side fixes when their router needed a simple restart.

Persistent connection issues after all fixes

If the standard fixes haven’t worked: Windows’ deeper network configuration can sometimes need a full reset. Settings → Network & internet → Advanced network settings → Network reset → “Reset now.” This removes all installed network adapters and resets all networking components to defaults. After the reset, Windows reinstalls network adapters and you’ll need to re-enter Wi-Fi passwords. It’s the most thorough Windows-side fix available without a full reinstall.

Network reset is a significant operation — it removes VPN clients, custom DNS settings, and any manually-configured network adapters. Use it as a last resort rather than a first step. But for a machine where Wi-Fi genuinely won’t connect despite correct driver and profile: it often resolves issues that more targeted fixes can’t reach.

One more targeted fix for intermittent failures specifically: if the network connects, drops after a few minutes, and needs reconnecting: this is the sleep/wake or DHCP lease issue covered in the Wi-Fi-disconnects-when-sleeping guide. Disable the adapter’s power management (Device Manager → adapter → Power Management → uncheck “Allow computer to turn off this device”) and set Wireless Adapter power saving to Maximum Performance in advanced power settings. These two changes together often permanently fix the “connects then drops” pattern that can look like a “can’t connect” problem when it happens quickly after connecting. You might also run into DNS Server Not Responding.