Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
8565 Discussions

Intel(R) Wi-Fi 6E AX210 160MHz not connect to wifi 6E 6 GHz

ychan1
Novice
73,188 Views

I am using MS window version 11 with Intel(R) Wi-Fi 6E AX210 160MHz (driver version: 22.80.1.1). I tried to connect to my wifi 6E (Asus Zenwifi ET8) with no success. Windows unable to see my 6E SSID. I can connect to my 2.4 and 5 GHz channel with no problem. My Samsung phone able to see my 6E SSID and connect to it with no problem. Is it a setting to enable to see 6 GHz channel or need new intel driver?

58 Replies
mailsanchu
Novice
20,758 Views

I actually raised a separate issue 

0 Kudos
TheEmrys
Beginner
17,788 Views
I am having the same issue. Device manager shows 6E but the 6ghz network doesn't show. It shows on my Pixel, 6 though. Drivers are up to date. 5g works fine
0 Kudos
TheEmrys
Beginner
17,788 Views
Router is an Asus AXE-GT-AXE11000.
0 Kudos
Luigi408
Novice
17,572 Views

My AX210 does not see 6E 160MHz (HE160) from my Unifi U6 Enterprise AP that is broadcasting at 160MHz at all.

I meet all the requirements from OS to Drivers but it only connects to 5GHz and NOT 6GHz at 160MHz. Am I missing something in order for this to work correctly? If not, Intel you guys need to fix this issue.

 

OS: Windows 11 - OS build: 22621.160

Driver: 22.140.0.3

6E Access Point: Unifi U6 Enterprise using the latest firmware updates.

 

Screenshot 2022-06-22 030239.pngScreenshot 2022-06-22 030221.pngScreenshot 2022-06-22 030208.pngScreenshot 2022-06-22 030344.png

0 Kudos
intc28665972
Beginner
17,435 Views

I'm experiencing a similar problem with the exact same setup that I believe might be related...

 

I cannot connect to my Asus Zenwifi ET8 on the 6GHz band when the SSID is hidden using my AX210 in Windows 11.

 

However, I have zero problems connecting on the 6GHz band when the SSID is NOT hidden using identical settings for everything.

 

Also, I have zero problems connecting on the 2.4GHz and 5GHz bands for both visible and hidden SSIDs using default settings for all of the hardware (except for disabling steering and roaming on the ET8 so I can rule out a weak signal, even though the ET8 and my WiFi antennas are about six feet apart).

 

There seems to be several critical and unresolved issues for the 6GHz band for this card. Has anyone been able rule out the card and/or drivers as the source of the problems by using hardware from different manufacturers?

 

I'm on Windows 11 21H2 (OS Build 22000.832), and have tried AX210 driver versions 22.0.1.5 (default with Windows), along with 22.140.0 and 22.150.0 (latest as of this writing). I have also tried the older 22.45.1.1 driver version recommended in other threads without any success.

 

The Asus Zenwifi ET8 is on firmware version 3.0.0.4.386_49873-g72159cc (latest as of this writing).

 

I'm including some debugging output from netsh:

 

Visible SSID (The operation was successful):

 

[0]1CC0.42AC::2022/08/05-18:49:56.914006700 [Microsoft.OneCore.NetworkingTriage.GetConnected]{"eventSource":"WiFi","interfaceGuid":"{fb902463-08d4-4831-bcf4-44db9d2c0282}","interfaceType":"WiFi","interfaceDescription":"Intel(R) Wi-Fi 6E AX210 160MHz","isWDI":true,"eventType":"Manual","isAUserLoggedIn":true,"ssid":"TEST NETWORK","authAlgo":"WPA3-Personal","cipherAlgo":"AES-CCMP","eapType":4294967295,"oneXAuthMode":"None","isHidden":false,"bssid":"7C:10:XX:XX:XX:XX","firstBSSID":"7C:10:XX:XX:XX:XX","wlanStatusCode":"0x0 = The operation was successful.","detailedStatusCode":"0x0 ( DOT11_ASSOC_STATUS_SUCCESS ))","firstDetailedStatusCode":"0x0 ( DOT11_ASSOC_STATUS_SUCCESS ))","assocDuration":125,"associationCount":1,"assocRestartCount":0,"authDuration":16,"authRestartCount":1,"rssi":-50,"signalQualityPercentage":88,"channelFrequency":6295,"channelNumber":0,"interferingAPCount":7,"totalVisibleAPCount":26,"apCountOnSSID":2,"apPhyType":"802.11ax","apMaxChannelWidth":20,"apDescription":"F832E4,506F9A","apManufacturer":"","apModelName":"BroadCom Chipset","apModelNum":"","rxRate":1500,"txRate":1500,"PartA_PrivTags":2048,"meta":{"provider":"Microsoft.OneCore.NetworkingTriage.GetConnected","event":"WiFiConnectedEvent","time":"2022-08-05T22:49:56.9140067Z","cpu":0,"pid":7360,"tid":17068,"channel":11,"level":5,"keywords":"0x400000000000"}}

 

