NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Windows 10 (A6100 A6200 A6210) Installation Heads Up
As a heads up, DO NOT install Netgear's driver package for your A6xxx device on Windows 10. It permanently removes Windows 10’s ability to access the WiFi Connections list. Instead, use the defa...
For problems with the windows 10 included driver with the a6210 (e.g. no 5ghz networks visible) just use the latest driver from mediatek (5.1.21.0).
It is the newer version of the driver that came with windows 10 and with it i can join my 5ghz wlan, which wasnt able with the old one!
The chip in the A6210 is a Mediatek MT7612U.
I have not tested the driver they have for 10 as the generic solution works for me fine. The question still remains as there is a version for 10 put out by Netgear and it hasn't been picked up by the repository, why? Are we going to make excuses for the biggest conglomerate on not staying on top of their driver database? 10 has been out for close to 6 months now. The OS didn't even bother seeing it as new hardware until I went into device manager. I'm just saying that its not 100% Netgear and its justified in saying the communication was lacking in this release.
As far as their driver for W10 doesn't work one may imagine why it hasn't been picked for the repository!!
Wether it's a technical problem on Netgear's side or MS' is actually not my problem. I got (for free) W10 which never pretended to be compatible with previous devices unless manufacturers make the necessary changes for compatibility. I *paid* a WiFi key which was sold as W10 compatible when it is *not* and when less important competitors are. The point is it works neither as plug & play nor with a custom driver installation. And if you finally succeded in running it with generics that's certainly not with the help of Netgear!
Netgear owes me a fix and at least some explanation here for their customers. Have you read anything from them about where is the problem but to explain for months they gonna fix it?
May someone from Netgear dare to tell us here this is MS' fault too as an excuse?
I did try to uninstall the generic Realtek driver and use the one that Netgear posted but it goes back to the Realtek. Really don't care b/c it works like a champ. I did notice when it reinstalled the original driver... the Windows wifi systray is now seeing the N network on my router. Before I had to use the widget to admin that connection... so it's perfectly fine now with me. You can keep griping or fix the issue with what a contributor posted a few pages back.
zipdrive wrote:I did try to uninstall the generic Realtek driver and use the one that Netgear posted but it goes back to the Realtek. Really don't care b/c it works like a champ. I did notice when it reinstalled the original driver... the Windows wifi systray is now seeing the N network on my router. Before I had to use the widget to admin that connection... so it's perfectly fine now with me. You can keep griping or fix the issue with what a contributor posted a few pages back.
zipdrive, with respect, which you have none of, your issue with your device may be for a different model than what others have. You see, I tried the Realtek solution out of desperation and ended up bluescreening upon driver install. I have searched out Broadcom drivers for the chipset that is involved with my adapter and used them to no avail. In conclusion, if your device is working, don't be a yutz and brag about how well your device is doing and not even provide a reference to the post which solved YOUR problem. We're not all blessed to be as special as you.