FULL AI ANALYSIS

USB DAC plays Windows system sounds but conferencing apps receive silent input on Windows 11

Generated Oct 3, 2026, 12:35:03 AM

Analysis summary

System playback and Windows test functions indicate the USB DAC hardware and basic driver are functional. The fact that a different USB microphone works, and OBS records when elevated, suggests a per-process permission or shared-access issue: either conferencing apps lack permission or a non-elevated process cannot access the device due to an exclusive lock by another process or driver-level policy. Event Viewer warnings about inability to open the device strengthen the hypothesis of access conflicts or per-process ACLs.

Possible causes

A driver or vendor utility running as SYSTEM or a different privilege level blocks non-elevated apps from accessing the device.

85%

One process is holding the device in exclusive mode preventing conferencing apps from opening the input stream.

70%

Conferencing apps are attempting to use an incompatible sample rate/format and failing to negotiate with the device.

15%

Windows privacy or group policy settings restrict microphone access for specific app types or non-store apps.

Suggested fixes

Diagnostic step 1

Open Resource Monitor / Process Explorer and identify processes with open handles to the USB audio device (search for the device name or wave_*.sys). Reboot into safe mode and test whether apps can access the device (safe mode reduces interference from third-party drivers).

Diagnostic step 2

Temporarily disable vendor audio utilities and any system-wide audio processing services; reboot and test to see if conferencing apps regain mic access. These steps are reversible.

Diagnostic step 3

In Windows Sound Device Properties > Advanced, try toggling 'Allow applications to take exclusive control of this device' off for the input device and then restart conferencing apps.

Diagnostic step 4

Compare the default recording format across apps (48 kHz vs 44.1 kHz). Configure the device to a common sample rate and test. Use WASAPI loopback tools to verify device openability from user-space.

Diagnostic step 5

If access errors persist and you observe driver-owned handles by system processes, escalate to vendor driver support and collect a Process Explorer handle dump and relevant ETW traces for deeper analysis.

Contact • Help • API Docs • Careers • Terms • Privacy • Cookies • Ads