Sunday, September 13th 2026
Windows 11 September Update Kills Audio Output on Some PCs
Windows 11 continues its streak of breaking things, as Microsoft has confirmed that there is an issue with the latest September security update. According to the updated support document, Microsoft confirmed that the KB5124008 Windows security update can break audio output on some PCs. Specifically, this security update introduces issues with USB audio devices, where users of these audio output devices can't get any output from them. Messages include "This device cannot start (Code 10)" in the device manager, which fails to recognize some devices, while other symptoms can include unresponsive volume controls, no volume at all, no audio output, unresponsive sound settings, or the complete lack of detection in the device manager.
Microsoft confirmed that this only affects USB Audio Class 1.0 devices, but the current workaround is quite strange. Some USB audio devices can continue to function in standard stereo configuration. However, when switching to multichannel audio features such as 8-channel or 3D audio mode, the device can fail. The company is stating that the mileage will vary depending on the device type and use case, as some users were able to restore audio functions by switching to 2-channel audio mode in cases like these. However, do note that it doesn't mean that the problem is solved, but that only a few devices can find a workaround until a temporary fix is in place. Microsoft is reportedly working on a resolution.
Interestingly, this is not the first case of strange bugs as Microsoft has already dealt with external devices that either break the OS or simply stop working after an OS update. Notably, a recent example is the Windows 11 August update, which reset custom cursors to an oversized default one. In some cases, the color and size settings don't stick, no matter how many times they are changed. This update has also caused gameplay issues, such as forced crashes, random freezing, errors, and unexpected device restarts due to RGB peripherals. We ran a poll of nearly 33,000 responses, with the majority of respondents stating that Windows 11 is degrading in quality of use, even after Microsoft's many promises. Hence, the streak of bad updates continues to this day.
Sources:
Microsoft, via Windows Latest
Microsoft confirmed that this only affects USB Audio Class 1.0 devices, but the current workaround is quite strange. Some USB audio devices can continue to function in standard stereo configuration. However, when switching to multichannel audio features such as 8-channel or 3D audio mode, the device can fail. The company is stating that the mileage will vary depending on the device type and use case, as some users were able to restore audio functions by switching to 2-channel audio mode in cases like these. However, do note that it doesn't mean that the problem is solved, but that only a few devices can find a workaround until a temporary fix is in place. Microsoft is reportedly working on a resolution.
63 Comments on Windows 11 September Update Kills Audio Output on Some PCs
(iykyk)
Regards,
Fred.
This guy and myself are like the only 2 people in the world who has a good running Windows OS lol..
Good tuning bud :cool:
They rather have you or a billion of other users report the bugs created by it, and resolve it again.
I am not surprised at all.
Then those testers were fired dozen years ago around time of Satya's "rise to power" starting downward spiral of quality.
Sorry I couldn't hear the bugs over my USB
Forum Guidelines (TPU)Regards,
Fred.
Take for instance the new taskbar in Windows 11. It's only now, several years later, that the Windows 11 taskbar is getting to be close to feature parity with what we've had for decades. Why the hell was the new taskbar released if it wasn't ready?
They really need to slow the hell down already. Stop with the constant new features and concentrate on stabilizing the system.Yep. They went to a system where the developers tested their own code. Of course the developer is going to know how the program is supposed to work or what input it's supposed to take, they're the developer! You need someone to go in after it's written to bang on it and otherwise try to break it. Today? That's us, the end-user. That's why Windows is so full of telemetry garbage.