Audio Service Is Not Running | Quick Fixes That Work

On Windows, “Audio Service Is Not Running” means the Windows Audio services stopped; restart them, set to Automatic, and update drivers to restore sound.

Your PC shows sound devices, but silence. The taskbar speaker has a red X, and the tooltip says the audio service isn’t running. This error points to one thing: Windows Audio and its helpers aren’t active or can’t start.

Fix Audio Service Is Not Running: Fast First Checks

Quick check: Before touching services or drivers, rule out easy blockers.

  1. Restart The Pc — A fresh boot resets stuck sessions and frees locks.
  2. Switch Outputs — Click the speaker icon, pick the right device (headphones, speakers, HDMI, or USB).
  3. Set Default Device — Open Sound settings > Choose where to play sound, select your device, press Set default.
  4. Check Volume Mixers — Right-click the speaker icon > Open volume mixer; make sure device and app sliders aren’t muted.
  5. Unplug And Replug — Reseat the 3.5 mm jack or USB plug; try a new port. For HDMI, power-cycle the display.
  6. Disable Exclusive Mode — In device Properties > Advanced, clear the Exclusive Mode boxes, then test.
  7. Run The Troubleshooter — Settings > System > Troubleshoot > Other troubleshooters > Playing Audio > Run.

Audio Service Is Not Running — Reset Windows Audio Services

Deeper fix: The core service names are Windows Audio (Audiosrv) and Windows Audio Endpoint Builder (AudioEndpointBuilder). Both must run, and both should start Automatic. Remote Procedure Call (RPC) is a dependency and should run.

Start Services From The Console

  1. Open Services — Press Windows+R, type services.msc, press Enter.
  2. Set Startup Type — Double-click Windows Audio > Startup type: Automatic > Apply. Do the same for Windows Audio Endpoint Builder.
  3. Start Or Restart — Click Start or Restart for each service. If either fails, note the error code.
  4. Confirm Dependencies — In the Dependencies tab, RPC should be listed and running.

Start Services With Commands

Fast path: Use an elevated terminal.

net stop audiosrv
net stop audioendpointbuilder
net start audioendpointbuilder
net start audiosrv

Or with PowerShell:

Stop-Service -Name audiosrv -Force; Stop-Service -Name audioendpointbuilder -Force
Set-Service -Name audiosrv -StartupType Automatic
Set-Service -Name audioendpointbuilder -StartupType Automatic
Start-Service -Name audioendpointbuilder; Start-Service -Name audiosrv

If you now hear the chime, the stack is back. If not, move on.

Driver And Device Fixes That Clear No-Sound States

Why this matters: The audio service can start yet stay mute when the device driver is missing, generic, or corrupt. HDMI and USB paths can also change the default target.

  1. Identify The Chip — In Device Manager > Sound, video and game controllers, note names like Realtek, Conexant, Intel, NVIDIA, or AMD.
  2. Reinstall The Driver — Right-click the device > Uninstall device > check Attempt to remove the driver > Uninstall. Reboot to reload a clean driver.
  3. Install Vendor Drivers — Download the model-specific package from your PC maker. Many laptops need the OEM set.
  4. Roll Back If Needed — If sound broke after an update, open device Properties > Driver > Roll Back Driver.
  5. Update Hdmi Audio — For GPUs, install the latest Intel/NVIDIA/AMD audio component. Pick the HDMI device as default only when the TV or monitor is on.
  6. Test A Usb Headset — A known-good USB headset bypasses the onboard codec. If it works, focus on the internal device and jack sense.

Fix Audio Service Is Not Running On Windows 10 And Windows 11

Fresh start steps: These actions repair broken registrations, bad profiles, and missing files that cause the prompt “Audio Service Is Not Running.” Pick the path that matches your symptoms.

Repair System Files

  1. Run Sfc — Open an elevated Command Prompt and run:
    sfc /scannow
  2. Restore With Dism — If SFC can’t finish, run:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Reboot And Test — Try playback again; if the error returns, continue below.

