Advertisement

Intel AX201 Wi‑Fi stops working after driver update

If your Intel AX201 stopped working right after a driver update, start with Device Manager and rollback before trying anything else. From there, decide whether you need a clean reinstall, a Windows service check, or a closer look at BIOS and hardware.

Windows 7 min read
A technician works inside an open laptop with tools beside it.

If your Intel AX201 stopped working after a driver update, start by checking whether the adapter still appears in Device Manager. If Windows offers rollback, use it first. If rollback isn’t available, remove the bad driver and reinstall a known-good Intel or OEM package. If the adapter has vanished completely, treat it as a deeper device, BIOS, or firmware problem instead of adding more driver updates.

What you may see

The failure often appears right after a Wi‑Fi driver update. The Wi‑Fi option disappears, Device Manager shows an error on the adapter, or the laptop falls back to USB tethering or Ethernet while Wi‑Fi will not connect.

A bad AX201 update usually shows up in one of two ways. Windows still sees the adapter but reports an error code, or the adapter is missing from Device Manager. That split matters. The first case usually points to a driver problem, while the second can point to hardware, BIOS, or firmware trouble.

Before you start

  • Use a Windows account that can open Device Manager and install drivers.
  • If the machine is already online through Ethernet or USB tethering, keep that connection available. You may need it to download a replacement package before you remove anything.
  • Check whether the AX201 appears in Device Manager before changing anything else.
  • If the adapter is present, note whether Windows shows an error code. Intel guidance in the retrieved material calls out Code 10, 22, 28, 31, 43, and 45 as signs to test with the OEM driver.
  • If the adapter is missing, skip the rollback path and go straight to the missing-device checks later in this article.
  • If you can get online, use Windows Update history, Device Manager, or your laptop maker’s support page to find the last working version before you install anything new again.

If Windows still sees the adapter, roll back the driver

This is the fastest recovery path when the AX201 still appears in Device Manager. If Windows kept the previous package, rollback can restore the last working state without a full reinstall.

  1. Open Device Manager.
  2. Expand Network adapters.
  3. Right-click Intel(R) Wi-Fi 6 AX201.
  4. Open Properties.
  5. Go to the Driver tab.
  6. Select Roll Back Driver if Windows lets you click it.
  7. Restart the laptop and test Wi‑Fi again.

If Wi‑Fi comes back after the restart, stop there and avoid stacking more updates on top right away. If the button is missing or greyed out, Windows no longer has an older package to restore, so move to a clean reinstall.

If rollback is available but the adapter still fails after restart, the current package is still the problem. Replace it with a known-good Intel or OEM driver instead of trying another random update.

If rollback is missing, remove the bad driver and reinstall a known-good package

When Roll Back Driver is unavailable, treat this as a clean reinstall job. On most laptops, the OEM package is the safer first choice because it is tuned for that model and BIOS combination. Intel’s generic package is still worth trying if the laptop maker tells you to use it.

  1. Download the current Wi‑Fi driver for your exact laptop model from the laptop maker’s support page, or download the current Intel wireless package if your vendor directs you to Intel.
  2. Save the installer locally.
  3. Open Device Manager, right-click the AX201, and choose Uninstall device.
  4. If Windows shows a box to delete the driver software for this device, use it only when the replacement installer is already saved on the machine.
  5. Restart the PC.
  6. Install the known-good Intel or OEM package you saved.
  7. Restart again if the installer asks for it.

Intel community replies in the retrieved material also point people with Code 10, 22, 28, 31, 43, or 45 toward OEM drivers first. That matches what I’d do on a preinstalled laptop adapter.

If the OEM package installs but Wi‑Fi still fails, check Windows Update history next and compare it with the laptop maker’s support page. That helps you find the exact version that was working before the failure, instead of guessing at versions.

If the adapter still exists but Wi‑Fi will not connect

A driver update can also disturb settings around the driver rather than the driver itself. After you confirm the adapter is present, check the Wi‑Fi service and the adapter’s power and advanced settings before you assume the hardware is bad.

  1. Open services.msc and make sure the WLAN AutoConfig service is running. If it is stopped, start it.
  2. In Device Manager, open the AX201 Properties page and check the Power Management tab. If Windows is allowed to turn off the adapter to save power, clear that option.
  3. On the Advanced tab, look for power-saving, preferred band, and roaming settings. Restore recent changes first, then return them to the vendor default if you know what was changed.
  4. Reconnect to Wi‑Fi and test again.

If these settings were the problem, the adapter should start behaving normally without another driver change. If they were already at default and Wi‑Fi still fails, the driver or the device itself is more likely at fault.

If the adapter disappears, or reinstalling fails again

If the AX201 is no longer visible in Device Manager, stop treating this like a simple driver update problem. That can mean the device is disabled deeper in the system, the BIOS is no longer exposing it, or the hardware has become unstable.

At that point, try BIOS or firmware updates only if the laptop maker explicitly lists a fix for wireless detection or AX201 stability. If the vendor’s update path says nothing about wireless, do not treat a BIOS flash as a first-line fix.

System Restore is the other fallback worth trying when the timing is clean and the adapter vanished or reinstalling fails. Use it only if you have a restore point from before the driver update. It is a blunt rollback, so it makes sense when the last known good system state is still available.

If the adapter is present but repeated clean installs still end in Code 10 or Code 43, the update may have exposed a hardware fault rather than caused the whole problem by itself. That is the point where I’d stop chasing packages and escalate to the laptop maker or board vendor for service or replacement.

An open laptop is being repaired with the Wi‑Fi adapter area visible.

Verify the fix

After the recovery step, confirm three things: the AX201 is visible in Device Manager without an error code, the Wi‑Fi option is back in Windows, and you can connect to a normal access point.

If you had a previous error code and it is gone after rollback or reinstall, that is a good sign the driver path worked. If the adapter shows up but the code returns after every reinstall, the issue is no longer behaving like a routine driver breakage.

Conclusion

If rollback worked, keep the working package and avoid another driver chase for now. If the AX201 still disappears or keeps returning Code 10 or Code 43 after a clean reinstall, escalate to BIOS, System Restore, or hardware service instead of repeating the same install cycle.

Frequently Asked Questions

Do I need to reset network settings if the AX201 stopped working after a driver update?

Usually not first. A network reset can help after broader Windows networking damage, but if the failure started after the driver update, rollback or a clean driver reinstall is the faster and safer path.

What if Windows keeps reinstalling the broken AX201 driver?

Then Windows Update is probably reapplying the same package. Restore the known-good driver from the OEM support page or Windows Update history, and avoid another generic update until the stable version stays put after a reboot.

Sources