What’s new and why it matters

On September 8, 2026, the Windows 11 security update (branches 26H1/25H2/24H2 and 23H2) introduced an issue that can leave some USB Audio Class 1.0 devices without sound. Microsoft added the problem to the Release Health dashboard and, six days later, shipped an out-of-band (OOB) update that mitigates part of the symptoms. This sequence touches Copilot pilots, deployments on NPU-enabled hardware, and creative environments relying on multichannel USB audio interfaces. (learn.microsoft.com)

In parallel, a separate incident impacted ARM64 PCs (for example, Surface Pro 11 and Surface Laptop 7): after the August 11, 2026 updates, Microsoft Teams and the new Outlook might fail to launch or close unexpectedly. For administrators operating mixed x86/ARM fleets, coordinating September maintenance windows and update rings has required extra caution to avoid downtime and user disruption. (support.microsoft.com)

Exact timeline: from KB5124012 to the September OOB

September 8, 2026: the cumulative security update KB5124012 lands for Windows 11 version 26H1 (build 28000.2954). After installation, Microsoft documents that certain USB Audio Class 1.0 devices may fail to start, display Code 10, produce no audio, or expose non-responsive controls. (support.microsoft.com)

September 14, 2026: Microsoft publishes OOB KB5129194 for 26H1 (28000.2956). This update resolves, among other points, failures in multichannel modes (e.g., 8 channels or 3D) for USB Audio Class 1.0 devices, while the note itself warns that not all audio symptoms are covered and refers admins to the known issues section for follow-up. The same day, equivalent OOB packages ship for 24H2/25H2 (KB5129195) and 23H2 (KB5129242). (support.microsoft.com)

What was breaking exactly

Affected devices report one or more of these symptoms after September’s B release: “This device cannot start (Code 10)” in Device Manager, total loss of audio output, volume controls that do not respond or remain stuck at zero, and sound settings pages that fail to load. The pattern is limited to peripherals implementing USB Audio Class 1.0. (support.microsoft.com)

In studio or creator scenarios, the impact has been more severe on multichannel configurations (7.1/8‑channel interfaces, 3D virtualization), which remained unstable until the September 14 OOB. In standard stereo setups, many devices continued to function, although Microsoft kept tracking active in Release Health to monitor other residual symptoms. (support.microsoft.com)

Status and scope today (September 20, 2026)

Microsoft marks the issue as mitigated following the September 14 OOB releases, with the caveat that cases outside multichannel audio may persist. The documented scope spans Windows 11 clients 26H1/25H2/24H2/23H2 and, in certain matrices, supported Windows 10 versions; Windows Server releases do not appear affected by this audio incident. (learn.microsoft.com)

Regarding the ARM incident with Teams and the new Outlook, Microsoft associated it with updates released on August 11, 2026 (KB5121003) or later, with explicit mention of Surface Pro 11 and Surface Laptop 7. In Release Health it is shown as resolved across the September cycle; administrators should validate that ARM devices have received the latest cumulative updates before closing the case. (support.microsoft.com)

Separate incident: incorrect Defender notifications and the fix

Beyond audio issues and the impacts around RDS/Hyper‑V, Microsoft recorded incorrect notifications in September stating that “Microsoft Defender Antivirus is turned off” even though it remained active. In the 25H2 dashboard, this incident is marked resolved on September 17, 2026. (learn.microsoft.com)

On the same day, the Update Catalog published Defender platform version 4.18.26080.4 (KB4052623). While Microsoft does not explicitly tie both pages together, in practice administrators report that the .4 platform normalizes compliance status. We recommend targeting 4.18.26080.4 or later in fleet checks. (catalog.update.microsoft.com)

What to do now: official steps and quick IT checklist

Recommended steps: 1) Install the OOB for your branch and reboot. On 26H1, KB5129194; on 24H2/25H2, KB5129195; on 23H2, KB5129242. 2) If you applied temporary mitigations for RDS/Hyper‑V via Group Policy, restore them to normal and re‑enable the indicated policies per the notes, then install the OOB and restart. 3) Update Defender to platform 4.18.26080.4 or higher (KB4052623); verify the version after reboot. 4) On ARM, confirm that Surface Pro 11/Laptop 7 devices have received the September cumulatives and that Teams/Outlook start correctly. 5) Keep monitoring the Message Center and Release Health for further status changes. (support.microsoft.com)

Quick IT checklist: • Verify installed KBs by branch and compile a version matrix. • Test multichannel audio peripherals and capture scenarios. • Validate ARM devices with Teams/Outlook. • Ensure Defender is at 4.18.26080.4+ and compliance is green again. • Adjust maintenance windows to complete OOB rollout across the fleet. • Keep Windows release health notifications active in the admin center for upcoming changes. (support.microsoft.com)

Context and follow-up

Windows 11 26H1 is a release specifically aimed at new devices arriving in 2026; it is not intended as an in‑place feature upgrade from 24H2/25H2, which explains part of the availability differences observed by deployment teams. Plan pilots and image pads with this support scope in mind. (learn.microsoft.com)

For operational follow‑up, anchor three sources: 1) the Windows release health dashboard per version, 2) the KB pages with history and known issues, and 3) the Microsoft 365 Message Center, which concentrates time‑sensitive production advisories. With minimal discipline —peripheral validation, Defender version control, and ARM canaries— you can reduce surprises in the next window. (learn.microsoft.com)