block audio driver

Question

The Windows Driver Policy for mbox 3 not working @

Answer 1

Hi Kelven Davis,

Thanks for the details so far.

To better understand what’s happening with the Mbox 3 driver, could you please provide a bit more information? It would be helpful to know your Windows version and build (you can check this by pressing Windows + R, typing winver and pressing Enter), along with any error code or message shown in Device Manager.

If possible, please also share a screenshot of the error so we can take a closer look. In the meantime, kindly give the AI-generated suggestions a try and let me know how it goes.

---

If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Windows 11 does not provide a built‑in “policy” UI to block a specific third‑party audio driver such as the mbox 3 driver. When an audio driver is installed and selected for a device, Windows Audio Services manage it, and audio will not work correctly if those services are stopped or misconfigured.

For USB or external audio devices that misbehave (for example, driver not starting, audio services not responding, or the wrong driver being selected), the supported approaches are:

1. Remove or switch the device/driver
   • Open Device Manager → expand Sound, video and game controllers.
   • Double‑click the problematic audio device (for example, a USB audio interface).
   • On the Driver tab, select Uninstall device.
   • If the guidance explicitly says so for that scenario, do not select Delete the driver software for this device; this is used when Windows should fall back to the standard USB audio class driver instead of a device‑specific one.
   • Alternatively, connect the device to a different USB port so Windows can bind it differently and possibly use a different driver instance.
2. Prefer the standard USB Audio 2.0 class driver instead of the vendor driver
   • Some USB audio problems occur when a device‑specific driver replaces the standard USB Audio 2.0 driver (usbaudio2.sys) and then fails to work correctly.
   • In those cases, uninstalling the device (without deleting the driver software) and reconnecting it, or installing the device‑specific driver before first connection, can ensure Windows selects the correct driver.
3. Ensure Windows Audio Services are running
   • If audio services are not running, no audio device (including mbox 3) will function.
   • Open Services (for example, via Control Panel → Administrative Tools → Services).
   • Confirm Windows Audio and Windows Audio Endpoint Builder are set to Automatic and are Running.
   • Stopping these services will effectively disable all audio devices, but this is a global switch, not a per‑driver “block policy,” and will prevent all sound output.
4. For persistent driver issues
   • If the driver does not start or repeatedly fails, check the system event log and collect audio logs as described in the USB Audio 2.0 driver troubleshooting guidance, then report the problem via Feedback Hub.

Windows’ DRM and audio driver requirements focus on preventing untrusted or non‑DRM‑compliant drivers from handling protected content; they do not expose an end‑user control to selectively block a specific audio driver while allowing others.

---

References:

• USB audio device not playing
• USB Audio 2.0 drivers
• User-Mode WDM Audio Components
• DRM Requirements
• Windows 10 doesn't install specific drivers for USB audio devices on the first connection