So I bought the Nighthawk AX8 yesterday, and when I go to set it up, the WiFi networks are now showing up in any of my decives so that I can set the router up through the Nighthawk app.
I have tried rebooting the router, power cycling the router, turning wifi off and on, resetting the router and nothing seems to work.
A number is more useful than "the latest". (It may not be by the time people read this.) There can also be newer versions, or "hot fixes", that do not show up if you check for new firmware in the browser interface.
Page 21 of user manual tells how to access using a browser on PC rather then the app. Then you can configure that way. Probably a more reliable way to access the router as folks seem to have issues when they use the app.
I had a similar issue but got it resolved. Android, Apple, and most W10 devices connected fine when the new AX8 (RAX80) was installed earlier this week. I started getting calls that people with Windows 10 laptops that couldn't connect to the network and the network didn't show in the list of 'available networks'. I spoke with Netgear support and the problem is fixed.
The issue was caused by older network device drivers, primarily Intel, on the W10 pcs. The new router runs at a high speed the old drivers cannot handle.
One option is to update the old drivers which is fine but will take time to identify and fix all affected pcs. The second option is to 'turn the speed down' on the router so the old drivers will work. It's a simple fix. Here are the steps:
Login to the AX8
Go to Wireless
Look for Enable AX - This wifi mode will enable AX features ....
Uncheck Enable AX
Apply
After unchecking this box the router immediately showed in 'available networks' and the pcs connected to the network. We didn't notice any difference in the speed of the network but we only had ten devices connected.
We found three W10 pcs with older Intel AC 7260 network drivers. We tested the fix before and after installing the latest driver and the issue/fix performed as expected.
This was my first experience with the support team at Netgear. It took over an hour to find the person that understood the issue because the router is so new. I think Netgear did an excellent job handling my issue.
Perhaps @StoneCold_X could check that this answer fixes things for them. If so, marking the response as "Solved" might help anyone who turns up later with the same issue.
