"No Audio Device Detected"

jimrev

Junior Member
Feb 28, 2007
14
0
0
I just finished my first build a few weeks ago. Everything worked just like it was supposed to the very first time I flipped the switch. A few days later, though, I noticed I was getting no sound. Thus began two grueling, confusing weeks of trying to figure out why the machine had lost track of the installed device, then couldn't find it again. I went back and forth between the on-board Realtek ALC888 and my trusty SB Audigy card I've had for a good number of years. I installed, uninstalled, swapped, rolled-back, downloaded, booted, and rebooted and rebooted and rebooted...and even tried some sweet talk. Still nothing but the message "No Audio Device Detected."

Then just this weekend I found a thread on Creative Labs' forum that cleared up all the problems in about...oh...a minute. In case anyone is experiencing a similar problem, here's the simple solution Microsoft apparently doesn't want you to know about, since I couldn't find anything remotely helpful on their site(s).

1. Start > Run > services.msc
2. Locate the "Windows Audio" service
3. If it's set to "Manual" or "Disabled", there's your problem. Right click on it to pull up the Properties and reset it to "Automatic."
4. Start the service and hopefully you'll get sound. I certainly did.

That's it.. done...and not a word on Microsoft's knowledge base, at least that I could find in relation to the problem I was having, about this little utility.

So, hope I can pass on this help to someone else in need. OH, BTW, in case anyone's wondering. I kept the four-year-old SB Audigy card installed and bagged the brand new on board Realtek thing. And it sounds WONDERFUL..:D
 

Jiggz

Diamond Member
Mar 10, 2001
4,329
0
76
Nice info. But this service is turned on or Enabled by default. I'm wondering why yours is not!
 

jimrev

Junior Member
Feb 28, 2007
14
0
0
It's been a mystery to me. I pretty much knew it was a software/driver problem because the sound worked for the first few days. I'm thinking somewhere in the process of installing software, updating drivers, etc., it somehow turned itself off.

JimRev