Daily Tech Dispatch

Windows Troubleshooting

Fix 'Windows Could Not Start Audio Service' Errors 2026

Struggling with 'Windows could not start the audio service'? Follow this 2026 guide to fix Error 1068 & permissions in minutes. Restore sound now.

You’re trying to listen to your favorite music or join a crucial meeting, and instead of sound, you get a cryptic error: "Windows could not start the audio service on local computer." This is a common post-update or dependency glitch, and it’s fixable in minutes. While the error message looks intimidating, it rarely signifies broken hardware. In most cases, you are dealing with a service dependency failure (Error 1068) or a permission blockage (Error 0x80070005).

I’ve spent the last fifteen years troubleshooting system-level issues, and I can tell you that diving headfirst into driver re-installs is usually the wrong first step. Before you touch your sound card drivers, you need to verify the status of the Windows Audio service using services.msc. This guide provides a structured troubleshooting path, moving from quick service restarts to specific registry fixes, designed to save you the time spent bouncing between ineffective solutions.

Close-up of an illuminated RGB keyboard displaying a cyberpunk interface with neon text options.

Quick Diagnostic: Is the Service Actually Stopped?

Checking Status via Services Console

Before attempting any complex repairs, we need to know exactly what state the service is in. Open the Run dialog (Win + R), type services.msc, and hit Enter. In the resulting window, scroll down to locate two specific entries: Windows Audio and Windows Audio Endpoint Builder.

Look at the "Status" column. If you see "Stopped" or "Disabled," you’ve found your culprit. A frequent mistake I see users make is assuming the service is broken when it has simply been set to "Disabled" by a previous software install or a misconfiguration. To check this, right-click Windows Audio, select Properties, and look at the Startup type. If it is set to "Disabled," change it to "Automatic (Delayed Start)." This is often the services.msc audio service disabled scenario that trips people up, as manual startup settings can be overwritten by group policies or security software.

Manual Start and Immediate Restart

Once you have verified the startup type is correct, attempt to start the service manually. Right-click Windows Audio and select Start.

If the service starts and stays running, test your audio immediately. Play a video or check a system sound. If it starts but stops again a few seconds later, or if you get an error immediately, note that specific error code. This distinction is vital: a service that refuses to start due to a permission issue is different from one that crashes due to a dependency failure.

Warning: Do not attempt to permanently disable this service. The Windows Audio service is critical for system functionality. Disabling it will silence not just your media player, but also system notifications, accessibility features, and potentially components of Windows Update that rely on media processing libraries.

Black and white abstract blocks on a white background, conceptual design.

Fixing Error 1068: Resolving Dependency Service Failures

Identifying Critical Dependency Chains

If your error message explicitly cites Error 1068, you are looking at a classic dependency failure. Windows services are like a chain of dominoes; if one falls, the others topple. Windows Audio is not standalone. It relies on Remote Procedure Call (RPC), Multimedia Class Scheduler Service, and Windows Audio Endpoint Builder.

If any of these underlying services are stopped or unresponsive, the audio service audio service depends on other service that is currently offline, and the system will throw Error 1068. This is why restarting just the audio service often fails. You need to ensure the entire dependency chain is active.

Restarting Dependent Services in Order

To fix this, we need to start the dependencies in a specific logical order. You can do this via the services.msc interface or the command line. I prefer the command line for precision, as it forces a strict execution order. Open an elevated Command Prompt (run as Administrator) and use the following checklist:

  1. Start RPC: This usually auto-starts, but verify it. Type net start RpcSs and press Enter.
  2. Start Multimedia Class Scheduler: Type net start MMCSS and press Enter.
  3. Start Windows Audio Endpoint Builder: Type net start AudioEndpointBuilder and press Enter.
  4. Start Windows Audio: Finally, type net start AudioSrv and press Enter.

If the AudioEndpointBuilder service hangs at "Starting," do not force it with taskkill as some forums suggest; this can corrupt the audio stack. Instead, reboot the machine and let Windows initialize the stack fresh.

Using Command Line to Force Service Registration

Sometimes the service configuration itself gets corrupted. We can verify this by checking the registration data. In your elevated Command Prompt, run:

sc qc AudioSrv

This command queries the service configuration. If the output looks standard (showing the service type, start type, and binary path), the registration is likely fine. If you suspect a glitch, you can force a restart sequence:

net stop AudioSrv
net start AudioSrv

If this fails with an access denied error, skip to the next section on permissions. If it fails with a "service not started" error, the dependency chain above was likely the issue, and the manual start sequence should have resolved it.

Resolving Error 0x80070005: Access Denied & Permissions

Why You Might See 'Access Denied'

Error 0x80070005 translates to "Access is denied." This is not a broken file; it is a locked door. In my experience, this usually happens in two scenarios. First, you are running the Services console without sufficient administrative privileges. Second, and this is rarer but more persistent, the registry permissions for the service executable have been stripped away by a virus, a failed software uninstall, or a misguided "cleaning" tool.

Understand that Windows uses User Account Control (UAC) and Local Security Policy to gatekeep service management. If your user account is a Standard User, you cannot start services. Even if you are an Administrator, if the specific ACLs (Access Control Lists) on the service binary have been corrupted, Windows will block the start command regardless of your login status.

Running Services as Administrator

The first step is ensuring you have the right to the gate. Open Command Prompt as Administrator. If you previously tried to start the service from a standard prompt, that is why you failed.

