www.it-connect.fr
Windows 11 26H2 Rolls Out, but Microsoft Already Lists 3 Known Bugs
Windows 11 26H2 has been available since September 29, 2026, and many users are asking the same question: are there bugs and issues with this release? The answer is yes, because Microsoft is already tracking three known problems in this version. Here is what you need to know before deploying it.
Microsoft began rolling out Windows 11 26H2, also known as the Windows 11 2026 Update, on September 29, 2026. As I explained in my article on the availability of Windows 11 26H2, its new features, and its support lifecycle, this version arrives as an enablement package on machines running Windows 11 24H2 and 25H2. The rollout is gradual: it first targets users who have enabled the option to receive the latest updates as soon as they are available, and will then expand to everyone else.
On the reliability side, Microsoft’s Windows 11 26H2 status page does not currently mention any compatibility-related block (safeguard hold). However, it already lists three known issues, although they were already known.
Three bugs inherited from the August and September updates
These three issues did not begin with Windows 11 26H2. They are inherited from earlier releases... which is not surprising, since this version shares the same foundation as 24H2 and 25H2, and therefore logically has the same flaws. The dedicated 26H2 page shows no originating update, because this version has not had one yet (so, on paper, it is a release shipped with bugs...), but the Windows 11 25H2 page reminds us that these bugs are linked to updates KB5120998 (August 27, 2026) and KB5124008 (September 8, 2026).
- Trust relationship loss: on some devices, the secure channel with the local Active Directory is broken. Users can no longer sign in with valid domain credentials and receive the message indicating that the trust relationship failed. Cached credentials continue to work and domain controllers are not affected. Source: KB5124008.
- Black screen after sign-in: this issue has been observed on Azure Virtual Desktop hosts using FSLogix, more often with some existing profiles. The desktop does not load and File Explorer crashes. Two workarounds are available: restart
explorer.exethrough Task Manager (Run new task) or deploy the Known Issue Rollback (KIR) Group Policy provided by Microsoft. Source: KB5120998. - Silent USB audio devices: some USB Audio Class 1.0 devices show Code 10 in Device Manager, produce no sound, or have stuck volume controls. The out-of-band update KB5129195 released on September 14, 2026 only fixed multichannel failures (8 channels, 3D audio). For everything else, audio remains unavailable while waiting for a fix. Source: KB5124008.
In other words, these bugs were not introduced by the move to 26H2: devices running 24H2 and 25H2 already have these issues.
Have you noticed any bugs?
Now I would like to use this article to ask whether, on your side, you have noticed any bugs after upgrading to version 26H2? Or, on the contrary, whether everything is working fine. I think it is valuable to share feedback and real-world experiences on this topic, especially in a spirit of mutual help. Feel free to comment on the article and share your situation and setup.
This version is so close to the previous two that I do not think it should be affected by any new bugs exclusive to it. A bug present in 25H2 should also be present in 26H2, and vice versa. What could create the impression of a new bug is if you install an update (the mandatory early-September update or the optional late-September update) at the same time as upgrading to 26H2. Anyway, that is just my opinion: I am looking forward to your feedback.
The floor is yours...
