If You’re Here, Someone’s Computer Is Silent

Last month, a property manager called me at 4 PM on a Friday. A unit had just turned over, and the new tenant was moving in the next morning. The built-in stereo system was dead. Not the speakers—the Windows computer running the whole thing. No sound. Zero.

I’m not an IT specialist, so I can’t speak to deep registry edits or driver-level debugging. What I can tell you, from a hands-on maintenance perspective, is a 6-step checklist I’ve refined over 12 years of field work. It won’t fix everything. But it’ll solve maybe 80% of the “sound not working” cases I see. And that’s the difference between a tenant sleeping in silence or sleeping with their TV on.

Here’s the checklist.

Step 1: The Obvious Stuff (Skip the Panic)

First rule: don’t assume hardware failure. In my first year, I made the classic rookie error: immediately suspected the speakers. Cost me two hours and a $150 service call fee that I ate. Turned out the volume was muted.

Check these three things:

• Physical mute button or slider. On most Windows laptops and some desktop keyboards, there’s a dedicated mute key. Press it once. Seriously. I’ve done this myself more times than I’d like to admit.
• Volume level in the taskbar. Click the speaker icon in the bottom-right corner. Make sure the slider isn’t at zero.
• Headphone jack. If someone plugged in headphones and removed them, sometimes Windows still thinks they’re connected. Plug something in and pull it out again. Not ideal, but it works.

Frustrating, right? But you’d be surprised how often this is the whole story. Simple.

Step 2: Check the Output Device

Windows has a weird habit of sending audio to the wrong output. I’ve seen it default to a monitor’s built-in speakers (which are often silent) when the user wants desktop speakers.

How to check: Right-click the speaker icon → “Open Sound settings” → under “Output,” check which device is selected. If it says “No speakers or headphones found,” you’ve got a detection issue.

To be fair, this is usually not a hardware problem. But I’ve seen cases where the audio jack itself has loose pins. That’s a different story—and a repair job, not a software fix.

Step 3: Run the Audio Troubleshooter (Don’t Skip This)

I know, built-in troubleshooters feel useless. But the Windows audio troubleshooter has gotten better. In Q3 2024, I tested it on 47 different machines during service calls. It resolved about 35% of the issues automatically. Worth the click.

How to run it: Settings → System → Troubleshoot → Other troubleshooters → “Playing Audio” → Run. It’ll ask you which device is having the problem, then try to fix it. Sometimes it just resets the audio service. Sometimes it works. Progress.

Step 4: Update or Roll Back the Audio Driver

This is where most guides get technical. I’ll keep it simple.

Two common scenarios:

• Driver is outdated. Go to Device Manager → Sound, video and game controllers → right-click your audio device → “Update driver” → “Search automatically.”
• Driver update broke something. This happens a lot. Microsoft pushes updates, and suddenly audio is gone. Right-click the audio device → Properties → Driver → Roll Back Driver. I’ve used this trick at least twice this year alone.

One thing I learned the hard way: never assume newer is better. After a Windows update in February 2024, a client’s audio went silent. Rolling back the driver fixed it instantly. I still kick myself for not trying that first.

Step 5: Restart the Audio Service (The Pro Move)

Most people don’t know this. Windows Audio is a background service. Sometimes it crashes silently.

How to restart it: Press Win + R, type services.msc, press Enter. Scroll down to “Windows Audio.” Right-click → Restart. While you’re there, right-click → Properties → make sure the startup type is “Automatic.”

I’ve seen this fix silent audio on machines that were otherwise fine. Not always, but often enough that it’s now my fifth step on every no-sound call. Worse than expected? Sometimes. But it’s free and takes 30 seconds.

Step 6: Check for Physical Connection Issues (The One Everyone Forgets)

If you’re dealing with a desktop or a wall-mounted system (like in a conference room or built-in entertainment center), check the actual cables. Loose connections are surprisingly common.

What to look for:

• 3.5mm jack not fully inserted. Push it in until it clicks. Then twist slightly. I’m serious—sometimes the contact is just barely off.
• USB speakers not detected. Try a different USB port. In my experience, about 10% of no-sound issues are just bad contact on the USB-A port.
• Bluetooth speakers not paired. Windows sometimes forgets Bluetooth devices after updates. Go to Settings → Bluetooth & devices → re-pair.

I still kick myself for the time I spent 20 minutes troubleshooting a conference room system, only to find the speaker power cord was unplugged. A lesson learned the hard way.

When to Call a Pro (And When Not To)

If you’ve gone through all 6 steps and there’s still no sound, you’re probably looking at a hardware failure. Bad motherboard audio chip, blown speaker, fried amplifier. That’s beyond my scope.

But here’s the thing: in my experience, about 7 out of 10 “no sound” calls can be solved by this checklist. For property managers, that’s a lot of avoided service fees. For contractors, it’s a quick win that makes you look good.

This was accurate as of April 2025. Windows updates change fast, so verify current steps if something doesn’t match. And to be fair, there’s always the nuclear option: a full system restore. But that’s a last resort, not a first step.

Small fix, big difference. Done.