Speakers were working fine, until I updated drivers a few weeks ago.

I can get internal sounds to work, but no external (through desktop speakers).

Everything is connected properly, and the Troubleshooter says everything is OK, working.

I just installed another new Realtek driver, from Intel (my Mfr), ran diagnostics, everything is still "OK", working; still no external sounds.

I have XP-Pro, 2002, SP-3, Intel Pent-4.

Anyone have experience with this problem?

Do I need to go into the BIOS?

EWW!

I know this might sound real stupid but I have had that kind of problem and go check and make sure your PC sound is on.

Go to Control Panel

then Sound and Audio Devices,

When you make a change to the system it will turn off this setting.

River

Wouldn't think a foray into the BIOS is necessary.

I'm no expert, but imo most problems like this are down to [a] connections, or settings.

You've said that your connections check out OK. But test them again.

If you're using a laptop, and connecting your speakers with a mini-jack-plug in the headphones socket, check that you haven't got your volume setting at 'minimum' or on 'mute'.

Elementary stuff, I know, but it's all I can think of ...

The last time I had a similar problem it turned out to be a burned out board in my speaker. --FLO--

Thanks for the replies so far.

The only changes to my system recently are from Microsoft's updates.

Speakers are turned on (Control Panel, Sounds, Audios devices), nothing is unplugged. Everything worked fine until I updated drivers 3 weeks ago.

It started the internal speakers after the download of a new driver, through Driver Detective.

It plays internal sounds inside the tower . . . music, pings, etc.

I think I need to turn on 'line devices', and saw that 'External' was disabled in one of the troubleshooter panes, but for the life of me, I can't think of how to find a way to get there. (This is where I was thinking BIOS) [ick!].

When I right clicked on one of the External 'No' in one of the 3 lines for Sound Devices (I'm assuming Unabled, Not Enabled, or Off), it just says a standard Windows "What's This", instead of showing "Properties".

I went back into Hardware in Sounds and Audio Devices, and made sure the correct Driver was being used (from Intel/Realtek, downloaded today). So I don't know where or what to do now.

I also have been cruising through the million (feels like) tech blogs that are over 2 years old at Microsoft's Tech site. So far, nothing of help. Thankfully, at least for now, Microsoft still supports my OS. Maybe I'll read more tomorrow.

My head hurts.

Thanks guys.

Those Windows Updates can wreck havoc. I got sick of them and turned them off.

If all else fails, you might try re-setting your computer to a previous time when the sound worked properly. It would eliminate any programs you have recently installed, though, and I'm not sure how you reach it with Windows XP Pro.

And hey, by the way... neat story you posted recently! Thanks!

StefanIsMe (imported) wrote: Tue Apr 20, 2010 10:47 am Those Windows Updates can wreck havoc. I got sick of them and turned them off.

If all else fails, you might try re-setting your computer to a previous time when the sound worked properly. It would eliminate any programs you have recently installed, though, and I'm not sure how you reach it with Windows XP Pro.

And hey, by the way... neat story you posted recently! Thanks!

Those updates are a necessary evil to owning a Microsoft product. Typically when they cause problems, you have a bug or embedded scripts. Windows Defender (http://www.microsoft.com/windows/produc ... fault.mspx) is a free product from Microsoft that really works to keep the system free of junk. I also use MalwareBytes (http://www.malwarebytes.org/) for maintenance (not free, but very reasonable). A perfect tool for those who hate to do the tedious PC things.

Back to the speakers . . . of course I tried a reset. Ended up going back to Intel and acquiring a chip-set driver ($). Speakers work fine now.

Serves me right for not paying attention to the Driver Detective pick. The driver they picked was for a Vista Machine.

This PC stuff changes on a daily basis. I think I have forgotten more than I have learned some days.

A really quick check to see if it's a software or hardware issue can be to burn a Linux Live CD of one type or another and see if sound works through that. If it doesn't, changes are it's a hardware issue; if it does work, then it's an issue due to a Microsoft update.

And remember rule #1: always check your connections (and power buttons) (and i this case any software mute buttons) first.

Sorry that I can't be any more help. I haven't used a Microsoft-based (or Apple) PC since '99.

Best of luck...

Oops! Just actually read the third from last sentence on the wrong driver. Glad it worked out. But the advice works for anyone needing to check out other stuff anyway. (Who knew Microsoft & Co had so many tools to check on the health of a Win box...Not me. But then my systems never go to bye-bye land...

I've had your problem more than once before. The cause turned out to be driver updates sent by Microsoft. Microsoft is very good with its own software, but they'll also send updates from other companies. These updates might not be appropriate for your hardware configuration. Microsoft doesn't know enough to match other companies' drivers to the right hardware.

The solution is to do a System Restore, bringing your software back to what it was just before the driver update. (Be sure to re-install any Microsoft updates from that time.)

In future, go to the sites of your driver manufacturers to look for updates. They'll tell you exactly what's right for your hardware. Also, some computer manufacturers have their own programs to check for software updates, including drivers. HP does this, and several others.

Be very wary of any updates offered by Microsoft for any software other than their own. I routinely refuse such downloads until I've confirmed their applicability at the software maker's site.

bobover3 (imported) wrote: Mon Apr 26, 2010 8:43 pm I've had your problem more than once before. The cause turned out to be driver updates sent by Microsoft. Microsoft is very good with its own software, but they'll also send updates from other companies. These updates might not be appropriate for your hardware configuration. Microsoft doesn't know enough to match other companies' drivers to the right hardware.

The solution is to do a System Restore, bringing your software back to what it was just before the driver update. (Be sure to re-install any Microsoft updates from that time.)

In future, go to the sites of your driver manufacturers to look for updates. They'll tell you exactly what's right for your hardware. Also, some computer manufacturers have their own programs to check for software updates, including drivers. HP does this, and several others.

Be very wary of any updates offered by Microsoft for any software other than their own. I routinely refuse such downloads until I've confirmed their applicability at the software maker's site.

Agreed 100%.

For anything other than MS/Windows software, get your drivers from the source. While Windows Update is getting better in regards to these things, it's still much safer just to go to the company that made the hardware and get the drivers from them.

The big debate among techies (Well, that I'm aware of, anyways) is whether you should update your drivers if there's nothing wrong with your system. Personally, there has to be a damn good reason for me to upgrade working drivers before I'll do it.