NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Model A6210 (AC1200 USB Adapter) Install causes HP printer to fail
8/22/21 - I just recently tried to install the A6210 USB adapter on my HP 2000 Lap Top runnning Window 8.1. The PC has 8GB of RAM and it is 64 bit. All the USB ports are 2.0. The A6210 is supposed to...
So you don't think its the using a windows vista driver on a windows 8.1 machine that could be causing it?
Seems like using a driver that isn't compatible would be whats causing issues.
I say no, and I base that upon the fact that I've been using this HP1012 printer for years without issue in this manner. I've used other USB gear on this computer as well and they never interferred with the printer so the only change has been trying to install the A6210. By the way, using the VISTA driver is the recommended solution from HP and other end users. ...and really the only purpose of a driver would be to translate instructions from the OS to the hardware. I would think each driver is set up for a specific device and the driver for the AC6210 is specific to that hardware and it should not conflict with the printer.
so try it without the printer installed. Or try it on a different computer.
Does it work fine? if so, the common thread would be the sketchy driver. And its a sketchy company who recommends using a vista driver on a windows 8.1 device. If they were that great at support, they'd simply update it.
Yes, the AC6210 works on the HP2000 after installed (that is not the issue) but, the install causes the printer to fail. As I said previously, the purpose of a device driver is to act as an interpreter between the app/OS and the hardware. The install of a new device should not corrupt the install of another working device. The device driver is not common between the two devices. The OS would only interoperate with the WIFI adapter and call the specific WIFI driver when it needs it and the same with the printer. So, since the drivers are both unique and used for different operations, it does not make sense that the printer device driver itself, is the issue.