Quantcast
Channel: Notebook Audio topics
Viewing all articles
Browse latest Browse all 25412

HP ENVY dv6-7229wm Mute Button

$
0
0

Why oh why does Micro$oft (and Crapple) have to jack with everything - then the computer manufacturer has to try and fix it, then "they" break it again.  Why the vicious cycle?  And the consumer is the one that suffers...

 

So, I just installed the latest updates from Micro$oft, then the fixes from HP, and then spent hours trying to get everything working again; except for the LED on the mute button.

 

I have searched and searched.  I found all kinds of discussion, but everyone seemed to have a "stuck on" condition.  I still tried some of the  appropriate solutions, disabling the drivers, reinstalling the drivers, installing old drivers.  I did not do a restore because I would lose some of the application updates I had to install because of the M$ and HP updates.  Nothing has worked.

 

Call me an old fuddy duddy, but I firmly believe that when Micro$oft steered away from XP, and tried to make everything tablet oriented and graphically flat (because they weigh down the system with their inefficient coding) with  Windose 8 (I won't mention VISTA, though Windows 7 wasn't too bad), they clearly signaled that they no longer cared about  us consumers, that they are arogant that they cannot be unseated, and ruined any chance of being a trusted member of the computing community.

 

But for the fact that we have Windows and Apple based systems at work, I would be wholly Linux and Android... but, enough venting.

 

The problem I have is that the mute button works, but the LED does not toggle on and off, it stays dark!  It was broken by a Microsoft update, and overlooked by HP?

 

I rely fairly heavily on that indicator!  Has anyone seen this problem?  Does anyone know what the fix is?

 

Thanks,

James

 

 


Viewing all articles
Browse latest Browse all 25412

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>