Windows Audio
Also called audiosrv, windows audio service
The Windows service that keeps the audio engine running. The isolated graph process is audiodg.exe.
What you need to know
This service is the audio contract. audiodg.exe is the isolated mixer.
Audiosrv starts the Windows audio engine. Ending audiodg.exe drops the graph until the service starts it again. Disabling Audiosrv silences the PC.
- Important?
- Yes, if you want speakers or a headset
- Same as audiodg?
- No. That is the graph host
- Safe to disable?
- No, unless you want silence
What does this service do?
Display name: Windows Audio. Service name: Audiosrv.
Windows Audio loads the audio engine, talks to drivers, and starts audiodg.exe for processing objects. Windows Audio Endpoint Builder is a related service that enumerates devices.
History on Windows
Still present
User-mode Windows audio as a service pair (Windows Audio and Endpoint Builder) arrived with Windows Vista when Microsoft replaced the older kernel mixer path. The Audiosrv service name has stayed on Windows 7, 8, 10, and 11. Windows XP and earlier used a different audio architecture without this service name.
| First shipped as Audiosrv | Windows Vista (2007) |
|---|---|
| Earlier form | Kernel mixer on Windows XP and earlier, different architecture |
| Still present | Yes, including Windows 10 and Windows 11 |
| Discontinued | No |
Why does Windows need it?
Every app that plays sound through WASAPI or the older APIs needs the engine. Without Audiosrv there is no shared device graph.
When does it run?
It should be running whenever you expect sound. The graph process can start and stop with streams.
Should it always be running?
Automatic is the default on client Windows. Manual only makes sense on a headless SKU that will never play audio.
Can I disable it?
No if you want sound
Disabling Audiosrv turns off the Windows audio engine. Meetings, browsers, and system sounds fail together. Restart the service instead of leaving it off.
What happens if I disable it?
No shared Windows audio. Some exclusive apps still fail because the device list is empty.
Process host
Audiosrv often lives in svchost.exe. The mix and enhancements run in audiodg.exe. See audiodg.exe / svchost.exe.
Dependencies
| Depends on | RPC and Windows Audio Endpoint Builder for devices |
|---|---|
| Used by | Any app that plays through Windows |
Resource behavior
- CPU
- Low in the service. Enhancements show on audiodg
- Memory
- Small
- Network
- None
- Disk
- Low
Common problems
No audio after a driver install
Restart Audiosrv and Endpoint Builder, then the graph. Disabling the service is not a driver rollback.
People end audiodg and think the service died
The service can restart the graph. Check services.msc if sound never returns.
Troubleshooting
Safe steps first.
Run the Windows sound troubleshooter first
It restarts these services. Then inspect the playback device enhancements.
Do not set Audiosrv to Disabled as a "privacy" tip
That tip is silence, not privacy.
Technical details
Technical details
| Display name | Windows Audio |
|---|---|
| Service name | Audiosrv |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: audio services · Audio stack
- Microsoft Support: fix sound · Audiosrv and devices
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.