If your PC plays Windows system sounds but individual apps are silent, you’re not alone — this is a common, frustrating problem with a handful of consistent causes and straightforward fixes. Microsoft’s official troubleshooting checklist walks through per‑app volume, per‑app output selection, audio services, and drivers; this article expands those steps with practical detail, diagnostic flowcharts, real‑world examples from Windows community threads, and cautions about risky fixes. Read on for a clear, repeatable troubleshooting plan that gets apps talking again — and for the traps to avoid while you fix them.
Background / Overview
When system sounds (startup chimes, notification beeps) play but individual apps produce no audio, Windows is telling you something specific: the audio stack is working at a system level, but either the app is being routed to the wrong output, muted at the app level, blocked by audio service settings, or a driver/driver profile mismatch is interfering with playback. The most common culprits are:
- Per‑app volume or mute in the Volume Mixer.
- Per‑app output device (apps can be assigned to different outputs than the system default).
- Windows Audio service or Windows Audio Endpoint Builder being stopped, stuck, or misbehaving.
- Outdated, corrupt, or incompatible audio drivers, including third‑party audio managers (Realtek, NVIDIA, USB audio dongles).
- Exclusive mode or audio enhancements that give one app exclusive access to the device.
- App‑level problems (app set to the wrong device or muted inside its own UI).
Community reports show these causes repeat across Windows versions and hardware combinations, and the simplest fixes (Volume Mixer and per‑app output checks) often resolve the issue quickly. Forum threads from long‑time Windows users demonstrate the prevalence of per‑app muting and per‑app device selection as immediate causes.
What Microsoft recommends — short summary
Microsoft’s guidance centers on three primary checks:
- Use the Volume Mixer to confirm the affected app isn't muted and the slider is up.
- Confirm the app is using the correct output device (apps can target a different device than the system default).
- Restart Windows Audio services (Windows Audio and Windows Audio Endpoint Builder).
- Update audio drivers via Device Manager if drivers are old or incompatible.
These steps are the right first moves because they check configuration, per‑app routing, and the core Windows audio services that sit between apps and hardware.
Quick first‑aid checklist (run this in 5–10 minutes)
If you want to test the fastest possible path before doing deeper work:
- Right‑click the speaker icon on the taskbar → Open Volume Mixer. Make sure the affected app is not muted and its slider is up. This fixes many cases instantly.
- In the taskbar audio icon, open Sound settings (or Control Panel → Sound) → Playback tab. Ensure the expected device is set as Default and set the app to use that device in App volume and device preferences.
- If that fails, open services.msc, find Windows Audio and Windows Audio Endpoint Builder, and select Restart for both services. Test the app again.
- If still broken, open Device Manager → Sound, video and game controllers → right‑click your device → Update driver (or uninstall + reboot to force reinstall). Test again.
If the app audio returns at any of these stages, stop there — don’t apply further changes unnecessarily.
Deep dive: why per‑app settings break audio
Volume Mixer and per‑app mute
Windows exposes per‑application volume controls through the
Volume Mixer. Apps that were muted previously or that set their own internal volume to zero will be silent even while system sounds play, because system sounds use a separate mixer path. Many forum posts show users surprised to find their browser or media player muted in Volume Mixer while system sounds worked fine. Checking this is the single most common fix.
App‑specific output device selection
Windows allows apps to target specific playback devices through
App volume and device preferences (Settings → System → Sound → Advanced sound options). If an app is pointed at a device that’s unavailable (for example, a Bluetooth headset that is disconnected), it will produce no sound even though the default device works for system sounds. Users often overlook this because the global default audio device appears correct.
Windows Audio services
The Windows audio pipeline relies on two Services:
Windows Audio and
Windows Audio Endpoint Builder. If either is stopped or in a hung state, app sound can fail while very early/low‑level system sounds still play (they are often generated earlier in the boot pipeline). Restarting these services resets the pipeline and resolves transient failures for many users.
Drivers: the most important, and the most dangerous, area
Why drivers matter
Drivers translate Windows’ audio API calls to real hardware behavior. If drivers are outdated, mismatched to a major Windows update, or corrupted, apps may be unable to open the audio endpoint they expect. Community reports across many years show driver mismatches — especially after Windows feature updates — causing selective app audio failures.
Safe driver troubleshooting workflow
- Try Update driver from Device Manager first (right‑click audio device → Update driver). This is reversible and low risk.
- If Update doesn’t help, choose Roll back driver (if available) — this is often effective after a driver that came from Windows Update caused a problem.
- If roll back isn’t available, consider Uninstall device (in Device Manager) and reboot so Windows reinstalls its driver automatically. That often clears corrupted driver state.
- As a last resort, download the OEM or component vendor driver (Realtek, Intel, NVIDIA, or the USB audio vendor) and install it manually. Only use vendor drivers from the hardware manufacturer; avoid third‑party “driver updater” tools.
Risks and caveats
- Installing unsigned or unofficial drivers can break system stability or security.
- Uninstalling drivers may temporarily remove certain features (surround processing, control panel apps). Ensure you have driver installers or a restore point before making major changes. Forum threads show frustrated users who lost onboard mic or device entries after driver changes; proceed carefully.
App permissions, exclusive mode, and audio enhancements
Exclusive mode
Some apps request
exclusive access to an audio device so they can manage sample rate and buffering. If an app locks the device incorrectly or if another app holds exclusive access, other apps become silent even while system sounds continue. To check:
- Open Sound Control Panel → Playback → Device Properties → Advanced → uncheck Allow applications to take exclusive control of this device. Test again.
Audio enhancements and format mismatches
Audio enhancements implemented by vendor drivers (virtual surround, EQ, microphone processing) can interfere with some apps. Try disabling enhancements and, if necessary, change the default audio format (sample rate / bit depth) to a common value (for example, 24 bit, 48000 Hz or 16 bit, 44100 Hz). Community troubleshooting posts often highlight switching sample rate or disabling enhancements as successful fixes.
Bluetooth, USB audio, and external device oddities
If your system default is a headset, speaker bar, or USB audio adaptor, confirm the device is connected and not asleep. Apps can remain pointed at a device that was previously present (a disconnected headset), leading to silence. For Bluetooth, make sure the OS is using the correct Bluetooth audio profile (A2DP for media; HFP/HSP for calls often have lower quality or different routing). Several forum threads show users switching to built‑in speakers to verify whether the issue is device‑specific.
Practical diagnostics: step‑by‑step procedure
Follow this ordered list to find and fix the problem reliably. Move to the next step only if the previous one did not restore audio.
- Reproduce the symptom with a simple app (e.g., a browser playing a short video or a media player).
- Open Volume Mixer: right‑click speaker → Open Volume Mixer. Verify the app’s slider and mute state. Unmute or raise if needed.
- Open Settings → System → Sound → App volume and device preferences. Confirm the app’s Output device is set to the expected device. If not, set it to Default or the chosen device and retest.
- Restart Windows Audio services: Start → type services.msc → locate Windows Audio and Windows Audio Endpoint Builder → right‑click → Restart. Retest.
- Check Device Manager: Start → Device Manager → expand Sound, video and game controllers → right‑click device → Update driver. If update fails, try Uninstall device then reboot to force reinstall. Test again.
- If app still silent, check Exclusive Mode and disable audio enhancements on the playback device. Change default format if necessary.
- Try a different output (plug in headphones or switch to internal speakers). If the alternative works, the issue is device‑specific.
- If the issue began after a Windows update or driver change, try rolling back the driver or a System Restore point created before the problem began. Users frequently find that a recent update caused selective app audio failures.
Real user examples and what they teach us
- Many users reported that a browser or Store app was muted in the Volume Mixer while system sounds were audible — the fix was simply unmuting the app. This reinforces the point that the Volume Mixer is the first check for every silent app.
- Several posts describe audio disappearing after a Windows update; updating or rolling back drivers restored app audio. Those reports highlight that driver‑update timing exactly matches feature updates as common failure points. When this happens, a device driver rollback or reinstall from the OEM is often required.
- Cases where one user’s account had working system sounds while another account didn’t indicate profile‑specific settings (custom sound schemes, registry entries, or per‑user app routing). If audio problems are only in one Windows user profile, try creating a new profile to isolate the issue.
When to escalate: hardware, firmware, or OS problems
If you’ve exhausted the steps above and app audio still fails:
- Test the hardware with another OS or a live boot environment (if you’re comfortable). If audio fails there too, suspect hardware.
- Check BIOS/UEFI to ensure onboard audio is enabled.
- If multiple feature updates correlate with the problem and drivers/rollbacks don’t help, you may be facing a deeper compatibility issue; consider contacting the device OEM or Microsoft support. Community posts describe cases where formal support was needed after driver reinstalls and restarts failed.
Safety and privacy considerations
- Back up drivers or create a Restore Point before changing system drivers. Uninstalling or forcing vendor drivers can make a system unbootable in rare cases.
- Only download drivers from trusted OEM sites or the chipset/audio vendor. Avoid third‑party driver packages that aren’t verifiable.
- When contacting support, share precise symptoms, the results of Volume Mixer checks, output device assignments, and any recent Windows updates or driver changes. This saves time and avoids unnecessary steps.
Prevention: reduce the chance of recurrence
- After a major Windows update, check App volume and device preferences and the Volume Mixer before assuming a driver is broken.
- Keep vendor drivers current, but prefer drivers from the PC or motherboard manufacturer when possible; they’re validated for your model.
- Use System Restore points or a reliable system image so you can revert quickly if audio breaks after an update.
- If you rely on audio for work, test your critical apps after major updates and keep an alternate audio device on hand.
Strengths and limitations of Microsoft’s troubleshooting guidance
Microsoft’s official steps are precise and well‑targeted: they address the most likely causes in the right order (per‑app settings, per‑app device, services, drivers). That makes them efficient for most users. However, the guidance assumes a baseline familiarity with Settings, Device Manager, and Services, which may be unfamiliar to less technical users. The Microsoft checklist is strong at triage but deliberately conservative about more aggressive driver changes; that’s appropriate because device drivers affect system stability.
Community threads show two additional realities: (1) many problems are transient and resolved by restarting audio services or the PC; and (2) some failures are caused by feature updates or vendor driver interplay that require vendor driver reinstalls or rollbacks. That practical nuance complements Microsoft’s official flow.
Unverifiable or uncertain areas — exercise caution
- Claims that a very specific Windows update universally broke audio for a brand/model are often anecdotal. While multiple users may report the same behavior, unless the vendor or Microsoft publishes a compatibility advisory it remains user evidence rather than confirmed causation. When reports suggest a certain Windows update caused issues, treat it as a strong hypothesis and attempt a rollback or driver reinstall, but avoid stating it as universal fact. Several forum threads show patterns but not official confirmations.
- When using third‑party driver‑management utilities, the long‑term impact on stability and security is unclear and often negative. Avoid automated driver updaters unless you can verify exactly what they change.
Quick reference: CLI / UI shortcuts
- Volume Mixer: right‑click speaker → Open Volume Mixer.
- App device preferences: Settings → System → Sound → App volume and device preferences.
- Services: Start → type services.msc → locate Windows Audio and Windows Audio Endpoint Builder → Restart.
- Device Manager: right‑click Start → Device Manager → Sound, video and game controllers → Update driver / Uninstall device.
- Sound Control Panel (advanced options): Control Panel → Sound → Playback → Device Properties → Advanced.
Conclusion
When system sounds work but app audio does not, the problem is rarely catastrophic — it’s usually a configuration or driver issue that you can diagnose quickly with Volume Mixer, per‑app device checks, and a service restart. If those basic steps fail, move to device driver updates or rollbacks and check exclusive mode or audio enhancements. Be cautious when reinstalling drivers: back up, prefer OEM drivers, and avoid unverified third‑party utilities. Community reports repeatedly show that the layered approach (mixer → per‑app device → services → drivers) finds and fixes the majority of cases with minimal risk. If after this workflow the app still won’t produce sound, collect your diagnostics (affected app, evidence of device assignments, recent updates) and escalate to the device vendor or Microsoft support, because you may be facing a rare driver/firmware incompatibility that requires vendor intervention.
Source: Microsoft Support
Fix app audio not working while system sounds work in Windows - Microsoft Support