Audio services not responding

Windows Audio Service Not Running: Real Fix That Works

Windows Errors Intermediate 👁 8 views 📅 Jun 19, 2026

Your audio stopped working because the Windows Audio service got stuck. Here's the fix and the reason it works.

Nothing worse than clicking the volume icon and seeing that red X. Let's cut the frustration and get your audio back.

The Fix: Restart the Audio Service Properly

  1. Press Win + R, type services.msc, hit Enter.
  2. Scroll to Windows Audio. Right-click and select Restart. Wait 10 seconds.
  3. Also restart Windows Audio Endpoint Builder the same way.
  4. Close Services, test your sound.

That's it 90% of the time. But if the service won't start, or the restart button is greyed out, move to the next step.

When Restart Fails: Manual Start

If Windows Audio shows as Stopped and the start button is unclickable, your service is locked by a bad driver or a system file issue. Here's the workaround:

  1. Open an admin Command Prompt (cmd as Administrator).
  2. Type:
    net stop audiosrv && net stop AudioEndpointBuilder
  3. Then:
    net start audiosrv && net start AudioEndpointBuilder
  4. Check audio again.

Why this works: The services.msc GUI sometimes gets stuck waiting for the service control manager to respond. Using net start from the command line bypasses that GUI delay. It's a direct system call that often shakes the service loose.

Why the Audio Service Freezes

What's actually happening here is the Windows Audio service (audiosrv) depends on AudioEndpointBuilder and several RPC services. If any one of those dependencies hiccups — like after a driver update, a Windows update, or a bad sleep/wake cycle — the whole chain freezes. The service looks like it's running but isn't responding to audio requests. Restarting the chain resets the state.

The reason step 3 works is that AudioEndpointBuilder is the service that actually manages audio device connections. If it's stuck, Windows Audio can't see your speakers or headphones. Restarting it forces a fresh enumeration of audio devices.

Less Common Variations

Audio Service Starts Then Stops

If the service starts but immediately stops, the culprit is usually a corrupt audio driver. Open Device Manager (devmgmt.msc), expand Sound, video and game controllers, right-click your audio device, and choose Uninstall device. Check Delete the driver software for this device if you see it. Then restart Windows — it'll reinstall the generic driver. Then update to your manufacturer's latest driver.

Volume Icon Missing Entirely

When the speaker icon disappears from the taskbar, it's often a different service: Windows Audio Endpoint Builder is running, but Windows Audio itself is dead. Check both services as above. If both are running but the icon is still gone, open Settings → Personalization → Taskbar → Turn system icons on or off. Make sure Volume is On.

Audio Service Won't Start After Windows Update

A Windows update can break the audio service if it updates the audiosrv.dll or AudioEndpointBuilder.dll files. Run sfc /scannow in an admin command prompt. If it finds corruption, let it fix, then restart. If that doesn't work, run DISM /Online /Cleanup-Image /RestoreHealth — this repairs the component store that sfc relies on.

Permanent Fix: Prevent Future Freezes

The root cause is usually a driver conflict or power management. Do these two things:

  • Disable audio device power saving: Device Manager → right-click your audio device → Properties → Power Management → uncheck Allow the computer to turn off this device to save power. Windows loves to sleep audio devices during idle, and sometimes they don't wake up properly.
  • Keep audio drivers updated: Directly from your motherboard or laptop manufacturer's site, not Windows Update. Realtek, Nvidia HDMI audio, and Intel Display Audio are the usual suspects. Check for updates every few months.
  • If sleep/wake cycles cause the issue: Open Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup. Fast startup caches driver states, and audio drivers are notorious for not surviving that cache.

That's the complete picture. No registry hacks, no third-party tools, no reinstalling Windows. Just the service chain, the driver, and the power setting. Test after each step — odds are you'll be back to music or YouTube in under two minutes.

Was this solution helpful?