Next, check the Local Security Policy. Press Win + R, type secpol.msc, and hit Enter. Navigate to Security Settings > Local Policies > User Rights Assignment. Look for the policy Service or Log on as a service. Ensure that SYSTEM, Local Service, and Network Service are all present in the user groups list. If they are missing, adding them back can resolve the permission block.

Advanced: Registry Key Fixes (For Experienced Users)

If the above steps didn't work, and you are comfortable with the registry, we can look at the file permissions directly.

Warning: Always back up your registry before making changes. A wrong key deletion can render your OS unbootable.

  1. Open Registry Editor (regedit).
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AudioSrv.
  3. Right-click the AudioSrv key and select Permissions.
  4. Ensure that SYSTEM and Administrators have Full Control.

If these entries are missing or set to "Read" only, that is the root cause. You need to take ownership of the key and grant full control to the Administrators group. This allows the enable windows audio service in registry context to function properly, restoring the service's ability to launch its executable.

Driver & System File Repair: Permanent Solutions

Updating and Reinstalling Audio Drivers

If your service status looks fine but audio is still dead, the issue is likely at the driver layer. Go to Device Manager and expand Sound, video and game controllers.

You have two paths. Option A is to right-click your audio device and select Update driver. Let Windows search automatically. Option B, which I recommend for stuck drivers, is to right-click and select Uninstall device. Check the box that says "Attempt to remove the driver software" if it appears. Reboot your PC. Windows will reinstall a generic driver upon startup.

Pro Tip: Generic Microsoft drivers are fine for baseline functionality, but for best performance, check your motherboard or laptop manufacturer's website for specific OEM drivers. They often include enhancements that the generic Microsoft package lacks.

Running SFC and DISM

Corrupted system files are a silent killer of service stability. If SFC /scannow gets stuck at 85%—a very common issue noted by many users—it means the system file cache is corrupted. You need to repair the image before scanning.

Open an elevated Command Prompt and run this DISM command first:

DISM /Online /Cleanup-Image /RestoreHealth

This downloads and repairs corrupted component files from Windows Update. Once it completes (it may look stuck at 60-70% but is working), run the System File Checker:

SFC /scannow

Reboot your computer after the scan completes. This sequence addresses the "stuck at 85%" problem by fixing the underlying component store first, a step many quick-fix guides miss.

System Restore & Clean Boot

If this issue started after a recent Windows Update or the installation of new audio software, consider rolling back.

  1. System Restore: If you have restore points, revert to a date before the issue started.
  2. Clean Boot: Press Win + R, type msconfig, and go to the Services tab. Check "Hide all Microsoft services" and click Disable all. This isolates third-party conflicts, such as aggressive antivirus software or audio enhancers that might be killing the service.
  3. Uninstall Updates: If you know a specific KB update broke it, go to Settings > Windows Update > Update History > Uninstall updates and remove the culprit.

Special Cases: Windows 10/11 Specific Behaviors

Differences in Service Management

Windows 10 and 11 have tighter service protection mechanisms than their predecessors. Some services are marked as "Critical System Service," meaning Windows prevents you from disabling them even as Admin. If you find Windows Audio is protected, check Group Policy Editor (gpedit.msc). Ensure that no policy is explicitly blocking the service from starting.

Additionally, check Event Viewer. Navigate to Windows Logs > System. Look for errors with the source Service Control Manager or Audio. The specific error ID here can tell you if a driver failed to load or if a policy blocked the start. Filter by "Error" level to find the relevant entries quickly.

Post-Update Glitches

I frequently see this issue after major feature updates. Windows sometimes temporarily disables audio services during the update process to allow file modifications. If you just installed a big update, wait 24 hours. The background processes may be re-enabling the services.

If it persists, run the built-in troubleshooter:

  1. Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. Run Audio.
  3. Run Windows Update.

This can reset the update agent and audio stack in one go. For users dealing with the specific windows 11 audio service error fix, this combination of patience and the built-in troubleshooter resolves the issue more often than not, without needing to touch the registry.

FAQ

Why does Windows audio service fail to start after a restart? This typically happens because the startup type has been changed to "Disabled" or "Manual" by third-party optimization software or a recent update. When you reboot, Windows doesn't start the service automatically. The fix is to open services.msc, locate Windows Audio, and set the Startup type back to "Automatic" or "Automatic (Delayed Start)."

Is it safe to disable the Windows Audio Service? No. It is critical for the operating system's media playback. Disabling it causes no sound in apps and can break Windows Update components that rely on media processing. It also disables accessibility features and system notifications. You should only "Stop" it temporarily for troubleshooting, not "Disable" it permanently.

What are the dependent services for Windows Audio? The three key dependencies are Remote Procedure Call (RPC), Multimedia Class Scheduler Service, and Windows Audio Endpoint Builder. If any of these are stopped, Windows Audio will fail to start with Error 1068. You must ensure these dependencies are running before the main audio service can initialize.

Conclusion

Getting past the "Windows could not start the audio service" error is rarely about complex hardware swaps. It is almost always a service management issue. The most effective solution is checking dependencies for Error 1068 and verifying permissions for Error 0x80070005. If those check out, move to driver updates and the DISM/SFC repair sequence.

If you have tried all the steps above—from the Clean Boot to the registry permission checks—and the service still refuses to start, a Clean Install of Windows is the "gold standard" resolution. It wipes the slate clean. But keep that as your last resort.

If your issue is resolved, please share which specific step worked in the comments to help others. Still stuck? Download our free Audio Troubleshooting Checklist PDF [Link] for a quick-reference guide to keep on your desktop.

Back to Home