Wi-Fi repeatedly asking for the password on Windows 11 — reconnecting every time you wake the laptop, every morning when you sit down at your desk, or every few hours with no pattern — is different from a one-time password prompt. The one-time prompt is usually just a forgotten network. Repeated prompts mean something is actively breaking and re-establishing the connection. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The most reliable first fix: forget the network completely and reconnect fresh. Wi-Fi icon → click the arrow next to your network name → Forget → wait 10 seconds → click the network name → Connect → enter the password. This creates a clean network profile, and for many people this is the entire fix. The stored profile was corrupted or outdated and Windows kept failing to reconnect with it, prompting for re-entry each time.
Understanding the Pattern
Repeated password prompts after wake from sleep are almost always power management cutting the Wi-Fi adapter. The adapter loses its connection during sleep, tries to reconnect on wake, and fails — Windows then prompts for credentials because it treats the failed reconnect as a new connection attempt.
Repeated prompts at random intervals without sleep are usually one of: adapter power management still (Windows powers it down briefly during low-activity periods), a driver issue, or a router authentication mismatch.
Prompts every single time you restart, but the connection works fine once entered: the credential isn’t being saved. This is a separate issue covered in Fix 5.
Fix 1: Disable Adapter Power Management
Device Manager → Network Adapters → right-click the Wi-Fi adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also: Control Panel → Power Options → your active plan → Change plan settings → Change advanced power settings → Wireless Adapter Settings → Power Saving Mode → change to “Maximum Performance.”
Both settings together. The first prevents Windows from directly cutting power to the adapter; the second prevents the wireless subsystem from reducing the adapter’s activity during low-use periods. After applying both, put the laptop to sleep and wake it — if the password prompt stops appearing, power management was the cause.
Fix 2: Update the Wi-Fi Driver
A buggy driver version — particularly common after Windows updates that replace manufacturer drivers with generic Intel or Qualcomm versions — can cause the adapter to lose its authentication state and prompt for re-entry. This usually manifests as prompts that appear on the same schedule as when Windows runs automatic maintenance tasks, or immediately after the laptop reconnects to the network after a brief interruption.
Download the Wi-Fi driver from the laptop manufacturer’s support page (not from Windows Update or Device Manager’s automatic search). The manufacturer-specific driver for Intel, Qualcomm, Realtek, or MediaTek adapters handles credential persistence and reconnection more reliably than generic versions.
If prompts started after a recent update: Device Manager → Wi-Fi adapter → Properties → Driver → Roll Back Driver first, then test before downloading a new driver.
Fix 3: Network Profile Corruption
Beyond just forgetting and reconnecting: network profiles are stored in the registry and in the Wireless Profiles folder. When either location has a corrupted entry for a network, Windows may reconnect but fail to authenticate using the stored key, prompting for the password.
Delete all saved profiles for the network and recreate from scratch. Administrator Command Prompt:
netsh wlan delete profile name="[YourNetworkName]"Replace [YourNetworkName] with the exact SSID of your network. Reconnect manually and re-enter the password. The fresh profile stores correctly and subsequent reconnections use the saved credential without prompting.
Fix 4: Router WPA3 Compatibility
Modern routers operating in WPA2/WPA3 mixed mode or WPA3-only mode sometimes fail to maintain authentication state with certain Windows Wi-Fi adapters. The connection re-establishes after prompting, works for a while, then fails to re-authenticate when it tries to renew the connection — causing another prompt.
Test: log into your router admin panel (typically 192.168.1.1) → Wi-Fi settings → security settings → change from WPA3 or WPA2/WPA3 mixed to WPA2-Personal only → save. If prompts stop, WPA3 compatibility is the issue. Update the Wi-Fi driver (Fix 2) for a more permanent fix, then switch the router back to WPA3 after the driver update.
Fix 5: Credential Not Being Saved
If the password is always prompted at every connection but works correctly when entered, Windows isn’t saving the credential — it connects fine but doesn’t store the password for future reconnections. This happens when the network is connected without checking “Connect automatically” or when the user account doesn’t have write access to the credential store.
Re-connect and explicitly check “Connect automatically” and “Remember my credentials” during the connection prompt. Also check Windows Credential Manager (search in Start) → Windows Credentials → look for any entries for your Wi-Fi network — if there are entries with old or incorrect credentials, remove them and let Windows create fresh ones on the next connection.
Fix 6: Fast Startup Interaction
Windows Fast Startup saves the kernel session to disk during shutdown. If the Wi-Fi adapter’s connection state is saved with Fast Startup and the router has restarted or changed its configuration during the shutdown period, the restored connection state is invalid — Windows prompts for the password because the saved connection state no longer matches the router’s current authentication session.
The tell: prompts appear specifically after a full shutdown and startup (not after sleep, and not after restart — only after shutdown + start). Disable Fast Startup: Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup.” After disabling, the adapter fully reinitialises on each boot and re-authenticates cleanly with the router.
Fix 7: Network Stack Reset
For persistent prompts that don’t respond to the above fixes, a full network stack reset clears accumulated state that may be causing authentication failures:
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsAdministrator Command Prompt → run all three → restart → reconnect to Wi-Fi with the password → observe over the next day whether prompts recur.
Corporate and 802.1X Networks
On corporate networks using 802.1X authentication (where you log in with work username and password rather than a shared Wi-Fi key), password prompts appear when the machine certificate expires, the authentication server rejects the stored credentials, or IT changes the authentication configuration. These aren’t fixable with the approaches above — the credential is being correctly rejected by the authentication server, and IT needs to renew the certificate or update the authentication configuration.
The indicator: the prompt asks for a username and domain, not just a password. Report to IT with the exact error message from the connection attempt — the error message identifies whether it’s a credential, certificate, or server configuration issue.
Our guide on Wi-Fi keeps disconnecting covers the related disconnection pattern — some of the same power management and driver causes apply to both, and fixing one sometimes resolves the other. For the router-side WPA3 configuration, our Wi-Fi not working guide covers security protocol settings in the router admin panel. Microsoft’s Windows 11 wireless networking documentation covers the WLAN AutoConfig event log and the credential profile XML format for advanced network profile management through Command Prompt.
Roaming Between Access Points
In homes and offices with multiple Wi-Fi access points (mesh systems, range extenders, or multiple routers) sharing the same SSID, Windows may prompt for a password when it switches between access points that have slightly different authentication configurations. If the access points use different security protocols (one is WPA2, another is WPA3), or if they have different pre-shared keys (misconfigured mesh network), Windows correctly rejects the stored credential for the new access point and prompts for re-entry.
Mesh systems should be configured to use identical security settings across all nodes — same protocol (WPA2 or WPA3, not mixed between nodes), same password, and seamless roaming enabled. If the repeated prompts correlate with moving around a space (near one router vs another), a misconfigured multi-AP setup is the likely cause. Check each access point’s security settings for consistency.
Hidden SSIDs and Authentication Issues
Networks configured with hidden SSIDs — where the network name isn’t broadcast and must be manually entered — sometimes cause repeated password prompts. Windows needs to actively probe for hidden networks, and the probe-response-authentication sequence is more complex than visible network connections. When the authentication for a hidden network fails to persist correctly (a more common issue with hidden SSIDs than visible ones), prompts recur.
Test: temporarily enable SSID broadcast on the router and reconnect Windows to the visible network. If prompts stop, the hidden SSID configuration was the cause. Hidden SSIDs provide minimal security benefit (the SSID is visible to network scanners anyway) — switching to a visible SSID with a strong password is more reliable and doesn’t reduce meaningful security.
Checking WLAN-AutoConfig Event Log
Every Wi-Fi authentication event is logged in the WLAN-AutoConfig operational log. Event Viewer → Applications and Services Logs → Microsoft → Windows → WLAN-AutoConfig → Operational. Look for Disconnection events and Failure events timestamped just before each password prompt appeared.
The “Reason” field in these events specifies why authentication failed: “Association failure” (radio-level connection problem), “Authentication timeout” (the router took too long to respond), “4-way handshake failure” (authentication key exchange failed — often WPA3 compatibility), or “RADIUS rejection” (on enterprise networks, the authentication server rejected the credentials). Each reason maps to a different fix, making this log the most efficient diagnostic for persistent repeated authentication failures.
DHCP Lease and Authentication Link
An unusual but real cause: when a Wi-Fi DHCP lease expires and renewal fails, Windows sometimes treats the re-authentication as a new connection requiring credentials — even though the stored Wi-Fi credentials are correct. This happens because Windows internally disconnects and reconnects when the IP address becomes invalid, and this reconnection triggers the credential prompt.
Check whether prompts occur at predictable intervals (matching the router’s DHCP lease time — often 24 hours or 1 hour on guest networks). If so, the DHCP renewal is failing. Fix: set a static IP for the connection (Settings → Network and internet → Wi-Fi → your network → IP settings → Manual) to eliminate DHCP renewal as a trigger. This is a diagnostic workaround — the underlying DHCP renewal failure should also be investigated by checking the router’s DHCP configuration.
Windows Hello and Wi-Fi Authentication
On machines using Windows Hello for Business, Wi-Fi authentication may integrate with Windows Hello’s certificate store for some enterprise Wi-Fi configurations. When the Windows Hello certificate expires or becomes invalid (after domain changes, certificate rotation, or hardware changes), Wi-Fi authentication fails and prompts appear even though the Wi-Fi password itself hasn’t changed.
This is an enterprise-specific scenario that requires IT intervention — the Windows Hello certificate needs to be renewed or the Wi-Fi authentication policy needs to be updated to use an alternative authentication method. Users experiencing this on personal machines (no Windows Hello for Business, just a standard Windows Hello PIN) shouldn’t encounter this specific scenario, as consumer Windows Hello doesn’t integrate with Wi-Fi authentication in this way.
Dual-Band Network and Band Steering
Some routers with dual-band (2.4 GHz and 5 GHz) “band steering” — which tries to move devices to the optimal band automatically — can cause repeated authentication prompts if the band switch doesn’t preserve the authentication state correctly. Windows authenticates on the 5 GHz band, the router steers it to 2.4 GHz, and the authentication for the 2.4 GHz band isn’t transferred from the 5 GHz session — prompting again.
Test: disable band steering in the router admin panel (usually under Wi-Fi → Band Steering or Smart Connect) and create separate SSIDs for 2.4 GHz and 5 GHz. Connect Windows explicitly to one band and observe whether prompts stop. If they do, band steering was causing the authentication disruption. Most users connecting a laptop that stays in one location don’t need band steering — a static band connection is more stable and eliminates the steering-related authentication interruptions.
One observation from working through this problem: the “forget and reconnect” fix resolves the immediate symptom but doesn’t identify the root cause. If prompts resume after a few days or weeks, the root cause is still active. The WLAN-AutoConfig event log provides the most direct path to understanding why the authentication is failing — reviewing those logs after the next prompt appears (before dismissing or entering the password) captures the specific failure mode that guides the permanent fix.
For laptops that travel between different networks regularly — home, office, coffee shops — accumulated network profiles for dozens of old networks can sometimes interfere with new connection authentication. Running netsh wlan show profiles lists all saved Wi-Fi profiles. If there are 50+ profiles for networks the machine no longer visits, deleting old ones reduces the chance of profile conflicts: netsh wlan delete profile name="OldNetworkName" removes individual profiles. Clearing all profiles periodically (especially for a laptop with years of accumulated connections) is good maintenance that prevents authentication issues from compounding over time. Related: WiFi Keeps Asking for Password on Windows 11.
