No trace of Wifi6 networks on Nighthawk RAXE500

Until Win10 21H1 is available (which is any moment now) you also have to make a Registry change for the AX210 to work.  Now, 21H1 is supposed to have this change already built in but I haven't seen anyone confirm it for the release version.

So if you have a late enough version of the AX210 driver (22.40.0) I'd wait for 21H1 and see what happens.  If it doesn't work then I can post the registry hack (or Google is your friend).

Amen....at the price class (and for that matter all routers should allow this), there should be a way to verify function on the router itself, see internal service logs, etc. 

I have similar issues. I upgraded a desktop with a pcie intel ax210. At the moment I do not know how to get it to connect to the 6g band. I'm confused on what to do

Here's a link that spans the earliest attempts to get 6E to work and follows it through to the current situation where Microsoft is adding support in the latest Windows Insiders builds.

https://www.snbforums.com/threads/installing-a-ax210-windows-10-driver-that-works.70226/ 

The thing you're probably missing (guessing, since you didn't mention what you've tried) is the Registry edit.

All that being said, at this point I think the best move for most people is to wait for the new Win10 21H1 update to get pushed to your machine.  Some are already getting it, in fact, I just built a new machine last night that got it.

It should have the necessary drivers (the one that is linked to near the end of that forum thread) to handle 6E without any Registry hacks.  I'm not clear if this will also provide WPA3 support, so if it doesn't, you'll need to use Enhanced Open.

I will close the loop on my original questions with a personal conclusion. Your milage may vary. Based on all the insight given by Tonydi (Thanks), I did testing to address the questions from my original post.

After doing the registry edit I was able to detect the 6g broadcasting SSID but still had issues connecting. I then read where someone had extracted the wifi driver from a pre-release of the next windows 10 patch. It seems the regedit with the pre-release driver is working for people. Keep in mind the "hack" is just adding a DWORD to the right spot in the registry. I op'd to undo the regedt and ultimately follow Tonydi's advice. I will wait for the patch. I'll check but I imagine it will simply add the same DWORD and apply an updated driver.

However, from my testing I was able to answer my original questions. 1. My RAXE500 is working fine. 2. My install of the Intel 6E laptop wifi card is working fine. 3. It is my OS that needs to catch up for me to experience true 6E.

If any of you choose not to wait and do both the regedit and find the pre-released driver, please confirm that it worked. 

Thanks all.

I can confirm that the Win10 update does not use the Is6GhzBandSupported DWORD.  Once I got the update I went back and removed that entry from the Registry and I can still connect to the 6G band. 

Yeah, as a test I took off the Win10 Insider build and reverted back to my backup image containing 20H1. That one had the really old Intel driver.

Then I ran the update to get 21H1 but it didn't change the driver.  I also told it to load the optional 21H1 update update, still no new driver.

So I went into Device Manager, opened the AX210 entry and told it to go to Windows Update to look for a new driver.  That finally loaded the 22.50 driver and I could connect to the 6GHz band.

Sadly, once I changed the 6GHz band to WPA3 the network disappeared.  So it still requires Enhanced Open for the security setting and the expected change to 21H1 that we thought would include the necessary pieces to support WPA3 must not have made the public build.

Curiouser and couriouser......I went back and looked at your earlier posts and noted the talk about the registry hack.  With the Insider build I was able to remove those keys and I could still connect.  Realizing that the old backup image that I restored probably had the hack I went and looked.  Sure enough it was there in both keys with a value of 1.  I changed them to 0 and rebooted.

The 6GHz band disappeared.

So clearly the Windows Insider builds have the support built in and the public 21H1+ does not.  It looks like Microsoft bailed out and removed it from the public release.

Put the key back in and see what happens. 

If that still doesn't work then I'd suspect that your AX210 card has an issue.  Because you can't buy these cards directly from known Intel wholesalers there are some sketchy things going on with them.  I've seen a number of people with certain "brands" say they could never get them to work on the 6GHz band.  This was a few months ago so I'd hoped this had all been worked out, but maybe not.