Windows 11 26H2 Rolls Out With Three Known Issues
Windows 11 26H2 arrives as an enablement package, but three known issues carried over from earlier updates are still open.
WINDOWS
10/28/20262 min read
Windows 11 version 26H2, also called the Windows 11 2026 Update, began rolling out on September 29, 2026. It arrives as an enablement package on devices already running Windows 11 24H2 or 25H2, which should make the upgrade small and quick for most fleets. However, IT-Connect reports that Microsoft already lists three known issues, and all of them were inherited from earlier updates rather than introduced by 26H2 itself.
The first issue affects domain-joined devices. Some machines lose the secure channel with the local Active Directory, and users see a message that the trust relationship failed, so they cannot sign in with valid domain credentials. Cached credentials still work and domain controllers are not affected. The report links this issue to KB5124008 (September 8, 2026) and mentions no workaround.
The second issue hits Azure Virtual Desktop hosts that use FSLogix, more often with some existing profiles. After sign-in the user gets a black screen, the desktop does not load, and File Explorer crashes. Two workarounds are described: restart explorer.exe from Task Manager by using Run new task, or deploy the Known Issue Rollback (KIR) Group Policy that Microsoft provides. This one is linked to KB5120998 (August 27, 2026).
The third issue involves USB audio. 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 (September 14, 2026) fixed only multichannel failures such as 8-channel and 3D audio. For the remaining cases no workaround is mentioned, so audio stays unavailable until a fix ships.
What should admins do? Because these problems already exist on 24H2 and 25H2, delaying 26H2 will not make them go away, but it is still wise to pilot the update on a small ring first. Include devices that sign in with domain credentials, any FSLogix-based AVD hosts, and users who rely on USB headsets or audio interfaces. If you run AVD with FSLogix, check whether the KIR Group Policy applies to you before a broad rollout. I am not certain which build numbers or cumulative updates currently carry fixes, so please confirm the details on the Windows release health pages and the linked KB articles before you change deployment rings.
Connect
Stay updated with latest Microsoft blog news
© 2025. All rights reserved.