- HP Support Forum Home
- >
- Laptop & Notebook
- >
- Network/Wireless
- >
- Re: HP Pavilion dv6812nr- Wireless Driver Issue
HP Support Forums
Join in the conversation.
Search the Community
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
This HP Community is for Customer to Customer Product Support. First Time Here? Check Out Videos on How to Search, Register, Post and More.
Re: HP Pavilion dv6812nr- Wireless Driver Issue
(2485 Views)
Reply
Topic Options
- Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Message 1 of 2
(2,537 Views)
HP Pavilion dv6812nr- Wireless Driver Issue
[ Edited ]Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
11-18-2009 11:28 AM - edited 11-18-2009 11:44 AM
I had reinstalled my Windows Vista Home Premium 32-bit Operating System and I updated all my drivers and everything but the Wireless Card seems to work perfectly fine. I have talked to HP Chat technicians numerous times and they have each said/told me to do the same thing each time. I reset my BIOS, and reinstalled the Broadcom driver and it is still not working. When I opened up HP Wireless Assistant it said that "this device has been disabled by Windows Device Manager, but when I go into Device Manager it does not show my drivers still. It is only showing my ethernet port drivers. If anyone who has had this same issue before, please contact me and explain a way inwhich I can fix this minor annoyance. Thank you.
Message Edited by fcpeditor113 on 11-18-2009 11:44 AM
Message 2 of 2
(2,485 Views)
Re: HP Pavilion dv6812nr- Wireless Driver Issue
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
11-19-2009 02:27 PM
I had a similar problems on my dv6810us and went through actions similar to yours. Then I installed and older driver for my wireless card and everything worked. I a separate instance, I restored my system to a date earlier than the day the problem started and solved another similar problem.
