Windows 7: Mute stopped working in Windows 7!

Hello all,

First time posting here as I have scoured the Internet and have not found a solution to my problem. I am hoping someone on here can help me out.

Just recently, when I go to mute the sound in Windows, it does nothing and sounds continues to still be played. The icon in my taskbar displays the red circle with the slash through it indicating that it has been "muted" when in fact it has not.

I am still able to adjust the volume with the slider and that works fine, just not mute.

Anybody have a clue as to what is going on here?

Thanks in advance for you help! This is driving my crazy!

First suggestion, reinstall the sound drivers. Use the drivers from your PC vendor or motherboard vendor (You didn't fill out the My System Specs so we can only guess).

Thank you for your reply.

I have tried uninstalling the Realtek audio drivers and reinstalling the latest version from HP's website to no avail. I recently installed a GTX 680 graphics card and I run an HDMI cable from it to my 7.2 receiver, so even when uninstalled, the Realtek audio drivers do not seem to affect anything, as I can still get sound coming out of my speakers from all sources.

I then thought it may be an issue with the first WHQL drivers from nVidia (as it seems to be what is now controlling my sound), so I did a complete removal of the current GPU drivers and did a clean install of the latest beta drivers. Still no luck

I've run the gamut of full scans on my system including Windows Malicious Removal Tool, Spybot Search and Destroy and McAfee Security Center - all of which have turned up nothing.

Anyone else experiencing this or could anyone please help me out? I'm literally wanting to tear my hair out.

Hello, if I Understand correctly, you are running the audio from your PC through the HDMI port of your 680, into a surround sound receiver?

If that's the case, then you might want to contact your GPU manufacturer. I'm sure this is a Driver related problem. It is a very new card, be patient.

And BTW, what's wrong with just hitting the mute button on the receiver?


James

Yes, you are correct in how I have my audio setup.

I have contacted nVidia and so far the only reply I have gotten is that if they can replicate the issue, they will address it in an upcoming patch. I was also kind of curious if anyone on these forums or elsewhere has experienced this particular issue with the GTX680 as numerous searches have not returned anything related to this issue. I would think if there were other users with this problem I would have been able to find something considering it is a new flagship card.

I am able to mute directly with my receiver remote, but it is just much more convenient to be able to hit the mute key on my Logitech K800 keyboard when I am gaming or typing.

I have tried everything I know to try, including, enabling/disabling devices in the sound properties, configuring the sound within, uninstalling/reinstalling and upgrading the 680 drivers, and swtiching the onboard audio in the BIOS from on to off to auto, all to no avail.

The only other suggestion I can give you is to use the S/PDIF out from your board. You can disable the audio via HDMI and set the S/PDIF as the primary for audio on your system and you should be able to mute then.

I HAVE HAD THE EXACT SAME PROBLEM!! I also have a Logitech K800 with setpoint, and my mute button wont work either. Even if its just the mute control at the bottom right hand corner of the screen in windows, without the keyboard it won't mute.

Interestingly enough, I have also installed one of Nvidia's latest Graphic Cards, the gtx 670 Superclocked and I'm willing to BET this has something to do with that... :/ I've pretty much done everything else I can think of from re-installing audio drivers from Asus, even the newest intel chipset. I've disabled, enabled, uninstalled and reinstalled sound drivers in the device manager, uninstalled setpoint, it goes on and on... Sorry to get your hopes up if this post got you excited for a responce. I say we contact nvidia about it. Maybe do some forum thumping there?

Well, I've got some good news for you! You are correct in believing it has something to do with the video cards - this is what I suspected as well. I contacted nVidia about two weeks ago and their hardware testing lab was able to replicate and confirm this bug in their current WHQL and beta driver for the 6xx series cards. The rep that I spoke with said that this should be implemented into the next beta driver that is released. Keep your fingers crossed!