Reset The Sound Stack

  1. Stop Audio Tasks — In Task Manager > Details, end stray audiodg.exe sessions.
  2. Clear Enhancements — In device Properties > Enhancements or Audio Effects, disable sound effects, then test.
  3. Switch Formats — In Advanced, set 16-bit, 44.1 kHz; test, then 48 kHz.
  4. Rebuild The Profile — Create a new Windows user, sign in, and test sound. If it works, the old profile has cache issues.

Fix Service Start Errors

  • Access Denied — In Services > the service’s Log On tab, the account should be Local Service or Local System.
  • Error 1068 — A dependency didn’t start. Set Endpoint Builder and RPC to Automatic, start them, then start Windows Audio.
  • Error 1079 — Use the service’s default account in Log On; pick Local Service from Browse and confirm.

Clean Boot And App Conflicts

Why this helps: Some OEM suites, virtual audio cables, voice changers, and capture tools hook into the stack. When they misbehave, the system thinks Audio Service Is Not Running even though services are alive.

  1. Run A Clean Boot — Press Windows+R > type msconfig > Services tab > check Hide all Microsoft services > click Disable all. In Startup > open Task Manager, disable third-party items. Reboot and test.
  2. Remove Extra Audio Paths — Uninstall virtual audio devices you don’t need. Reboot and check the default device again.
  3. Check Security Suites — Some “device control” features block drivers. Disable that module and retest.
  4. Recreate Apps’ Output — In each media app, pick the correct device. Set them back to Default once the system path works.

When The Message Keeps Coming Back

Stubborn cases: If the prompt “Audio Service Is Not Running” returns after each boot, lock in the service state and update core parts.

  1. Force Automatic Start — In an elevated terminal:
    sc config audiosrv start= auto
    sc config audioendpointbuilder start= auto
  2. Reinstall Uaa Class Driver — In Device Manager > System devices, right-click Microsoft UAA Bus Driver for High Definition Audio (if present) > Uninstall, then Scan for hardware changes.
  3. Turn Off Fast Startup — Control Panel > Power Options > Choose what the power buttons do > clear Turn on fast startup.
  4. Run Windows Update — Apply pending quality updates.
  5. Firmware And Bios — Install the latest BIOS and chipset packages from the maker’s page.
  6. System Restore — Pick a restore point from before the error, confirm, and let Windows roll back drivers and services.

Keep Windows Audio Stable

Simple habits: Few simple choices prevent repeats of the “Audio Service Is Not Running” prompt.

  • Use Oem Drivers — For laptops, stick to the maker’s audio pack unless a later pack is listed for your model.
  • Update In Order — Apply BIOS and chipset updates first, then the audio driver, then GPU audio if you use HDMI.
  • Limit Virtual Devices — Install only the tools you need. Extra paths add risk.
  • Shut Down Before Cable Swaps — Power off the PC and the display before moving HDMI or USB audio, then boot and select the target device.
  • Back Up A Working State — Create a restore point after you reach a stable setup.

Causes Of The Error And Fast Remedies

Reference: Match your symptom to a quick action. Then follow the linked section above for the full steps.

Symptom Likely Cause Quick Remedy
Speaker icon shows a red X Audio services stopped Start audiosrv and endpoint builder
Sound works on HDMI only Wrong default device Pick the playback path you use
Apps play, system sounds mute Per-app mixer or effect Open volume mixer, disable effects
Starts after boot, then dies Third-party hook or driver Clean boot; remove virtual devices
Service start error 1068 Dependency not running Start RPC and endpoint builder
Works on new profile only Corrupt user profile Create a new profile or repair
USB headset works, speakers don’t Onboard codec or jack sense Reinstall OEM audio package

With the steps above, most systems go from no sound to clear output in minutes. If nothing brings audio back, check for hardware faults: a damaged front panel cable, a bent jack, or a failing codec on the board. In those cases, a USB DAC or a small PCIe card is an easy workaround while the machine is serviced.