New
#1
Sound - speakers/headphones - stopped working on ASUS laptop
With no intervening "event" - no new hardware or software or drivers installedFollowing the installation of a Cisco VPN client, the sound stopped working on my ASUS laptop.
There is a red X over the speaker icon at the bottom right of the computer. Mousing over the icon, one sees "no speakers or headphones are plugged in."
The computer had Conexant audio, plus AMD hi-def audio (I don't have the computer with me now, so this could be an inexact listing).
First thing I tried was to update the drivers, but both were up to date. I then uninstalled the Conexant via the device manager and restarted. Upon restart, the red X was gone, but I was still not getting sound. I could adjust the sound properties by clicking on the speaker icon in the system tray, but there was still no sound.
I believe I tried this again, and upon restart, the Conexant was gone from Device Manager, leaving just the AMD hi-def. I tried changing the driver for this to the generic Windows hi-def audio driver, but that didn't work.
I tried just about every trick I could google up:
- Download next drivers from AMD/ASUS/Conexant's sites
- Run sfc /scannow from an admin command prompt (everything was intact)
- Restart the sound services, and make sure they were on automatic start
- Seemingly a billion computer restarts
- Many I can't remember now
None have worked. And again, Conexant had been the default audio, then disappeared (why?). Now when I go to my "Sound" from the control property, AMD hi-def is the only thing showing in the playback tab, and it says "not plugged in" with a red down arrow next to it. The system tray speaker icon has a red X over it and left-clicking on it launches troubleshooting, which (un)helpfully tells me the sound isn't plugged in, after "churning and churning" for minutes.
The optical drive is the only thing I'm comfortable "opening up" on a laptop! Is there a chance that MAYBE something somehow DID become unplugged internally?
The only "bag of tricks" angle I've not tried is a system restore to four days ago, before this condition started.
Ideas?
Last edited by asus2016; 09 Mar 2018 at 08:06.