Windows 11’s September update, released on the 8th, has quickly drawn attention for a series of issues that have prompted Microsoft to acknowledge and investigate various problems. These include complications with Remote Desktop, USB audio, and applications based on Linux and WSL, such as Claude Cowork. Additionally, Windows Latest reported failures in File History, crashes of Explorer.exe, and instability with AMD GPUs. An emergency update was issued on September 14, yet it failed to resolve all the outstanding issues.
Nine months of Windows 11 updates have produced a long list of issues and fixes
In our review of the nine monthly updates from January to September 2026, it became evident that Windows 10 has experienced significantly fewer bugs compared to its successor. The troubles began in January with KB5074109, which led to black screens, frozen Outlook Classic POP profiles, and authentication issues with Azure Virtual Desktop. While Microsoft did release a fix, the problems persisted, culminating in confirmed BSODs and boot failures on some commercial PCs.
March stood out for its relative calm, as reports of BSODs and inaccessible drives were traced back to a handful of cases, with some misinformation circulating online. However, a genuine issue arose with KB5079473, which disrupted Microsoft account sign-ins across Teams, OneDrive, Edge, and Office. This was rectified 11 days later with an out-of-band update, KB5085516. Microsoft also had to retract the optional KB5079391 preview due to an installation error loop.
April and May continued the trend of bugs, with KB5083769 triggering BitLocker recovery on certain PCs and requiring multiple reboots for installation. May’s KB5089549 faced installation failures on systems with minimal free EFI System Partition space, necessitating an emergency patch from Microsoft.
The months of June and July proved particularly challenging. KB5094126 caused boot failures and BitLocker recovery loops on HP business PCs, while July’s KB5101650 was blocked on Dell PCs due to conflicts with Intel drivers, resulting in unexpected shutdowns and battery drain. These issues originated from the previous month’s preview update and carried over into July’s mandatory security update.
August offered a slight reprieve, as KB5121003 appeared to crash certain games. However, investigations revealed that the crashes were linked to a third-party driver rather than a fault with Windows itself. September, unfortunately, marked the most problematic month yet, with a litany of issues including RDP failures, audio complications, Linux/WSL problems, and ongoing GPU instability, leading to the need for an emergency update that still left some concerns unresolved.
| Month | Windows 11 | Windows 10 |
|---|---|---|
| January | Multiple confirmed/reported regressions | Several issues, quickly fixed |
| February | No major new known regression | No known issue |
| March | Microsoft account sign-in + failed optional update | No known issue |
| April | BitLocker and installation issues | Smaller Remote Desktop/BitLocker issues |
| May | Update installation failures | Limited enterprise BitLocker issue |
| June | Boot failures, BitLocker recovery loops, OneDrive and Recycle Bin bugs | A smaller group of application/Explorer issues |
| July | Dell/Intel compatibility problem | Limited BitLocker/TDI issues |
| August | Game crashes (traced to third-party driver, not Windows) | No major new issue documented |
| September | RDP, audio, Linux/WSL, File History, Explorer, GPU and domain issues | No comparable wave |
Windows 10 has bugs too, but look at what Microsoft is fixing
Windows 10 is not without its own set of bugs. In January, KB5073724 caused issues for some Secure Launch-capable PCs, which were resolved by February’s KB5075912. Microsoft’s release-health documentation indicated no new issues with February’s update, and March’s KB5078885 also shipped without known problems, effectively fixing the shutdown bug.
While Windows 10 did encounter some issues in June and July, they were relatively minor compared to the challenges faced by Windows 11. The September update for Windows 10, KB5122878, was a routine security-and-servicing release, contrasting sharply with Windows 11’s KB5124008, which required an emergency follow-up and multiple investigations into known issues.
It is noteworthy that Windows 10 continues to receive updates due to Microsoft’s commitment to Extended Security Updates (ESU), which has been extended until October 12, 2027, despite the initial support deadline being set for October 2025.
But why does Windows 10 get fewer bugs than Windows 11?
The relative stability of Windows 10 cannot solely be attributed to Microsoft’s perfection of the system; rather, it stems from a lack of significant changes. In contrast, Windows 11 is undergoing continuous enhancements, with Microsoft introducing highly requested features each month. The company is also embracing AI-assisted development, as noted by Distinguished Engineer David Fowler, who remarked on the evolving nature of coding.
Interestingly, while Microsoft is addressing a record number of security vulnerabilities with each update—723 known vulnerabilities were fixed in the recent September update—the rapid pace of development does not inherently equate to fewer bugs. The update history of Windows 11 serves as a reminder that software quality hinges on thorough testing, compatibility efforts, and a degree of restraint. Although Windows 10 may lack the excitement of new features, its current state of stability is a notable advantage in the ever-evolving landscape of operating systems.
