USB headset (USB Audio Class 1.0) fails with Code 10 / STATUS_DEVICE_DATA_ERROR on Windows 11 after KB5124008

Question

USB headset (USB Audio Class 1.0) fails with Code 10 / STATUS_DEVICE_DATA_ERROR on Windows 11 after KB5124008

Yefrank Castellano 0

Title: USB headset (USB Audio Class 1.0) fails with Code 10 / STATUS_DEVICE_DATA_ERROR on Windows 11 after KB5124008

Description:

A new USB headset works fine on another laptop, but on my desktop PC the device shows a yellow warning in Device Manager: "This device cannot start (Code 10)", status STATUS_DEVICE_DATA_ERROR. No device appears under Sound > Playback. The symptoms match the known issue Microsoft lists for KB5124008 / KB5129195 ("USB Audio Class 1.0 devices with error Code 10 or no output").

System:

Windows 11 Pro, version 26H2, build 26300.9457
Installed updates: KB5124008 (2026-09-10), KB5129195 (2026-09-16), KB5121794 26H2 enablement package (2026-10-07), KB5126052 (.NET)
Motherboard: ASUS PRIME A520M-K, BIOS 3621 (2025-01-13)
CPU: AMD Ryzen 5 5500, 16 GB RAM, NVIDIA RTX 3050

Affected device:

Seisa E7005a USB headset, recently purchased
Hardware ID: USB\VID_C00A&PID_6506&REV_0100&MI_00
Service: usbaudio (generic Microsoft "USB Audio Device" driver)
Error: Code 10, STATUS_DEVICE_DATA_ERROR

What I already tried (no change):

Different USB port (device location changed, same error)
Installed the AMD chipset driver
Update driver > "Let me pick from a list": only "USB Audio Device" (Microsoft) and USBMidi2-ACX are offered; the first one fails the same way
Restarted and reconnected the headset

Notes:

This is the first time I connect this headset to this PC, so I can't confirm it worked before KB5124008.
On the laptop [Windows version/build of the laptop: fill in] it works correctly.
KB5124008 does not appear under "Uninstall updates" because it is included in KB5129195.

Questions:

Is there a fix or workaround for Code 10 on USB Audio Class 1.0 devices on this build?
Will it be fixed in the October 13, 2026 update?
Can you confirm that Windows 11 26H2 (26300.x) is also affected?

0 comentarios

2 respuestas

Su respuesta

Answer 1

Hello,

To figure out what is going on here, I need to narrow down whether this is actually the audio stack regression or a controller negotiation failure on your desktop.

Were the different USB ports you tested located directly on the rear motherboard I/O panel, or were you plugging into front case ports or a hub? Also, were those specifically USB 2.0 ports or USB 3.2 ports?

If you switch Device Manager to View by connection, is the parent USB Composite Device reporting as working properly, or is the error code only showing up on the audio child device?

Lastly, do any other USB audio devices or USB microphones currently work on this desktop without issues?

Answer 2

Benjamin Pucheta 0

Ya lo arreglaste? por favor respondeme

0 comentarios