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 default driver that comes with Windows 10, of which will freeze when you try to connect to networks until you complete the installation of Intel’s new Chipset Drivers here:
https://downloadcenter.intel.com/download/20775/Intel-Chipset-Device-Software-INF-Update-Utility-
If that still doesn’t work for you, try the following:
Go to Network List, select the network you are trying to connect to, hit “Connect”, you should see “enter password” box and also a message about using WPS to connect, then instead of entering the password go hit the WPS button on your router.
Your adapter should connect and function completely now.
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.
277 Replies
- Download the driver now, don't install it. Save it to your desktop or elsewhere you well know where it's at. Then do all the steps.
Update us whether it works for you or not.Thank you for your response. Unfortunately, my daughter already uninstalled the drivers per the instructions from a previous post. Do we have any options for downloading the needed drivers other than moving and connecting her computer to an Internet connection using an Ethernet cable? Thank you for your help.
Download using another computer to a USB memory stick.
Months. Take that word in. It has been MONTHS, since Netgear has had any tangible information or updates for this particular problem. It has been MONTHS, since I have seen any viable solution or suggestion to fix this problem. In case you don't know what I'm talking about, I would suggest looking here and here. You have taken my information, Netgear, and done what with it? Nothing, absolutely nothing. No word, no PMs, no credibility. I'll grant the guise of effort, but that is about all I will grant. I have been compliant with all requests for information and patience. I have been completely understanding that things like this take time, but MONTHS? There are issues with your hardware that have been around since Windows 8, and now with the release of Windows 10 the problem has resurfaced. Living proof that the problems you DON'T SOLVE will come around to bite you. Are you going to learn this time? Probably not, but as long as you got my money, and that of others, at one point or another you probably couldn't care less.
This is a total stuff up by NETGEAR for firmware update/upgrade to Windows 10
I have no faith in this brand any more,
They have had made no attempt to resolve this and platitiudes only go so far.
I cannot believe an organistation release so call ed updates when it causes so much grief.
I wil be getting rid of NETGEAR all of it, it all seems to fail from router to extender to adapter.
So bad
"To assist in the most rapid and complete solutions Netgear engineers would be most grateful if people could provide some specific information. This thread is now somewhat confused as it deals with three different adaptors, and each has its own driver.
Please answer as much of the following as possible in a reply to this thread;
- What model of adaptor are you having issues with?
- Is the Win10 install a fresh install or an upgrade?
- If an upgrade, from what version of Windows?
- What is the H/W model of the PC/tablet/netbook?
- What driver version are you attempting to install?
- Did you try installing with AV / Firewall disabled?
- What error messages do you see?
- If no error messages what failure of functionality do you see?"
1. Two A6210 adapters
2. Windows 10 clean install
3. N/A
4. MSI Z97 Gaming 5 Motherboard
5. The driver i have installed for the a6210 1.0.0.32 and my r8000 router has the latest firmware 1.0.3.4
6. Installation of Driver is not an issue.
7 & 8 please refer to Link
Same questions here...Even I install the latest firmware of A6210, it crashes with windows 10 and always showing blue screen with kernal sercuity failure ...
When I remove the a6210 adapter and everything work fine ....When will netgear fix it? I wait the solution starting from September....
without any suggestion or solution, Is it meaning that i need to give up A6210?"To assist in the most rapid and complete solutions Netgear engineers would be most grateful if people could provide some specific information. This thread is now somewhat confused as it deals with three different adaptors, and each has its own driver.
Please answer as much of the following as possible in a reply to this thread;
1. What model of adaptor are you having issues with? A6210 with R7000
2. Is the Win10 install a fresh install or an upgrade? Upgrade to windows 10, probelm occured, reinstall the windows completely, problem still remain until i remove A6210
3. If an upgrade, from what version of Windows? Windows 8
4. What is the H/W model of the PC/tablet/netbook? Intel Core i5-4440 16GB Ram Gefore GTX760 Asus motherboard
5. What driver version are you attempting to install? Both v1.0.0.28 in compatibility mode(Win 8) and v1.0.0.32, same problem occur (Kernel Sercuity Check Failure and restart)
6. Did you try installing with AV / Firewall disabled? yes
7. What error messages do you see? Blue screen - Kernel Sercuity Check Failure https://dl.dropboxusercontent.com/u/44736506/20151019_113859.jpgGiven the depth of this problem, and the information been given to NETGEAR, they appear to be non responsive.
They keep asking the same questions and enough information suppled to support without any doubt There is a real probelm here.
NO action has been taken and its been how long now??
Silence has been deafening...
Say something NETGEAR !!!!!
This and other hardware / firmware issues really make this a poor choice for networking solutions. Hello D Link..
I got the A6210 adapter to work the following way:
1) Uninstall Netgear Genie
2) Revert back to Windows 8.1
3) Upgrade to Windows 10
4) Plug in the A6210 adapter
5) Windows 10 automatically installs driver, I can finally see networks and connect
Has anyone tried using the A6210 since the new WindowsX update from today? I've been living in Win8.1 since stupid butthole Netgear never wanted to fix this issue in WinX. I would really like to be able to upgrade back, but I'd just bought this damn adapter a month before WinX was released.
I havent seen any updates ????, 1.0.0.32 is the firm ware that stuffed eveything up, for A6210.ever other a62xx
- In some defense of Netgear, they do happen to have the 10 version on the downloads but I'm sticking with workaround until I have a problem. I think the big question here now is why isn't MS seeing the hardware on plug and play and the fact it's not searchable via "search online" option for new drivers?
I think there is a little blame to go around on both parties as Netgear should be a big enough name to be included in the list of latest releases.
zipdrive wrote:
In some defense of Netgear, they do happen to have the 10 version on the downloads but I'm sticking with workaround until I have a problem. I think the big question here now is why isn't MS seeing the hardware on plug and play and the fact it's not searchable via "search online" option for new drivers?
I think there is a little blame to go around on both parties as Netgear should be a big enough name to be included in the list of latest releases.There is no defense of Netgear in this case. For some this problem has been around since Windows 8 and is manifesting for more users. This is not a time to say, "Windows driver repository doesn't have everything for PnP, so it's partially their fault." Do you know how many devices that are PnP on the market both past and present? There are hundreds of thousands. Seeing as how this problem has been around for so long and Netgear doesn't have an answer for a driver related issue, (yes, it's driver related) you can't point the finger and play the blame game. Companies with integrity don't do that.
There is a w10 version of the drivers but it simply doesn't work.....so the job is not done.
W1O does recognise the key alone and install the necessary generic files. The device is in the "working status" but simply doesn't practically work like with the netgear drivers. So it's a product problem. Online search for new drivers works well for me, In both case I'm told I have the latest drivers. To be fully "plug and play" a device must be designed to be so and respect relevent protocols. Obviously this one doesn't.
I don't think any manufacturer or software developper is "included" in any MS release, no matter big they are. MS has its own code and protocol, they have to fix any bug from it but it's the job of those manufacturers to adapt their part to fit.
And if Netgear is big enough, I expect them to be able to get in contact with MS if needed to solve THEIR problem. As a modest individual I already had some support from MS when needed. I would if I had problem with *any* WiFi USB key which is not the case.
In the meantime I am waiting for a solution from Netgear for a rather expensive product in its category.
- 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.
