Quick answer: Check the exact USB audio device and its Device Manager status before reinstalling drivers. Microsoft lists an update-related USB Audio Class 1.0 issue that can cause Code 10 or silence. Some symptoms have a fix; other cases remain under investigation.
Status reviewed 10 November 2026: partially resolved. The issue is limited to USB Audio Class 1.0 hardware. Code 10 on a different device is not proof of this regression.
Record the device and the update
Open Device Manager, locate the affected audio device, and read Properties > General. Keep the exact status message, device model, driver information, Windows version, and installed update from Settings > Windows Update > Update history.
Check the headset manufacturer's documentation to establish its USB audio class. An entry named "USB Audio Device" by itself is not sufficient identification.
If there is no Device Manager warning, check Settings > System > Sound and select the intended output and input. Compare playback in another app. A healthy Windows playback test with silence only in Teams or Zoom points to a different investigation.
What Microsoft has confirmed
Following September 2026 updates, affected USB Audio Class 1.0 devices can show Code 10, produce no sound, or leave volume controls unusable. Microsoft's notices include Windows 10 and several Windows 11 versions, including 24H2, 25H2, 26H1, and 26H2.
The September 14 out-of-band updates addressed the multichannel or 3D-audio part of the problem. On the 24H2/25H2 update branch, Microsoft identifies KB5129195 for that partial resolution. This does not establish a fix for every remaining Code 10 or silent-device case. Use the current notice and the package for your exact Windows version.
Choose the next step from the observed symptom
- Save your work, complete any pending restart, and check for applicable supported Windows updates. On a managed PC, use your organization's update process.
- For a device connected through a hub or dock, test a direct USB port. This checks the connection separately from the Windows regression.
- If stereo works but multichannel playback fails, record both outcomes and compare the installed update with Microsoft's partial fix. If the device offers a stereo option, it may provide a temporary way to work.
- If Code 10 or silence persists on an identified Class 1.0 device, give support the model, status, update history, and test results. Microsoft directs affected administrators to its business support channel for remaining cases.
Keep a known-working audio option available for urgent calls if you already have one. Deleting audio-class registry filters is not a general remedy for this update issue. For other microphone Code 10 causes, see the microphone diagnosis guide.
Verify playback and microphone use separately
Play a familiar clip through the selected headset, then test its microphone in the original calling app. If the problem followed reconnection, test reconnecting too. Record a partial recovery honestly: restored output does not prove the microphone works.
Get help with this USB audio problem
Againly can help investigate the device and propose a plan for review. An unresolved Windows regression or faulty hardware may require Microsoft or manufacturer support.
Diagnose my USB headset problem
Related: Windows 11 26H2 known issues.