Wi-Fi repeatedly asking for the password on Windows 11 — where you enter the password, connect, and then it asks again after a short time or after sleep — is different from a connection failure. The connection works; it just doesn’t stay authenticated. The stored credentials are either being discarded or failing on reconnection. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The most common causes are: the profile stored the wrong credentials (one typo during initial connection), Windows is forgetting the profile during sleep, or the router is rejecting re-authentication. Each has a different fix.
Start: forget and reconnect with the correct password
Settings → Network and internet → Wi-Fi → Manage known networks → find the network → Forget. This removes the stored profile entirely, including any wrong password that may have been saved. Reconnect fresh: enter the correct password → connect. Before entering: confirm the exact password on another working device or in the router admin panel. One wrong character creates the repeated-password-request loop.
After reconnecting: stay connected for 15 minutes including letting the screen go off once. If no password prompt after that test: the problem was a wrong stored password and it’s resolved.
Power management and re-authentication after sleep
If the password prompt appears specifically after waking from sleep or screen-off: Windows is suspending the Wi-Fi adapter during sleep and failing to re-authenticate when the adapter wakes. The authentication session on the router has expired during the sleep period and requires the password again.
Device Manager → Network Adapters → right-click Wi-Fi adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also: Advanced tab → Power Save Mode or Power Management Mode → set to Maximum Performance or “Disabled.” This keeps the Wi-Fi adapter active through sleep, maintaining the router authentication session.
WPA3 and re-authentication issues
WPA3 uses a different authentication protocol (SAE — Simultaneous Authentication of Equals) compared to WPA2. Some Windows 11 Wi-Fi drivers have intermittent SAE re-authentication failures — successfully connecting initially but failing to re-authenticate after sleep or after a certain time period. The symptom: password prompt after sleep specifically on WPA3 networks.
Test: in the router admin panel → Wireless settings → change from WPA3-Only to WPA2/WPA3 Mixed mode → reconnect on the Windows machine. In Mixed mode, the Windows adapter uses WPA2 authentication which is more reliably persistent. If the password prompt stops: the WPA3 re-authentication was the issue. Updating the Wi-Fi adapter driver from the laptop manufacturer’s site (manufacturer drivers have better WPA3 implementation than generic versions) resolves this properly without downgrading the router’s security mode.
DHCP lease and password prompt confusion
Some Windows 11 configurations show a password prompt when a DHCP lease fails to renew rather than when authentication actually fails. The lease renewal failure looks like an authentication failure to the user because the connection appears to drop and the Wi-Fi reconnects — sometimes showing the password entry screen as part of the reconnection UI flow, even when the password is still correctly stored.
Check: Settings → Network and internet → Wi-Fi → your network → IP settings → change to Manual → assign a static IP and DNS to eliminate DHCP renewal entirely. Alternatively: increase the DHCP lease time in the router admin panel from the default (often 1 hour) to 24 hours or longer. If the password prompts stop after this change: DHCP was the trigger, not actual authentication failure.
Random MAC address causing authentication issues
Windows 11’s random hardware address feature changes the device’s MAC address periodically for privacy. When the MAC changes: the router sees a new device and may require fresh authentication. If the network uses MAC-based authentication (common in corporate environments) or if the router has MAC filtering enabled: MAC rotation causes repeated authentication challenges.
Settings → Network and internet → Wi-Fi → your network → Properties → Random hardware addresses → change from “On” to “Off” for this specific network. With a stable MAC address: the router recognises the device consistently and doesn’t challenge for re-authentication after MAC rotation.
Network profile corruption
Beyond the UI-level “Forget” approach: administrator Command Prompt → netsh wlan delete profile name="NetworkName" → removes the profile completely. Then reconnect. The command-line deletion is more thorough than the Settings UI forget option, removing all registry entries associated with the profile rather than just marking it as forgotten.
Enterprise WPA2 Enterprise and certificate expiry
Corporate networks using WPA2 Enterprise (802.1X authentication) with certificates require a valid certificate on the device for authentication. When the certificate expires — annually in many organisations — Windows is prompted to re-authenticate each connection attempt. The password prompt is actually a credential prompt for the RADIUS server authentication, not the Wi-Fi password.
Check the certificate: certmgr.msc → Personal → Certificates → look for any expired or expiring certificates for the network connection. Contact IT to renew the certificate or re-enroll the device. This is a routine maintenance task in enterprise environments and isn’t a Windows problem — it’s certificate lifecycle management.
Our guide on Wi-Fi authentication error covers the WPA3 driver compatibility and WLAN event log error codes that help distinguish authentication type from DHCP failures. For the DHCP-specific scenarios, our IP address management guide covers static IP configuration and DHCP reservation setup. Microsoft’s Wi-Fi profile documentation covers the netsh wlan show profiles command for reviewing saved profile details and the XML export format that allows inspecting and editing saved credentials directly.
Stored credentials in Credential Manager
Windows stores Wi-Fi network credentials in two places: the WLAN profile (managed by Settings) and optionally in Credential Manager. Some network configurations create entries in both, and a mismatch between them causes authentication to fail repeatedly even when the correct password is entered.
Control Panel → Credential Manager → Windows Credentials → look for entries related to the Wi-Fi network (they may appear under the network name or under a Microsoft or domain entry). Remove any related to the problematic network → reconnect fresh. After clearing: the new connection creates a clean single set of credentials rather than conflicting sets in two locations.
Auto-connect behaviour and expiry
Settings → Network and internet → Wi-Fi → your network → “Connect automatically when in range.” If this is off: Windows prompts to connect (and show the password screen) every time the network is discovered. This looks like a “keeps asking for password” issue but is actually “keeps asking if you want to connect” — a different problem with a simpler fix: toggle “Connect automatically” on.
Also check: “Sign in info” setting in the network profile. Settings → Network → Wi-Fi → your network → Properties → scroll to “Sign in info” → if set to “Domain user account” instead of “Anyone” on a personal machine: the authentication expects domain credentials rather than the Wi-Fi password, producing a repeated authentication prompt even when entering the correct Wi-Fi password.
Router settings causing repeated authentication
Some routers have aggressive re-authentication intervals. A corporate or ISP-provided router might be configured to require fresh authentication every 30 or 60 minutes as a security measure. In the router admin panel → Wireless or Security settings → look for “re-authentication interval,” “key lifetime,” or “802.11r” (fast BSS transition) settings. If the re-auth interval is very short, increasing it reduces forced re-authentications for all connected devices.
Also: some routers have a “Band Steering” feature that moves devices between 2.4 and 5 GHz bands. The band switch causes a brief disconnection and reconnection that sometimes triggers the authentication UI. Disabling band steering (separate 2.4 GHz and 5 GHz SSIDs, or disabling band steering in router settings) eliminates band-switch-triggered authentication prompts.
Guest network password prompts
Guest networks often use a captive portal or time-limited authentication — designed for temporary access. Devices connected to a guest network regularly see password or authentication prompts because the guest access is intended to expire. Switching from the guest network to the main network (which uses persistent authentication) resolves repeated prompts that are actually working as designed for the guest network.
Third-party VPN and authentication interference
Some VPN clients modify Windows network authentication behaviour. A VPN that intercepts network authentication for its own purposes — particularly Always-On VPN configurations — can interfere with Wi-Fi password storage in ways that cause the profile to be treated as unauthenticated. Disconnecting or disabling the VPN before reconnecting to Wi-Fi confirms whether the VPN is the variable. For Always-On VPN: IT needs to configure the VPN policy to exempt Wi-Fi authentication from its interception, or explicitly trust the Wi-Fi network in the VPN client’s policy.
Windows Hello and network authentication
Windows Hello (PIN, fingerprint, face) manages certain credential operations. On machines with Windows Hello configured, Wi-Fi credential prompts may route through Windows Hello and appear as different, confusing UI flows compared to standard password entry. If the authentication prompt looks unusual or asks for something other than the Wi-Fi password: it may be requesting Windows Hello verification for a credential operation.
Complete the Windows Hello authentication (enter PIN, scan fingerprint) when prompted — this isn’t the Wi-Fi password prompt, it’s Windows verifying your identity to use stored credentials. If Windows Hello is not set up: Settings → Accounts → Sign-in options → set up PIN or biometric authentication, which resolves the “Windows Hello required” prompt that appears for credential operations on some corporate machines.
Profile export and inspection
Administrator Command Prompt → netsh wlan export profile name="NetworkName" folder="C:temp" key=clear → exports the Wi-Fi profile as an XML file including the stored password in plaintext. Opening this XML file confirms whether the correct password is stored in the profile. If the password shown doesn’t match the actual network password: the profile has the wrong credentials, and a forget-and-reconnect with the correct password is the definitive fix.
This command requires administrator rights and deliberately shows the password in cleartext — use in a private context and delete the exported XML after checking.
Multiple access points with the same SSID
In homes or offices with multiple access points (range extenders, mesh nodes) broadcasting the same SSID: different access points may have different passwords (if not properly configured to match). When the device roams from one access point to another, it uses the stored password from the first connection against the second access point which has a different password — authentication fails, password prompt appears.
Ensure all access points broadcasting the same SSID use identical passwords. In a mesh system: all nodes should be configured through a single management interface that enforces consistent password configuration across all nodes. Range extenders with independent setup sometimes have their own passwords that differ from the main router — update all to match.
The netsh wlan export command is genuinely useful as both a diagnostic (see if the stored password is correct) and as a fix path (once the correct password is confirmed, delete and re-import the profile with the correct credentials). For IT administrators managing multiple machines that all show the same password prompt issue: the profile export format is also the right mechanism for centrally distributing correct Wi-Fi profiles to all machines via Group Policy, ensuring consistent and correct authentication configuration across the fleet.
Mesh network password prompts — specific scenario
On a mesh system where the device is near the edge of the mesh (low signal from the nearest node), the mesh system may attempt to hand off the device to a different node. If the handoff (roaming) includes a re-authentication step rather than seamless transition: the password prompt appears during normal use without any obvious trigger. This is a mesh firmware issue — check for firmware updates on the mesh system, as fast roaming improvements are commonly patched. Also: configuring the mesh system to use a dedicated backhaul (wired or dedicated wireless backhaul) ensures smoother handoffs that don’t interrupt client authentication.
The core diagnostic question for this problem remains: does the prompt appear at a predictable time (after sleep, every 30 minutes, only when roaming between floors) or completely randomly? Predictable patterns point at power management, router re-auth intervals, or roaming. Random prompts point at profile corruption or DHCP failures. This simple pattern check directs the investigation to the correct fix category without needing to try all approaches. You might also run into Why WiFi Keeps Asking for Password on Windows 11.
For the most straightforward cases: forget the network, reconnect with the verified-correct password, disable adapter power management, and check random MAC is off for that network. These four steps take under 10 minutes and resolve the majority of repeated-password-prompt situations. The WPA3 re-authentication issue, DHCP-triggered prompts, and credential manager conflicts are for situations where those four steps have been applied and the prompt still recurs — they represent a smaller fraction of cases but are important to know when the basic fixes don’t hold. Related: WiFi Keeps Asking for Password.
