In October 2026, Microsoft continues to grapple with lingering issues from its September updates for Windows 11. Despite the rollout of a mandatory Patch Tuesday update, an emergency patch, and an optional release, users are still encountering a range of problems. The latest revelation from Microsoft indicates that certain applications and games may experience crashes if they utilize the built-in audio decoding feature of Windows. The company is currently working on a resolution for this issue.
Some apps and games could crash when decoding audio
As highlighted by Windows Latest, Microsoft has confirmed that applications and games relying on Windows’ built-in AC-3 (Dolby Digital) audio decoding may crash unexpectedly when users adjust the volume, modify audio settings, or engage specific audio features. While Microsoft has not disclosed the exact nature of the audio malfunction, users experiencing performance issues post-update may want to consider avoiding audio playback or disabling recently activated audio features.
“The incidence of this issue varies based on the activities performed by these applications. In some instances, the application may fail to launch or close unexpectedly,” Microsoft noted in an official document. “In other cases, the application may function normally until certain features are utilized, such as music playback. The affected applications can include games, media players, and various productivity tools.”
Microsoft says most modern apps shouldn’t be affected
According to Microsoft, the bug is not expected to impact a significant number of users, as it primarily affects older applications and games that depend on the built-in decoder. The company reassures users that most modern applications should operate without issue when playing audio, although it has not specified which applications or games might be impacted. This situation is distinct from the USB audio bug reported in September, which caused some audio devices to cease functioning, display a Code 10 error in Device Manager, or render Sound settings unresponsive.
Windows 11’s September updates fixed some bugs and introduced another
September has proven to be a tumultuous month for Windows, raising questions about Microsoft’s quality control measures. Initially, the rollout of KB5124008 on September 8 introduced several highly anticipated features, including a movable taskbar, a resizable Start menu, and a Bing-free Windows Search. However, the excitement was soon overshadowed by a series of complications.
September also marked a significant increase in security fixes, with Microsoft addressing 974 vulnerabilities compared to just 86 in September 2025, reflecting a staggering year-over-year increase of over 1,000%.
| Month | Microsoft CVEs in 2025 | Microsoft CVEs in 2026 | YoY |
|---|---|---|---|
| January | 159 | 112 | -29.6% |
| February | 63 | 59 | -6.3% |
| March | 57 | 83 | +45.6% |
| April | 126 | 165 | +31.0% |
| May | 78 | 137 | +75.6% |
| June | 66 | 206 | +212.1% |
| July | 130 | 622 | +378.5% |
| August | 111 | 421 | +279.3% |
| September | 86 | 974 | +1,032.6% |
| January-September | 876 | 2,779 | +217.2% |
As the volume of security fixes escalates, the potential for new bugs to emerge within Windows also increases. Microsoft has acknowledged the challenges posed by the extensive nature of last month’s updates, which complicate the identification of root causes for various issues. Reports have surfaced regarding problems with Remote Desktop, audio, and File History backups, alongside additional concerns such as black screens and AMD GPU errors, including driver timeouts and freezes.
Microsoft’s emergency update didn’t fix everything
On September 14, Microsoft issued KB5129195, an emergency update aimed at addressing several reported issues, including broken Remote Desktop connections and folder-sharing problems affecting applications like Claude Cowork. However, it soon became apparent that the audio issues were only partially resolved, with some audio devices still malfunctioning.
Furthermore, the emergency update inadvertently disrupted the functionality of File History, a valuable backup tool that allows users to save copies of their files on external drives. Many users were caught off guard when they discovered that File History had ceased backing up their files, despite having a drive connected or a network location configured. Microsoft has since acknowledged this oversight and is investigating the matter.
The optional update brought a File History fix and another problem
On September 22, the optional KB5124010 update was released, which Microsoft claimed would rectify the File History feature. Testing revealed that while File History could now detect drives, it still faced issues with backup timestamps and file versions not updating correctly, undermining its intended purpose.
Compounding the frustration, this update has led to new crashes in various applications and games, leaving users disillusioned with the Windows update process. The cycle of installing updates to resolve issues only to encounter new bugs has become increasingly vexing for many. Currently, Microsoft is focused on addressing the audio-decoding bug, though a timeline for the fix remains unspecified. “Microsoft is working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available,” the company stated.
