11-27-2012 11:56 AM
After installing Windows 8 my wireless network adapter no longer works. It is a driver issue. Here are my system details.:
HP Pavilion Model MS225 running Windows 8 Pro. Yes I ran the support assistant before upgrading and no it did not list my wireless network adapter as a problem. The installation did damage my restore partition and the Recovery disks I made are worthless due to a defective original factory installation.
Misrosoft tells me to contact HP and Qualcomm Atheros. HP refuses to support the upgrade even though their original factory installation of Windows 7 Factory Restore Partition was defective making it impossible to go back without purchasing System Restore disks. I refuse to pay for them as I made disks before I started the process, unfortunately they are worthless due to HPs original defective software installation.
Qualcomm Atheros simply refuses to respond in any way.
For the record ACER uses the same adapter in many of its machines and has posted Windows 8 drivers on it's website. Why can't HP?
11-27-2012 12:04 PM - edited 11-27-2012 12:29 PM
If you are certain the ACER wirless card is the same as yours and has W8 drivers, I would suggest you use the Acer driver then and see if it works.
Hardware is hardware.
I have used Dell drivers on HP equipment and HP drivers on Dell PC's.
HP isn't going to do anything to help you, as you already indicated.
Did you try the windows 7 driver from your PC's support and driver page?
If it didn't install, did you try to manually install the driver?
11-27-2012 01:09 PM
Yes I have tried everything you suggested except the manual install. I could use pointers on how best to do that. Failing all else, does anyone know if I can remove the device from the system? Or is it built into the motherboard?
11-27-2012 01:46 PM
A manual install is not difficult and oftentimes works.
Basically you are going in the back door to install the driver when going in the front door as you have tried, doesn't work.
So, this is what you do...
Run the driver file again. Close out of any error windows you get.
Now, go to the device manager and click on the network controller with the little yellow ! mark (that is the wireless adapter).
Click on the driver tab. Click on Update Driver. Select the Browse my computer for software" method of installation and browse to the driver installation folder that was created when you ran the file.
That file will be located in C:\SWSetup\sp44585.
Make sure the Include Subfolders box is checked and hopefully, the driver will install that way.
If it doesn't then that card may not be compatible with W8.
You can also try this newer atheros driver if you want.
You can remove the card but you may not be able to replace it with a different internal card. In the event the drivers don't work, I would remove the card and purchase an external USB wireless adapter which should suit your needs.
The upgrading and servicing guide is at the link below. It isn't of much help, unfortunately. It looks very difficult go go beyond replacing the memory or hard drive.
If you can get to the motherboard, you will probably find a card that looks like this...that would be what you want to yank.
11-27-2012 02:38 PM
Thanks so much for your time and effort! I have performed the additional suggestions and have decided to just remove the thing. Dont worry about my skills. I have done more intricate tasks at my job and on many notebook computers many times. At this time I will consider the issue closed.
11-27-2012 06:57 PM
Thanks for the suggestion but it did not work. When you said it worked for you, did you have the same adapter in your computer because if you do and it worked I wll keep looking for a solution because that indicates to me that the adapter is Windows 8 compatible. I think I will wait another couple of days before yanking it from my system. Who knows? Maybe the Windows 8 experts will have a solutiion or suggestion tomorrow.
11-28-2012 09:09 AM
The Atheros AR5007EG is listed as compatible. So I will not be removing it any time soon. I am starting to think this is a windows problem! Several of the above steps should have worked and did for other users.