Intel Wifi 6 Ax201 This Device Cannot Start. (code 10)

[Florian Peitz]

TheBluetooth also stopped working after a while and disappeared from the Action Center. I did a bit of digging and found out that it's the AX201 wireless network card inside the laptop that is of very poor quality and causing the issue.

I took my laptop to a local computer shop to get the card replaced and the guy said that it's a common issue with this network card. However, he uninstalled an Unknown device under the Other devices section in the Device Manager, restarted the laptop, and the Wi-Fi and Bluetooth was back (like a miracle). Still, I still wanted to get the network card replaced, but he said that doing so may not resolve the issue in the long run. He recommended that removing the network card, cleaning it a bit, and reinstalling may be a better option for now, which he did.

When you answered the question about trying different networks, you responded "No"; does it mean that you have not tried other networks? If so, are you able to try using other networks to check if the issue persists?

I also would recommend performing a clean installation of the latest ASUS driver; for your unit, version 22.130.0.5. Be careful not to install the driver 3.00.01.1264, as this one is for a MediaTek WLAN device. Remember that there are two types of drivers, generics provided by Intel and Equipment Manufacturer drivers, that are customized to work with each specific system. The best thing to do is to use the drivers provided by the system manufacturer (OEM).

Can you please elaborate as to why you don't recommend installing the MediaTek WLAN device? Is it a Wi-Fi driver similar to Intel AX201? If so, why shouldn't I switch to this one provided the Intel one is being so problematic.

As I mentioned, the Original Equipment Manufacturer (OEM) drivers are customized to work with each specific system. The one I suggested is the latest version that Asus customized to work with your system.

It is important to mention that the generic drivers from Intel have not been validated for your specific PC and thus can exhibit issues specific to your system. If problems are seen after installing the latest Intel driver, restore your original experience by reinstalling the latest graphics driver directly from ASUS.

Remember that performing a clean installation will delete any file from the previous driver version. Since you stated you tried this method, it would indicate that past ASUS drivers aren't installed on your system anymore.

Regarding your question about installing the MediaTek WLAN driver, remember that it is developed to work with their products. Based on the ASUS website states that the driver is customized to work alongside the AW-XB468NF or MT7921LEN MediaTek adapters. Installing driver designs for different products may cause some problems.

When the driver stopped working again, I opened Device Manager to find there was this AnchorFree Tap-Windows-Adapter V9 installed (this driver wasn't there before). I Googled about it and found that this driver was causing internet connection to stop among some users, so I uninstalled it.

Then, after I performed a clean install of the AX201 driver, I was unable to upgrade to the latest driver version. When I'm trying to install 22.180.0, I'm getting the message that "One or more issues caused the setup to fail", and when I'm trying to install 22.170.0, it's telling me that a new version is already installed (screenshot of both attached).

Hello guys, I have a Samsung Galaxy Book2 Pro with this Wifi chipset ax211 160mhz and after months using it I got this error too, I spend all day thinking on Router, WANs, Drivers and nothing made any sense.

Ping tests just didn't work for no reason, 2.4G works, so I have another laptop, a Lenovo one with wifi chipset ax201 160mhz and everything was working with same router.

After all day testing and trying, I just thought taking the chipset from Lenovo and put on Samsung, so when I opened Samsung Book2 Pro I notice that is a board with Wifi, usb C ports, Hdmi and fan power supply and not just a Wifi card as other laptops. Dawnnn, the plan was failed.

But, when I was putting the plate and screws on Book2 Pro, I notice that was very weak and fragile so I tested the laptop loney, without usb dock, hdmi cable, just the laptop working on battery, and worked!

I started to think what could be and I remember that, by the morning I organized my cables and I was using 2 monitors, one on HDMI port on Laptop and other on HDMI port on USB dock, so I changed they to let the cable better organized.When I putted the **bleep** HMDI cable on HDMI laptop port the erros started to pop on ping test!

Putting like before the morning move, other monitor on laptop HDMI port that didn't happen. Could be two things, or the cable is so stretched that it's bending the board making the fail or the cable is a cheap one and maybe be doing some static over the board.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

So I had a related issue just now on Ubuntu 23.10 using the Beelink S12 Pro. I could not for the life of me get wifi or bluetooth to work. I tried all the logging commands you'll find while researching this topic and I kept seeing errors around missing firmware, my device was seeing either AX101 or a generic Intel Adaptor depending on which logs I checked. (Note from later, it appears I do actually have AX101, it is incredibly difficult to determine this from Beelink docs)

After way too many hours lost to this problem, I came to an understanding of what was going on and found a solution. I am leaving it on this thread for posterity in case anyone else finds themselves in a similar situation.

Essentially, what you need to know is that there are 2 major components at work here - the driver and the firmware. The driver is iwlwifi and the firmware is all the various .ucode files you'll find in /lib/firmware/

My understanding is that the driver has a number of pre-defined firmwares it looks for depending what adapter it detects. What's happening in this case is that the driver is detecting a relatively new adapter that doesn't have matching firmware in the linux-firmware package that is bundled with Ubuntu. You're gunna read a bunch of stuff about making sure your kernel is above 6.2, and maybe that's the case if you're using some old-ass kernel in 2023 but it's a red herring.

What you need to do is go to this page: and look for the linux-firmware package maintained by intel (iwlwifi/linux-firmware) and clone the git repo to your computer. For good measure in my own case, I also copied the latest release of the regular linux-firmware that wasn't on apt yet, but I believe that to be optional (this isn't on the intel page, you have to find it on google). There are 4 packages there, and I believe the backports one only to be necessary on older kernels, and fixes/next to be active development-related and unhelpful to us here.

From there, you'll find a section on the Intel page that has the command: cp iwlwifi-*.ucode,pnvm /lib/firmware/ followed by the instruction "load the driver". It's kind of cryptic and confusing exactly what to do, but basically all you need to do is cd into the git repo(s) you cloned and run that command as sudo overwriting all the intel firmware files in the /lib/firmware/ folder. I did the intel managed one first, then the official package as it seems much more recently maintained. Then reset your computer.

Second Edit: I'm back as I booted up the other day and my wifi was once again broken! It turns out even with the fix above Intel has shit support on linux for wifi 6. To determine if you have the same problem, check to see if your router is a wifi 6 router. If it is, run the following command and look for this error: Microde SW error detected. Restarting 0x0.

3a8082e126