Hidden SSID (The driver disconnected while associating):

 

[1]1CC0.6B58::2022/08/05-18:50:37.625450800 [Microsoft.OneCore.NetworkingTriage.GetConnected]{"eventSource":"WiFi","interfaceGuid":"{fb902463-08d4-4831-bcf4-44db9d2c0282}","interfaceType":"WiFi","interfaceDescription":"Intel(R) Wi-Fi 6E AX210 160MHz","isWDI":true,"eventType":"Profile","isAUserLoggedIn":true,"ssid":"TEST NETWORK","authAlgo":"WPA3-Personal","cipherAlgo":"AES-CCMP","eapType":4294967295,"oneXAuthMode":"None","isHidden":false,"bssid":"7C:10:XX:XX:XX:XX","firstBSSID":"7C:10:XX:XX:XX:XX","wlanStatusCode":"0x38002 = The driver disconnected while associating.","detailedStatusCode":"0x29 ( DOT11_ASSOC_STATUS_NO_AUTH_RESPONSE ))","firstDetailedStatusCode":"0x29 ( DOT11_ASSOC_STATUS_NO_AUTH_RESPONSE ))","assocDuration":10016,"associationCount":8,"assocRestartCount":0,"authDuration":0,"authRestartCount":0,"rssi":-76,"signalQualityPercentage":50,"channelFrequency":6135,"channelNumber":0,"interferingAPCount":4,"totalVisibleAPCount":26,"apCountOnSSID":1,"apPhyType":"802.11ax","apMaxChannelWidth":20,"apDescription":"F832E4","apManufacturer":"","apModelName":"BroadCom Chipset","apModelNum":"","rxRate":0,"txRate":0,"PartA_PrivTags":2048,"meta":{"provider":"Microsoft.OneCore.NetworkingTriage.GetConnected","event":"WiFiConnectedEvent","time":"2022-08-05T22:50:37.6254508Z","cpu":1,"pid":7360,"tid":27480,"channel":11,"level":5,"keywords":"0x400000000000"}}

0 Kudos
intc28665972
Beginner
17,113 Views

I'm not sure if the specific issue I am experiencing is substantially similar to the issue others are experiencing, or if I should start a separate thread.

 

https://community.intel.com/t5/Wireless/Intel-R-Wi-Fi-6E-AX210-160MHz-not-connect-to-wifi-6E-6-GHz/m-p/1406465#M42799

 

Could @AndrewG_Intel  or one of the other moderators please weigh in?

 

Also, could any of the moderators please give some sort of update on the status of these seemingly similar problems with the 6GHz band? Are they known to the developers? Have they been able to identify the source of the problem? Does it only happen with Asus routers? Are they working on a fix? Can they suggest a workaround in the meantime?

 

It's frustrating to not have much guidance or even a roadmap on these issues.

0 Kudos
Spacefish
New Contributor I
17,092 Views

This is fully expected behaviour. You are enjoying a regulatory feature here called "no IR" or "no inititial radiation". It basically blocks the fimrware sending on a band / channel which it never received a frame on before in the current session.


This is intended, such that your station (Client) does not accidently transmit on a band which it is not supposed to in the current regulary domain.. If your APs SSID is "hidden", it will not send beacon frames, so your AP (client) will not receive anything on the 6 GHz band / Channel.. So it would have to actively send out a frame to associate with the AP, this is blocked by the "no IR" feature..

