A6200 Windows 8 support

I have both the WNDA4100 and the A6200 and they are both worthless on Windows 8.

Mark

I just purchased the A6200 and am having the same issues described here in Windows 8.1 Build 9431.

Anyone else seeing these errors in their event logs?
Source: System | Event ID: 7000
"The BCM42RLY service failed to start due to the following error:
The system cannot find the file specified." (Go to Start > eventvwr.exe > System > Filter > and filter by event ID 7000)

It appears that the device is using a Broadcom chipset and the service is crashing out in my situation.

I don't know if I'm going to stick with the A6200 though, I'm not a fan of Broadcom. I'll try support though.

Wow. This is enlightening. I've been facing the same issues as many posters with A6200 - needing to reinstall drivers. I don't haven't I'll have to try the pulling and reinserting the adapter but the couple of times I tried that earlier I had no success. My initial problems stemmed from trying to set it up with a Linksys EA6500. I won't bore you with details but suffice to say that after 3 days of losing internet connectivity along with frequently losing just wireless connection caused me to replace the EA6500 with an ASUS RT-AC66U which solved the loss of internet drops. While waiting for the replacement, I had the A6200 linked with a Linksys WRT54G router and had no wireless/internet losses for 4-days. Now that I'm back to ~250-300 Mbps speeds the wireless losses reappear.

I suspect drivers and think perhaps the stand-alone 1.0.0.26 is a tad more stable than the version with Genie nut still I have wireless drops. I may give the 1.0.0.23 a try next time it drops. In the long haul, I may just search for a good "n" adapter and wait for the "ac" adapters to get a life.

In summary, if anything is encouraging with this adapter/firmware/support issue, it is the voices being raised about the sad state of it. That may prompt a quicker solution. However, as in the case of my router return/replacement one can take just so much frustration before jumping ship for another product.

posting on this forum alone will not help in getting any issues fixed.
You must register your issues at NetGear support site.

fghamilton wrote:

Wow. This is enlightening. I've been facing the same issues as many posters with A6200 - needing to reinstall drivers. I don't haven't I'll have to try the pulling and reinserting the adapter but the couple of times I tried that earlier I had no success. My initial problems stemmed from trying to set it up with a Linksys EA6500. I won't bore you with details but suffice to say that after 3 days of losing internet connectivity along with frequently losing just wireless connection caused me to replace the EA6500 with an ASUS RT-AC66U which solved the loss of internet drops. While waiting for the replacement, I had the A6200 linked with a Linksys WRT54G router and had no wireless/internet losses for 4-days. Now that I'm back to ~250-300 Mbps speeds the wireless losses reappear. I suspect drivers and think perhaps the stand-alone 1.0.0.26 is a tad more stable than the version with Genie nut still I have wireless drops. I may give the 1.0.0.23 a try next time it drops. In the long haul, I may just search for a good "n" adapter and wait for the "ac" adapters to get a life. In summary, if anything is encouraging with this adapter/firmware/support issue, it is the voices being raised about the sad state of it. That may prompt a quicker solution. However, as in the case of my router return/replacement one can take just so much frustration before jumping ship for another product.

An update ~8 hours later:

Just as I was preparing for finally hitting the pillow my 'puter beeped and I noticed I'd lost wireless again. In no mind to try to sleep, I deleted the 1.0.0.26 driver and installed the 1.0.0.23 (with Genie). It looked OK for the time it took to try out the WEB and scan a stream or 2 on line at somewhere after midnight so I wrapped it up.

Today 5:30 AM EST: First thing I did was check the desktop icon and sure enough wless was disconnected. When I had installed the 1.0.0.23 drivers I had plugged the adapter in a usb port on the front of the PC thinking the clutter on my desk (wless printer, smart phone, PC monitor) in close proximity might have some bearing on the problem. Since it dropped even in the PC port I grabbed a USB extender cord and placed the A6200 in the provided dock, running the longer cord up to an uncluttered position on my bookshelf. I only had to plug the adapter in the port and wireless came back at 300 Mbps and is still there at 7:40 AM after a few WEB excursions, searches, downloads ,email, etc which is encouraging.

I'm going to let it stew for a (hopefully) few days and if I still have not dropped I will attempt 1.0.0.26 again with the adapter now located on the bookshelf and update here.

Mark_K wrote:
posting on this forum alone will not help in getting any issues fixed. You must register your issues at NetGear support site.

By what means? Is there a specific forum for that or by direct email?

My.netgear.com and contact support

fghamilton wrote:

An update ~8 hours later: .....Edit out part..... I only had to plug the adapter in the port and wireless came back at 300 Mbps and is still there at 7:40 AM after a few WEB excursions, searches, downloads ,email, etc which is encouraging. I'm going to let it stew for a (hopefully) few days and if I still have not dropped I will attempt 1.0.0.26 again with the adapter now located on the bookshelf and update here.

Still at 300 Mbps as of now ~5 hours later.....

jmizoguchi wrote:
My.netgear.com and contact support

For some reason, even though my card is registered, I have a username and provided a password, I can not login when requested, when attempting to contact support through email. Even after resetting password 3 times. I get a "Your password was invalid, please re-enter your details or click 'Forgot your password" error each time.

Anyway, I sent to chat for support, which I avoid if possible since I have 10 thumbs when it comes to typing. I was able to get a rep quickly explained the dropping issue I was having. BTW, since my last post, I had 2 drops one after 1lmost 12 hours of continuous service and a second after about 1n hour.

During chat, the tech had me install 1.0.0.26 drivers, go into >device manager >system >Network adapters >double click on a6200 >select Advanced >scroll down and select Maximum Power consumption and change it from the (default) Enabled to Disabled >click OK and close. Once back on line I was asked to monitor it for 12/24 hours. It has now been 2.5 and I'm still connected.

Hopefully, all my issues were configuration related and that simple toggle takes care of things. Will update progress in coming days.

Thank you, jmizoguchi, for pointer and thanks to "Cathy Lyn" at chat support for quick response and hopefully a solution......

fghamilton wrote:

......portion edited out...... During chat, the tech had me install 1.0.0.26 drivers, go into >device manager >system >Network adapters >double click on a6200 >select Advanced >scroll down and select Maximum Power consumption and change it from the (default) Enabled to Disabled >click OK and close. Once back on line I was asked to monitor it for 12/24 hours. It has now been 2.5 and I'm still connected. Hopefully, all my issues were configuration related and that simple toggle takes care of things. Will update progress in coming days. Thank you, jmizoguchi, for pointer and thanks to "Cathy Lyn" at chat support for quick response and hopefully a solution......

I connected to the 5 GHz band 24 hours ago and have not had a drop. (It had been 12 hours prior to that on 2.4 Ghz without a drop.) The frequent resets and drops have been absent.

I had been on and off the system for those 36 hours and expect to be randomly using as such until about 36 Hrs from now (now being 8/30 Friday at 8:10 PM EST)

Sunday (9/1 and over the Labor day holiday til Tuesday morning it will get significant use - web searching, streaming, etc. - so if I can make through that without a glitch I'l consider it "burned in"....
I hope.....