Microsoft has confirmed another problem in the September Windows 11 update cycle: some PCs may lose audio output after installing KB5124008, and in certain cases microphones or multichannel audio setups may also stop behaving normally. For home users, that can mean a silent laptop after a reboot. For IT teams, it can mean help-desk tickets from conference rooms, contact-center workstations, classroom PCs, and employees who suddenly cannot join calls with working sound.
The affected update is associated with Windows 11 versions 24H2 and 25H2, moving systems to builds 26100.9445 and 26200.9445 respectively. Windows Latest reports that Microsoft has acknowledged failures where audio devices may not start or produce sound after recent Windows updates. The visible symptom may be deceptively simple: the speaker icon appears normal, the volume slider moves, but no sound plays. In other cases, Windows sound settings may become unresponsive, making the usual first-line troubleshooting path less useful.
What appears to be happening
According to the report, the confirmed issue is tied to USB Audio Class 1.0 devices. Device Manager may show the affected audio device with the familiar but vague message: “This device cannot start (Code 10).” That matters because Code 10 is not a diagnosis by itself; it is a sign that Windows could not start the device stack successfully. Reinstalling the same driver, disabling and re-enabling the device, or pushing the volume to 100 percent may not resolve the problem if the trigger is in the Windows update layer rather than in a vendor control panel.
Windows Latest also notes related reports involving microphones and multichannel audio. Some users may find that an 8-channel, 3D, or surround configuration no longer produces output even when the device itself is detected. Microsoft’s temporary advice, as reported, is to switch affected hardware to a 2-channel configuration where possible. That will not preserve every speaker layout, but it may restore basic sound while Microsoft works on a permanent resolution.
Why this is more than a consumer annoyance
Audio failures are disruptive because they are discovered at the worst possible time: when a meeting starts, a webinar goes live, a classroom begins, or a support agent logs in for a shift. In managed environments, this bug should be handled like any other compatibility regression. Inventory the systems that depend on USB audio adapters, docking stations, classroom speaker systems, meeting-room bars, headsets, or specialized multichannel hardware. Then decide whether those devices can tolerate a temporary two-channel fallback or need a deployment pause.
If your organization has not yet deployed KB5124008 broadly, treat the update as a change-management event, not a routine reboot. Patch Tuesday security fixes are important, but staged deployment rings exist for exactly this reason. Pilot devices should include audio-heavy scenarios, not just standard office laptops. A small validation group should test speakers, microphones, Teams or Zoom calls, browser audio, recording applications, and any room-control software before a wider rollout.
Practical checks for affected PCs
Start with the Windows build number. Open Settings, go to System, then About, and confirm whether the device is on the affected 24H2 or 25H2 build. Next, test sound with more than one application. If browser audio, system sounds, and conferencing apps are all silent, the problem is more likely to be at the device or Windows audio layer than inside a single app.
Then open Device Manager and review the audio device status. If the device reports Code 10 after the update, document the device model, driver version, connection type, and Windows build before making changes. That information will be useful if you need to escalate through Microsoft support, an OEM, or an internal endpoint-management team. Avoid repeatedly uninstalling and reinstalling the same driver unless you have a rollback plan; it can consume time without addressing the underlying regression.
For multichannel systems, test a two-channel configuration as a workaround. For USB audio hardware, try an alternate output path if one is available, such as built-in speakers, a different USB adapter, HDMI audio through a monitor, or a wireless headset. Windows Latest reports that wireless audio devices do not appear to be affected in the same way, so Bluetooth or proprietary wireless headsets may be a short-term option for users who need to join calls immediately.
Guidance for administrators
Administrators should review update rings and pause expansion if audio-dependent roles are at risk. Help-desk scripts should ask whether the issue began immediately after the September update, whether the device uses USB audio, and whether Device Manager shows Code 10. Endpoint-management dashboards can be used to identify machines on builds 26100.9445 or 26200.9445 and correlate them with incoming audio tickets.
It is also worth preparing a user-facing advisory. Tell users not to spend time changing every app setting if Windows itself cannot start the audio device. Provide a short list of approved workarounds: try a different audio device, switch to stereo mode if applicable, use a wireless headset, or move to another workstation for urgent calls. Keep rollback decisions centralized, because removing a cumulative update can reintroduce security exposure and may not be appropriate for every device.
Bottom line
Microsoft has not yet provided a permanent fix, so the safest approach is controlled deployment and clear troubleshooting guidance. If KB5124008 is already installed and audio is broken, focus on confirming the build, checking Device Manager, testing two-channel mode, and providing alternate hardware where possible. If the update is still pending across your fleet, validate audio scenarios before pushing it to users who depend on microphones, USB headsets, docking stations, or multichannel speaker setups.
Source: Windows Latest source