ThisCalculator

Everyday

Audio Service Not Running Solved: Fix Steps

Updated · Standard formula, shown below

Audio Service Not Running Solved: Fix Steps

If you see “One or more audio service isn’t running� in Windows, the fix is usually to restart the Windows Audio service and its dependencies, then re-enable the audio device. This error appears when the Windows Audio, Windows Audio Endpoint Builder, or Remote Procedure Call (RPC) services are stopped or disabled, and it blocks sound from playing on your PC. Below are the exact steps to resolve it, plus what to do if the service won’t start.

Why the Error Happens

The message comes from the Windows audio stack, which relies on three services working together:

  • Windows Audio (Audiosrv) – manages audio devices and mixes sound from apps.
  • Windows Audio Endpoint Builder (AudioEndpointBuilder) – configures audio endpoints (speakers, microphones).
  • Remote Procedure Call (RPC) – a core Windows service that the other two depend on.

If any of these are stopped, disabled, or set to manual when they should be automatic, Windows shows the “One or more audio service isn’t running� error in the Sound settings and the volume icon may have an X. Common triggers include a recent Windows update, a third-party “optimizer� that disabled services, or a driver conflict.

Quick Fix: Restart the Audio Services

This solves most cases. You’ll need administrator rights.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Windows Audio. Right-click it and select Restart.
  3. Do the same for Windows Audio Endpoint Builder.
  4. If the service is not running, right-click it, choose Start, then right-click again and select Properties.
  5. In the Startup type drop-down, set it to Automatic (not “Automatic (Delayed Start)� for the Endpoint Builder). Click Apply and OK.

After restarting, check the volume icon – the red X should be gone. If the service stops again immediately, go to the next section.

If the Service Won’t Start

Sometimes Windows Audio fails to start with an error like “Error 1068: The dependency service or group failed to start.� This usually means the RPC service is disabled. To fix it:

  1. In services.msc, find Remote Procedure Call (RPC). Its Startup type should be Automatic and it should be running. If not, start it and set to Automatic.
  2. Check DCOM Server Process Launcher – it should also be Automatic and running.
  3. If both are fine, open an elevated Command Prompt (Win + R, type cmd, press Ctrl+Shift+Enter) and run:
net localgroup Administrators /add networkservice
net localgroup Administrators /add localservice

Then restart your PC. This adds the built-in service accounts to the Administrators group, which fixes permission problems that can prevent the audio service from starting.

Check Your Audio Device in Device Manager

If the services are running but you still see the error, the audio driver may be disabled or corrupted.

  1. Right-click the Start button and select Device Manager.
  2. Expand Sound, video and game controllers.
  3. Find your audio device (e.g., Realtek High Definition Audio, Intel Display Audio). If it has a down arrow, right-click and select Enable device.
  4. If it’s already enabled, right-click and select Uninstall device (do not check “Delete the driver software� unless you have a backup). Then click Action > Scan for hardware changes to reinstall it.

After reinstalling, restart your PC. Windows will re-detect the device and reinstall the driver automatically.

Run the Built-in Audio Troubleshooter

Windows has a dedicated tool that can find and fix common audio issues.

  1. Go to Settings > System > Sound (Windows 11) or Settings > Update & Security > Troubleshoot (Windows 10).
  2. Click Troubleshoot or Additional troubleshooters.
  3. Select Playing Audio and run the troubleshooter.

It will check for disabled services, driver issues, and volume settings. It may ask you to restart the PC. This is safe and often fixes the problem without manual steps.

When the Error Persists After All Fixes

If you’ve tried everything above and the error remains, the problem may be deeper:

  • Corrupted system files – run sfc /scannow in an elevated Command Prompt, then DISM /Online /Cleanup-Image /RestoreHealth.
  • Third-party audio software – uninstall any “audio boosterâ€� or “sound enhancerâ€� apps that might conflict.
  • Windows update pending – check for updates and install them, then restart.
  • Hardware issue – if you’re using USB speakers or headphones, try a different port or test on another PC.

As a last resort, you can do a System Restore to a point before the error appeared, or reset Windows (keep files). Only do this after backing up your data.

Frequently Asked Questions

Why does the audio service keep stopping?

It usually stops because a dependency (like RPC) is disabled, or because a third-party service is conflicting. Check the service properties and set them to Automatic, then look for “optimizer� apps that disable services – uninstall them.

Can I fix this without admin rights?

No. Starting or changing services requires administrator privileges. If you’re on a work or school PC, contact your IT admin.

Will restarting the service delete my audio settings?

No. Restarting the service only stops and starts it. Your volume levels, default device, and enhancements remain unchanged.

What does “Error 1068� mean?

It means a dependency service failed to start. Usually the RPC service or DCOM Server Process Launcher is disabled. Enable them and set to Automatic.

Is it safe to run the command that adds services to Administrators?

Yes, that command adds the built-in NetworkService and LocalService accounts to the local Administrators group. It’s a known fix for audio service permission issues and is safe on most systems.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.