So hidden SSIDs won´t work on channels with "no IR" enabled.. Intel enabled that feature for all channnels in the 6 GHz band.

 

"The NO-IR flag then means you cannot use modes of operation that require you to initiate radiation first"

0 Kudos
intc28665972
Beginner
17,073 Views

Thanks for the info on this. It makes sense.


So this is a feature and not a bug?


It seems to me that the user should be able to override this behavior so long as hidden SSIDs don't break the spec.


There doesn't seem to be a configurable option for this in the Advanced Properties for the Intel Windows driver. If there isn't an option to override it, there should be one.

 

Do you know of any workarounds?

0 Kudos
Spacefish
New Contributor I
17,057 Views

No workarrounds, it´s locked in firmware which you can´t patch as the image is signed. You can´t "override" it.

 

I guess they did it because of regulatory requirements in some regions.

 

You can´t even run the AX2** / AX4** card´s in 5 GHz AP mode, only 2.4GHz, let alone 6GHz.

They are really good client cards, but they are locked down heavily in firmware, if you want to do anything special with them / tinker with them, you are out of luck.

0 Kudos
alperg
Beginner
17,312 Views

I'm in the same situation where I can connect both 2.4 and 5GHz with out any issue BUT 6GHz is not visible. 

I'm using  Intel AX211 6E card with Windows10(64bit)  driver 22.150.0.3.

My router is ZenWifi ET8 with latest Firmware. 

0 Kudos
intc28665972
Beginner
17,248 Views

If you have a Dell XPS 9520, there's a thread about Dell intentionally disabling 6GHz capabilities for the AX211 adapter.

 

https://community.intel.com/t5/Wireless/AX210-AX211-not-showing-6GHz-networks-with-latest-drivers/m-p/1396105

0 Kudos
William104
Beginner
17,304 Views

I have the same issue when 22.150.03 update my driver my copy of 22.60.03 disappeared and now I cannot get the driver to install 22.60.03 which allows the 6 ghz band to work.

0 Kudos
intc28665972
Beginner
17,246 Views

You might have to first remove other versions of the driver already installed on your computer.

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax

 

Use the command:

 

pnputil.exe -e

 

to get a list of all of the drivers on your computer and make note of all of respective Intel "Network adapters" oem#.inf files.

 

Then for each oem#.inf file, run the command (replacing each "#" with the appropriate number):

 

pnputil.exe /delete-driver oem#.inf /force

 

You should reboot, and then try reinstalling the drivers.

0 Kudos
alperg
Beginner
17,196 Views

Unfortunately deleting driver via pnputil and the re-installing after reboot didn't work for me. 

0 Kudos
patwood
Beginner
15,537 Views

I am using MS window version 10 with Intel(R) Wi-Fi 6E AX210 160MHz .driver ver. 22.180.0.4I tried to connect to my wifi 6E nighthawk RAXE500) router with no success. Windows 10 64 is  unable to see my 6E SSID I can connect  2.4 GHz and 5 GHz channels with no problem. My Samsung Galaxy S23 connects just fine to my 6E SSID My lenovo laptop cor i7 just doesn't see it the AX210 is not the original card  I Have a desktop with windows 10 64 with a fenvi AX210 card with the same issue 

0 Kudos
Xardas
Beginner
5,810 Views

I've just installed the latest version of the driver, 23.80.1 after manually searching for it online.
https://www.intel.com/content/www/us/en/download/19351/intel-wireless-wi-fi-drivers-for-windows-10-and-windows-11.html
Now it does see and connects to the 6ghz wifi network.
Why isn't it appearing under the regular windows updates to make life easier?

0 Kudos
Dumitru
Beginner
5,168 Views

I have the same frustrating issue, cannot connect to my Wi-Fi 6e with ax210 160mhz. I've tried the solution from another post using the 22.45.1.1 driver version, also with the latest drivers is not working. Is there any way to check if the 6e is disabled at ax210 firmware level? Or maybe there is another solution for this issue?
I'm using Windows 11 with an Asus GT-AXE16000 router.

0 Kudos
Reply