NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
paradeigmas
Jul 30, 2015Tutor
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...
- Aug 01, 2015
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.
smintz
Jan 11, 2016Aspirant
now you tell me! :) I have been having nothing but problems since my ISP installed the drivers. What as a novice can I do to reverse it and re-install?
Cdr_Perkins
Jan 11, 2016Guide
In my case the problem was the forced and automatic device driver installation by Win 10.
Regardles of wether Mediatek was installing his driver, Win 10 installs his own driver over the Mediatek installation - a Netgear driver.
And when i uninstalled the forced Netgear driver, Win 10 installed an old Mediatek driver and so on. It looks like after uninstall a driver Win10 rolls out all of the other USB drivers they were installed in Win7.
This was the reason for my problems and why it didn't shows up my 5GHz connection - because of old driver installation by Win 10 (or Win 7, who knows).
I think this is caused by installed USB drivers under Win7 (upgrade to Win10, no clean install), meantime i'm pretty sure.
I had similar problems with a Kensington trackball and his driver, but now this works too.
Solution was to install the newest Mediatek driver, wating until Win 10 has installed his own driver and after that installing the Mediatek driver manually from its installation folder via device manager.
Because of this i have switched off the automatic device driver installation in Win 10 via gpedit to have no further problems - fingers crossed.
Now everything works.
Marcus