Wi-Fi password not working in Windows 11 — entering the correct password but getting “Can’t connect to this network,” password rejected immediately, or the network never finishing the authentication process — has a clear set of causes that depend on whether the password is definitely correct and whether other devices can connect. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Verify the actual password first. The most common cause of Wi-Fi password failure is a wrong password — typos, confusing 0 and O, mixed case errors, or a password that was changed on the router without updating all devices. On the router’s admin page (typically 192.168.1.1 or 192.168.0.1): find the current Wi-Fi password under Wireless → Security or equivalent. Compare character by character with what you’re entering in Windows.
Forget the network and reconnect
Windows stores Wi-Fi connection profiles including the password. When the router’s password changes: Windows keeps the old saved password and fails authentication repeatedly without prompting for the new one. The fix: forget the saved connection and reconnect fresh.
Settings → Network and internet → Wi-Fi → Manage known networks → find the network → Forget. After forgetting: click the network in the taskbar Wi-Fi menu → Connect → enter the current password. This creates a fresh connection profile with the correct credentials rather than reusing the outdated saved one.
Network adapter driver and Windows Hello credential cache
An outdated Wi-Fi adapter driver sometimes fails to complete WPA2 or WPA3 authentication even with the correct password — the authentication process starts but doesn’t complete, appearing as a password rejection. Install the manufacturer-specific driver for your Wi-Fi adapter from the laptop manufacturer’s support page (not from Windows Update). After updating: forget the network (above) and reconnect.
Router security protocol mismatch
Windows 11 dropped support for WEP and some WPA (TKIP-only) configurations. If the router is set to WEP or “WPA Personal (TKIP only)”: Windows 11 refuses to connect even with the correct password, because it won’t use those insecure protocols.
Router admin → Wireless → Security: set to WPA2 Personal (AES) or WPA3, or WPA2/WPA3 mixed mode. After changing: reconnect Windows. Also: if the router uses WPA3 but has compatibility issues with older devices, switch to WPA2/WPA3 mixed mode — this allows both WPA2 and WPA3 clients to connect.
MAC address filtering
Routers can be configured to only allow specific devices based on their MAC addresses. If MAC filtering is enabled on the router and your Windows 11 machine’s MAC isn’t in the allowed list: it can’t connect regardless of whether the password is correct.
Check: router admin → Wireless → MAC filtering or Access Control. If filtering is enabled: either add the Windows machine’s MAC address (Settings → Network → Wi-Fi → hardware properties → shows MAC address), or disable MAC filtering if it’s not serving a genuine security purpose (it provides minimal security and causes frequent connectivity problems).
Windows 11 random MAC address
Windows 11 can use a random hardware address (MAC) for Wi-Fi connections to improve privacy. If random MAC is enabled and the router uses MAC filtering: the random MAC won’t match the allowed list, causing connection failure with a correct password.
Settings → Network and internet → Wi-Fi → the network → “Random hardware addresses” → Off. After disabling: forget and reconnect the network. This ensures Windows uses the fixed physical MAC address that can be added to the router’s allowed list.
Reset network settings
Corrupted Wi-Fi adapter settings or driver state can cause persistent password failures. Administrator Command Prompt:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
Restart after running all five commands. This resets the network stack to a clean state, resolving corruption that causes authentication failures unrelated to the actual password.
Our guide on Wi-Fi connection troubleshooting covers the full range of Wi-Fi failures beyond password issues, including connectivity problems after a successful connection. For router configuration including security protocols, our network configuration guide covers router admin access and settings. Microsoft’s Wi-Fi troubleshooting documentation covers the Windows 11 Network Reset feature in Settings that resets all network adapters and settings simultaneously — more thorough than individual netsh commands but also more disruptive, requiring VPN and network configuration to be re-entered after the reset.
Corporate Wi-Fi with certificates
Enterprise Wi-Fi (WPA2 Enterprise, typically used in offices and universities) uses certificates rather than a simple password. If a work Wi-Fi requires credentials that aren’t working: the authentication may require a certificate installed on the device, or RADIUS server credentials (username and password for the domain account, not the Wi-Fi password specifically). Settings → Network and internet → Wi-Fi → the network → Advanced → authentication settings. For enterprise Wi-Fi troubleshooting: IT manages the authentication infrastructure — contact IT rather than modifying authentication settings.
Viewing the saved Wi-Fi password
If you need to confirm what password Windows has saved for a network: Command Prompt:
netsh wlan show profile name="NetworkName" key=clear
Replace “NetworkName” with the actual SSID. The output includes “Key Content” which shows the currently saved password. If this matches the router’s current password but authentication still fails: the issue is protocol, driver, or network state — not the password itself. If it shows an old password: forgetting and reconnecting (with the new password) is the correct fix.
Password special characters
Wi-Fi passwords with special characters (#, @, &, %) occasionally cause issues on specific router firmware versions or with specific driver implementations. If a complex password fails but a simpler one works on the same network: a special character in the password may be the cause. Temporarily set a simpler test password on the router (letters and numbers only) → test connection → if it connects: the special character was the issue. Most modern routers and drivers handle all printable ASCII characters correctly, but older or budget router firmware sometimes doesn’t.
DHCP lease failure appearing as password failure
Sometimes the authentication (password check) succeeds but DHCP fails to assign an IP address. Windows shows “Can’t connect” which looks like a password failure but is actually an IP assignment failure. Distinguish them: if the connection briefly shows “Authenticating” then “Getting network requirements” then fails: DHCP, not password. If it fails immediately at “Checking network requirements” or never shows progress: password or protocol.
DHCP failure fix: router admin → DHCP → check available addresses and lease times. If the DHCP pool is exhausted (too many devices): expand the pool or reduce lease times. Or manually assign an IP: Network adapter Properties → IPv4 → Use the following IP address → enter an IP in the router’s range (e.g., 192.168.1.200), subnet 255.255.255.0, gateway 192.168.1.1 → this bypasses DHCP entirely.
Hidden networks
If the router is configured with a hidden SSID (not broadcasting its name): Windows 11 can still connect, but requires manual network entry. Settings → Network and internet → Wi-Fi → “Manage known networks” → “Add a new network” → enter the exact SSID (case sensitive), security type, and password. Hidden networks don’t appear in the standard Wi-Fi scan list — you must manually type the SSID exactly as configured on the router. A typo in the hidden SSID causes a “network not found” error, which can be confused with a password failure.
Wi-Fi band and frequency
Modern routers broadcast on both 2.4 GHz and 5 GHz. Some routers use the same SSID for both bands; others use separate SSIDs (e.g., “HomeNetwork” and “HomeNetwork_5G”). If connecting to the 5 GHz network: the device must support 5 GHz Wi-Fi. Most modern laptops do, but if a password failure only occurs on the 5 GHz band while the 2.4 GHz band connects: the device may not support 5 GHz, or the 5 GHz band is on a different SSID with a different password.
Device Manager → Network Adapters → your Wi-Fi adapter → Properties → Advanced tab → “Band preference” or “802.11 mode” — if it shows 2.4 GHz only: the device doesn’t support 5 GHz. Connect to the 2.4 GHz network instead.
| Error / behaviour | Cause | Fix |
| Password rejected immediately | Wrong password; old saved profile | Verify password on router; Forget network; reconnect |
| Connects then disconnects | DHCP failure or authentication timeout | Check DHCP pool; assign static IP |
| Works on other devices, not Windows | Driver issue or WPA3 incompatibility | Update Wi-Fi driver; check security protocol setting |
| Never shows the network | Out of 5 GHz range; hidden SSID | Try 2.4 GHz; manually add hidden network |
| Was working, stopped after router reset | Router changed password or SSID | Forget saved network; reconnect with new credentials |
Wi-Fi password failures are almost always one of three things: wrong password (verify on router), outdated saved profile (forget and reconnect), or router security protocol incompatibility (set router to WPA2 AES or WPA3). The netsh command to view the saved password, combined with the forget-and-reconnect procedure, resolves the majority of Windows 11 Wi-Fi password rejections in under 5 minutes.
For users who travel frequently and connect to new networks often: Windows’ “Wi-Fi Sense” and network sharing features from Windows 10 were removed in Windows 11, so passwords no longer auto-share with contacts. Each new network requires manual entry of the correct password. For frequently-visited networks (office, relative’s home, gym): Windows stores the password after first successful connection. If a stored password stops working: the network’s password changed, and the forget-and-reconnect procedure is needed rather than any technical investigation.
Credential Manager and Wi-Fi
Windows stores some network credentials in Credential Manager alongside Wi-Fi profiles. For enterprise Wi-Fi that uses Windows credentials: Control Panel → Credential Manager → Windows Credentials → look for entries matching the network name or authentication server. If outdated credentials for an enterprise network appear there: remove them → try reconnecting. Fresh credential prompts allow entering current domain credentials rather than the outdated stored ones.
SSID confusion on mesh networks
Mesh Wi-Fi systems (Eero, Google Nest WiFi, Orbi) broadcast a single SSID from multiple access points. The password is the same across all access points — it’s one network, not multiple. If a mesh network password fails: the password check is against the primary router’s configuration, same as a single-router setup. Verify the password through the mesh network’s app rather than accessing a traditional router admin page — mesh systems are managed through their smartphone app or web portal rather than the standard 192.168.1.1 admin interface.
For mesh networks showing different SSIDs (mesh backhaul SSIDs alongside the main SSID): connect only to the main SSID. The backhaul connections between mesh nodes have different credentials not meant for client devices. If the wrong SSID is being attempted, this appears as a password failure for the backhaul SSID that simply isn’t for device connections.
One underappreciated tip for home networks: changing the Wi-Fi password on the router requires updating every device individually. Phones, tablets, smart TVs, streaming sticks, game consoles, smart home devices — each stores the old password and needs to be reconnected after a router password change. A password change that resolves one device’s problem (security concern, new password policy) creates a temporary disruption for every other device. Planning the device reconnection sequence before changing the password — especially for smart home devices where the process is less intuitive — reduces the post-change frustration significantly.
QR code for Wi-Fi sharing
Windows 11 can share Wi-Fi credentials via QR code to simplify connecting new devices. Settings → Network and internet → Wi-Fi → your network → “Share” → Windows generates a QR code that other devices can scan to connect automatically without typing the password. This feature is useful for sharing guest credentials, connecting phones without typing complex passwords, and confirming that the password Windows has stored is the correct one (if another device scans and connects: the password is correct; if it fails: the stored password is wrong).
For anyone who’s exhausted the above fixes and still can’t connect: connect via Ethernet temporarily → access the router admin → change the Wi-Fi SSID to a new name and set a fresh, simple alphanumeric password → save → from Windows, forget the old network → find the new SSID → connect with the new password. This creates a completely clean starting point — new SSID, new password, new Windows profile — that rules out any cached profile or saved credential issue. If this also fails: the problem is hardware (Wi-Fi adapter, router’s 2.4/5 GHz radio) rather than software, and hardware-level investigation or replacement is needed.
In summary: Wi-Fi password failures in Windows 11 resolve through a predictable sequence. Verify the password is correct (check the router). Forget the saved profile and reconnect (clears old credentials). Update the Wi-Fi adapter driver (fixes authentication failures with correct password). Check the router’s security protocol (fixes WEP/WPA TKIP rejections). Check MAC filtering (fixes silent blocking). The netsh commands reset corrupted network state. Each step eliminates one possible cause, and the sequence covers the full range of password failure scenarios from the simplest to the most obscure. You might also run into WiFi Keeps Asking for Password on Windows 11.
