Entering a Wi-Fi password correctly and still getting “Incorrect password” or “Can’t connect to this network” is one of the more disorienting tech problems because you know the password is right. The issue is rarely the password itself — it’s one of several other things masquerading as a password error. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The most common cause: the saved network profile is corrupted or outdated. Windows stores Wi-Fi passwords in network profiles, and these occasionally go wrong — particularly after router firmware updates, after replacing a router, or after Windows updates that change how credentials are stored. Forgetting and restarting the connection takes 30 seconds and resolves this in most cases.
Click the Wi-Fi icon → click the arrow next to your network → Forget → wait 10 seconds → click the network name → Connect → enter the password fresh. If this works, the old profile was the problem. No further action needed.
Verifying the Password Is Actually Correct
Before going further: confirm the password is definitely right by checking it on another device. Connect a phone to the same network. Does the phone connect with the password you think is correct? If the phone connects, the password is right and the problem is Windows-specific. If the phone also fails, the password has changed at the router — log into the router admin panel and reset it.
View the currently stored Wi-Fi password: Settings → Network and internet → Wi-Fi → Manage known networks → click your network → Properties → Show → the password appears. Compare this to what you’re entering. Case sensitivity matters — Wi-Fi passwords are case-sensitive, and a single uppercase/lowercase mismatch causes the exact “incorrect password” error you’re seeing.
Fix 1: The Network Stack Reset
If forgetting and reconnecting didn’t fix it, the Windows network stack — the software layer that handles authentication — may have gotten into a bad state. Running these commands from an administrator Command Prompt and restarting often clears authentication failures that look like password errors:
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsAfter restarting: Settings → Wi-Fi → find the network → Connect → try entering the password. A clean network stack removes the possibility that corrupted state from a previous failed connection attempt is interfering with the new one.
Fix 2: Update the Wi-Fi Adapter Driver
An outdated or corrupted Wi-Fi driver causes authentication failures that look exactly like wrong password errors. The driver handles the WPA2/WPA3 security handshake with the router — if it doesn’t implement the handshake correctly, the connection fails at authentication even with valid credentials.
Device Manager → Network Adapters → right-click your Wi-Fi adapter → Update driver → search automatically. Better: go to the laptop manufacturer’s support page and download the current Wi-Fi driver for your model. Manufacturer drivers handle authentication protocols more reliably than generic Windows drivers, particularly for WPA3 and WPA2/WPA3 mixed mode.
Fix 3: WPA3 Protocol Mismatch
Modern routers offer WPA3 security or WPA2/WPA3 mixed mode. Some Windows 11 Wi-Fi drivers — particularly older Intel and Qualcomm adapters — have incomplete WPA3 implementation that causes authentication to fail in a way Windows reports as an incorrect password.
Test: log into your router admin panel (usually 192.168.1.1) → find Wi-Fi security settings → temporarily change from WPA3 or WPA2/WPA3 mixed to WPA2-Personal only → save and reconnect Windows. If it connects successfully, WPA3 incompatibility is confirmed. The permanent fix is updating the Wi-Fi driver (newer driver versions improve WPA3 handling). Leave WPA2-only as a temporary workaround while testing the driver update, then switch the router back to WPA3/mixed after the driver update.
Fix 4: Check Security Type in Network Properties
The network profile stores not just the password but the expected security type (WPA2, WPA3, etc.). If the router’s security type changed — or if the profile was saved during a different security configuration — the mismatch causes authentication failure even with the correct password.
Settings → Network and internet → Wi-Fi → Manage known networks → select the network → Properties → Wi-Fi security type → confirm it matches what the router is set to. On Windows 11, this is often set automatically, but manually checking and correcting it resolves cases where the stored type doesn’t match the current router configuration.
Fix 5: MAC Address Filtering
Some routers have MAC address filtering enabled — only devices with pre-approved hardware addresses are allowed to connect. From Windows’ perspective, MAC filtering rejection looks identical to a wrong password: the connection fails after authentication with the same error message.
The giveaway: the password works on a phone you’ve connected before but fails on this Windows machine that hasn’t connected to this router previously. The phone’s MAC address is on the approved list; the PC’s isn’t.
Find the PC’s Wi-Fi MAC address: Command Prompt → ipconfig /all → look at the Wi-Fi adapter section → “Physical Address” (format XX-XX-XX-XX-XX-XX). Log into the router admin panel → find MAC filtering settings → add this address to the allowed list.
Fix 6: Credential Manager Cleanup
Windows stores Wi-Fi credentials in both the network profile and in Windows Credential Manager. When these two become inconsistent — old credentials stored in one but not the other — authentication can fail mysteriously. Clearing the old credentials forces fresh re-entry.
Search “Credential Manager” in Start → Windows Credentials tab → look for any entries related to your Wi-Fi network → Remove → confirm. Then attempt the Wi-Fi connection again. This is less common than the profile forget/reconnect approach but resolves the specific case where forgetting the network didn’t clear all stored authentication data.
Enterprise Networks: 802.1X Authentication
Corporate, university, and some hotel Wi-Fi networks use 802.1X enterprise authentication rather than standard WPA2 with a shared password. For these networks, the “password” is your organisational username and password — not a static shared key. An incorrect password error on an 802.1X network usually means the credentials expired (after a mandatory password change), the certificate expired, or the enterprise authentication server rejected the login.
On 802.1X networks: forget the network and reconnect. Windows prompts for enterprise credentials separately from a WPA2 shared password prompt. Enter your current domain username and password. If the network requires a certificate rather than credentials, IT needs to provision the certificate to the device — personal machines often can’t complete 802.1X authentication because they lack the required enterprise certificate.
WPS as an Alternative
If the password method continues failing and the router supports WPS (Wi-Fi Protected Setup), using the physical WPS button on the router bypasses password entry entirely. Put the router into WPS mode (press the WPS button), then on Windows: Wi-Fi settings → click your network name → “Connect using WPS” (if this option appears) → Windows connects automatically.
WPS is disabled on some routers due to known security vulnerabilities in the PIN implementation. If the WPS button press doesn’t trigger connection, check whether WPS is enabled in the router admin settings. The push-button WPS method (as opposed to PIN-based WPS) is considered secure and is the recommended way to use WPS when it’s needed as a fallback.
Our guide on Wi-Fi keeps disconnecting covers the network adapter and driver causes that produce connection instability after successfully connecting — a related problem that shares several of the driver and profile fixes. For the network stack reset that’s covered briefly above, our DNS and network connectivity guide covers the full command sequence and its effects. Microsoft’s Wi-Fi troubleshooting documentation covers WPA3 compatibility requirements for specific Windows 11 versions and the known driver compatibility issues for Intel and Qualcomm adapters.
DHCP Server Exhaustion vs Password Error
A router whose DHCP pool is full — all IP addresses have been assigned to devices (including some that haven’t connected recently) — will fail connections in a way that produces the same “Can’t connect to this network” error as a wrong password. The device successfully authenticates with the correct password, but then can’t get an IP address, and Windows reports the whole connection as failed.
Distinguish this: if the password is definitely correct and other devices can still connect (particularly newer ones that weren’t there before), the DHCP pool might be full of old lease entries. Restarting the router clears the DHCP lease table and typically resolves this immediately — all old leases are cleared and addresses become available again. Alternatively, check the router admin panel → DHCP lease table → confirm there are addresses remaining in the pool. Routers with small DHCP pools (configured for 10 or 20 devices on networks with 25+ connecting devices) run into this regularly.
Frequency Band Connection Failure
Dual-band routers broadcast both 2.4 GHz and 5 GHz bands, sometimes with the same SSID (network name). Windows attempts to connect to whichever frequency it detects with better signal at that moment. If the 5 GHz connection fails (due to a driver limitation or router configuration) but 2.4 GHz works, Windows may report the password as wrong because its connection attempt to the 5 GHz band failed — even though the 2.4 GHz band would accept the same password.
Test: if the router broadcasts separate SSIDs for 2.4 GHz and 5 GHz (sometimes labelled as “NetworkName” and “NetworkName_5G”), try connecting to each one separately. If one band accepts the connection and the other doesn’t, the driver has a band-specific issue. Updating the Wi-Fi driver typically resolves 5 GHz connection failures that the 2.4 GHz band doesn’t experience.
Router-Specific Password Character Restrictions
Some routers have undocumented restrictions on which characters can be used in Wi-Fi passwords — certain special characters that are valid in Wi-Fi security standards cause the router’s firmware to reject them, producing an authentication failure that looks like the wrong password from the client side. This is a router firmware bug rather than a Windows issue.
If the Wi-Fi password contains characters like $, &, @, %, or very long passwords (over 40 characters), try changing the router password to a simpler 20-character alphanumeric password and reconnecting. If this allows Windows to connect, the special character or length was the issue. Update the router firmware if available — these character restrictions are often fixed in firmware updates. As a long-term solution, a clean alphanumeric password avoids the router compatibility issue while still being secure at appropriate lengths.
VPN and DNS Resolver Interference With Wi-Fi Authentication
Some VPN applications and DNS resolver applications install Windows filter drivers that intercept network traffic at a low level. In rare cases, these drivers interfere with the WPA2/WPA3 authentication handshake — the authentication fails not because the password is wrong but because the filter driver is intercepting and corrupting packets during the authentication process.
Test: temporarily disable or uninstall any VPN applications and DNS resolver tools (NextDNS, Pi-hole client, AdGuard DNS) and attempt the Wi-Fi connection. If the connection succeeds without these applications, their network filter drivers were interfering. Reinstalling the applications after the connection is established allows them to configure themselves correctly now that the base network connection is working. Some applications need to be re-installed after a network connection is established rather than before — this is particularly common with corporate VPN clients that perform initial configuration against a connected network.
Checking the Event Log for Connection Failure Details
Windows captures detailed Wi-Fi authentication logs in Event Viewer. After a failed connection attempt: Event Viewer → Applications and Services Logs → Microsoft → Windows → WLAN-AutoConfig → Operational. Look for “Failure reason” in the most recent Failure events. The reason codes distinguish between password failure (authentication failed due to wrong credentials), DHCP failure (authentication succeeded but IP assignment failed), and protocol failures (WPA3 handshake failed due to driver incompatibility).
This five-minute diagnostic takes “can’t connect despite correct password” from a vague description to a specific failure mode — saving the time of working through all possible fixes when the event log points directly at the one that applies. A reason code indicating DHCP failure points at the router; a reason code indicating authentication protocol failure points at the driver; a reason code indicating RADIUS rejection (on enterprise networks) points at the authentication server credentials.
One final practical note: if a Windows machine consistently can’t connect to a specific router while every other device connects fine — including after trying all the above fixes — the router and the Windows Wi-Fi adapter may have a specific compatibility issue. Some router firmware versions have known incompatibilities with specific adapter drivers. Checking the router manufacturer’s release notes for the current firmware version (available in the router admin panel) sometimes reveals Wi-Fi authentication fixes with specific device mentions. A router firmware update, when available, is worth trying when all client-side fixes have been exhausted and the problem is clearly specific to this particular combination of router and Windows machine. Our guide on WiFi Password Not Working in Windows 11 covers an adjacent issue.
