Advertisement

Intel AX201 Wi‑Fi forgets password after reboot: fix it

If your Intel AX201 keeps asking for the Wi‑Fi after every restart, the adapter may be fine. The real problem is often a missing or corrupted Windows saved network profile, auto-connect failure, or a router security mismatch. Start by checking what Windows stored.

Windows 9 min read

If your Intel AX201 laptop keeps asking for the Wi‑Fi password after every reboot, the adapter usually isn’t forgetting it on its own. In Windows, this problem more often means the Wi‑Fi profile is missing or corrupted, auto-connect is failing at startup, or the router’s security settings no longer match what Windows saved. Start by checking whether the profile is stored, then remove and re-add the network, and only move on to the driver or router once you know which side is failing.

Symptom: what this usually looks like

What you usually see is simple: the laptop connects after you type the password, but Windows asks again after a reboot, as if it has never seen the network before. Sometimes the network name still appears in the saved list, but the sign-in prompt comes back on the next startup anyway.

That pattern usually points to one of three things: Windows lost the profile, Windows kept the profile but cannot reconnect cleanly on boot, or the router security settings no longer line up with the saved connection. The AX201 is often just the adapter that exposes the problem, not the root cause.

A useful clue is whether the issue happens only after a cold reboot. If it reconnects fine after sleep, but not after a full shutdown and power-on, Fast Startup or adapter power management is more suspicious than the password itself.

Before you start

Use this as a quick scope check before you change anything:

  • You need access to the Windows account that normally connects to the Wi‑Fi.
  • If this is a work or school laptop, a policy may rewrite the wireless profile after sign-in or after reboot.
  • If the same SSID is used on multiple routers or access points, make sure you are testing the exact network you expect.
  • If the laptop can still connect manually after reboot, stop treating this like a dead adapter problem and work through the profile and startup checks first.

If the network is managed by an employer, school, or MDM policy, some local changes may be overwritten again. A clean profile test is still useful, but the fix may need to happen through policy rather than on the device itself.

Check whether Windows is actually saving the profile

Before you touch the driver, confirm that Windows really has a saved Wi‑Fi profile for the network. A network can appear in the list and still have a broken or duplicated profile behind it, so the first job is to check what Windows stored.

  1. Open Wi‑Fi settings and look for the network under your saved or known networks.
  2. Check whether it is set to connect automatically.
  3. If the network does not appear in the saved list, Windows is not preserving the profile.
  4. If it appears more than once, or you suspect an old entry is hanging around, remove the stale copy before you do anything else.

You can also check from the command line if you want a clean inventory of saved profiles.

Command Prompt
netsh wlan show profiles

If the network is missing from that list after you have used it before, the problem is on the Windows side, not the router side. If it is listed but keeps coming back wrong after a reboot, that usually means profile corruption, a duplicate saved profile, or a policy that is rewriting the connection settings.

Fixes to try in order

Start with the least disruptive fix: forget the network, then add it back cleanly. That clears out a damaged profile without wiping the rest of the machine’s network history, and it often fixes the repeated password prompt on its own.

  1. Open the Wi‑Fi list and choose Forget for the problem network.
  2. Reconnect to the same SSID and enter the password again.
  3. Make sure Connect automatically is turned on before you finish.
  4. Reboot and see whether Windows reconnects without asking again.

If it still prompts, check whether Windows has stored a stale credential as well. Some setups keep an old Wi‑Fi or generic Windows credential that gets reused after restart.

Settings path
Control Panel > Credential Manager > Windows Credentials

Remove entries that clearly belong to the problem network, then reconnect once more. If the prompt disappears after that, the issue was probably a stale credential rather than an AX201 driver problem.

Next, check the settings that can make Wi‑Fi look fine until the next reboot. In Device Manager, open the Intel AX201 adapter properties and look for the Power Management tab if it is present. If Windows is allowed to turn off the device to save power, clear that option and test again.

If the problem happens after a full reboot but not after sleep, turn Fast Startup off once and test a real shutdown and power-on cycle. Fast Startup can preserve part of the previous session, and that sometimes leaves Wi‑Fi in a bad state on the next boot. If the password stops reappearing after that change, you have a startup-state problem, not a password problem.

If none of the above changes anything, a driver reinstall or rollback is worth trying, but only after you have confirmed that the profile and credentials are clean. Reinstalling the Intel AX201 driver makes sense when the timing points to a reconnect bug, when Device Manager shows errors, or when the problem began right after a driver update. It is much less likely to help if Windows is clearly saving the wrong profile or the router is refusing the saved connection.

If you roll back the driver, do it only when the issue started after a recent update and you have a reason to think the older version behaved better. That gives you a way back if the newer driver is the one causing the startup problem.

A network reset makes sense when several networks are broken, when the profile keeps corrupting, or when normal reconnect fixes do nothing. Skip it if the problem is limited to one SSID and you have not checked the router security mode yet.

When the router or policy is the real problem

If Windows looks normal but the prompt keeps coming back, check the router next. A security-mode mismatch is a common cause. For example, if the router was changed from WPA2-Personal to WPA3-Personal, or to a mixed WPA2/WPA3 mode, some laptops will behave badly until the profile is rebuilt.

Router-side filtering can also make the laptop look like it forgot the password when the real issue is that the router no longer accepts the device cleanly. MAC filtering, access control lists, and similar allow-list features can break reconnects after a reboot, especially if the router is expecting a different device identity than the one Windows is presenting.

Managed devices add another layer. If this laptop belongs to an employer or school, policy can rewrite wireless settings after sign-in or after reboot. That is a strong clue when the network works briefly, then reverts, or when another account on the same PC behaves differently.

A simple separation test helps. If the network fails on this laptop but connects normally to other devices on the same router, the router may still be fine and the issue is more likely local profile corruption or policy. If multiple devices are being prompted again, look harder at the router security mode and the saved network configuration.

How to tell what kind of failure you have

The pattern usually tells you where to look next.

  • If the network works after manual connection but fails only after cold boot, suspect Fast Startup, power management, or a damaged profile.
  • If the network name is saved but the password prompt returns anyway, suspect a stale credential, duplicate profile, or security mismatch.
  • If the problem affects only one account on the PC, suspect profile corruption or policy tied to that account.
  • If the adapter shows repeated Device Manager errors or disappears across several networks after a clean reinstall, the issue is more likely driver-related, and hardware is only a later possibility.
  • If only this laptop has trouble but other devices are fine, the router may be innocent and the fault may sit in Windows, the profile, or device policy.

In practice, I would only blame the AX201 hardware itself after the profile has been rebuilt, the router settings have been checked, and the driver still misbehaves across more than one network.

Conclusion

If you want the shortest path, start with the profile and auto-connect settings, then check Fast Startup and power management, and only then move to the AX201 driver or the router. If the same problem comes back after a clean profile rebuild and the router settings look normal, the next step is usually policy or a deeper Windows profile issue, not random hardware failure.

Frequently Asked Questions

Is the Intel AX201 itself usually the cause?

Usually not. A repeated Wi‑Fi password prompt after reboot is more often a Windows profile, startup, or router-security problem than a bad Intel AX201 chip, especially if the network still works when you connect manually.

Should I reset the network right away?

No. A network reset is better saved for when simpler fixes fail, because it removes useful saved profiles and settings. Start with forgetting the network, checking auto-connect, and cleaning up saved credentials first.

Could Fast Startup really cause this?

Yes. Fast Startup can leave Wi‑Fi in a bad state across shutdown and boot, so the adapter comes up poorly and Windows asks for the password again. Turning it off is a reasonable test if the issue only happens after reboot.