Windows 11 26H2 Known Issues: What Microsoft Has Confirmed

Microsoft's own Windows 11, version 26H2 release health page now lists four known issues for the update, as of its October 9, 2026 refresh: one resolved domain-trust bug, two mitigated problems (USB audio devices and a black-screen sign-in issue on virtual desktops), and one still-open audio-decoding bug. Here is exactly what Microsoft has confirmed, which devices are affected, and what workarounds exist today.

What Microsoft has officially confirmed for 26H2

Windows 11, version 26H2 reached general availability on September 29, 2026, rolling out as a fast, servicing-based enablement update to eligible Windows 11 24H2 and 25H2 devices. Since then, Microsoft's Windows 11, version 26H2 known issues and notifications page has tracked four items. This is Microsoft's own official tracker — not forum chatter — and it is the same page IT administrators and support agents use to check whether a symptom is a known, acknowledged bug.

How the four issues line up with the 26H2 rollout timeline

Three of the four issues were opened before 26H2 even reached general availability, during the version's final preview and early-adoption window, which is typical: Microsoft tracks known issues across a shared servicing branch, and 24H2, 25H2 and 26H2 all ship cumulative updates from the same monthly package. The domain-trust bug was opened September 16, 2026, and fixed by September 22's KB5124010. The USB audio and black-screen issues were both opened earlier — September 11 and September 24 respectively — and marked "Mitigated" (meaning a workaround exists but no permanent code fix has shipped) on September 29, the same day 26H2 reached general availability. The AC-3 decoding bug is the newest entry, opened October 2 and still sitting at "Confirmed" as of this writing, meaning Microsoft has reproduced and acknowledged it but has not yet published any workaround beyond avoiding the affected legacy codec path.

That sequencing matters for anyone trying to judge how risky 26H2 is right now: the one truly new-to-26H2, unresolved regression is the AC-3 bug, while the USB audio and black-screen issues are really carryover problems that also show up on older Windows 11 versions and, in the USB case, even Windows 10 and several Windows Server releases.

Resolved: domain-joined PCs losing their secure channel with Active Directory

The most serious of the four issues is also the one Microsoft has already fixed. After installing 26H2, some machines protected by Credential Guard-protected machine accounts lost their secure channel with an on-premises Active Directory domain. Affected users saw sign-in failures and a "trust relationship between this workstation and the primary domain failed" message, even with valid credentials, though offline sign-in with cached credentials still worked and AD replication was unaffected.

Microsoft traced the cause to 26H2 enabling enforcement of a feature called Machine Identity Isolation, which is only supported on domains running Windows Server 2025 domain controllers or later. Any device using the feature outside that environment hit the bug. The September 22, 2026 update, KB5124010, resolved it by disabling Machine Identity Isolation enforcement outright while Microsoft reworks the feature. Devices on KB5124010 or later need no workaround; organizations still on an earlier build can apply a Known Issue Rollback policy or manually flip the registry value at HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MachineIdentityIsolation from 2 to 0 and then run Test-ComputerSecureChannel -Repair.

Mitigated: USB Audio Class 1.0 devices failing to start

Microsoft has also acknowledged that some older USB Audio Class 1.0 devices — a specification that predates most of today's audio hardware — fail to start or produce no sound after installing 26H2. Device Manager shows a Code 10 "This device cannot start" error, volume controls can go unresponsive, and Sound settings may stop opening at all. The bug isn't limited to 26H2: Microsoft lists it as affecting everything from Windows 11 23H2 through 26H2 and even Windows 10 and several Windows Server versions, suggesting the regression sits in a shared audio driver component rather than anything unique to this release.

There is no consumer-facing fix yet. Microsoft says it is "working to address this issue in a future Windows update," and in the meantime directs IT administrators who need an immediate workaround to contact Microsoft Support for Business. Home users with affected hardware currently have no documented workaround beyond waiting for a cumulative update.

Mitigated: black screen after sign-in, mostly on virtual desktops

The third issue hits a narrower audience: Microsoft says it has "primarily" seen black-screen or desktop-loading failures after sign-in on Azure Virtual Desktop hosts using FSLogix profile containers, and more often on devices with existing user profiles. Symptoms include a black screen that never loads the desktop automatically, sessions that need to be started manually, and Explorer crashes in the event log.

Two workarounds exist today. Users can manually launch explorer.exe from a new Task Manager task to recover a stuck session. For a permanent fix at scale, IT administrators can deploy a Known Issue Rollback (KIR) Group Policy — Microsoft published separate KIR packages for 26H1 and for 24H2/25H2/26H2 — which disables the underlying change until a permanent fix ships in a future update.

Safeguard holds: a separate reason some PCs haven't gotten 26H2 yet

None of the four tracked issues above are "safeguard holds," but Microsoft's known-issues page explicitly points to that mechanism too. A safeguard hold is a compatibility block Microsoft applies automatically to prevent a specific device configuration from receiving an update until the underlying problem is fixed — it's a separate system from the known-issues list, and it's why some eligible PCs simply won't be offered 26H2 yet even though no error appears. Microsoft documents how to check for an active hold on its safeguard holds support page.

How to check whether your device is affected

If you've already installed 26H2 and want to confirm whether a symptom matches an acknowledged bug rather than something else:

• Open the official known-issues page and use Ctrl+F to search for your symptom — Microsoft updates it as issues are opened, mitigated and resolved.
• Check your installed update via Settings > Windows Update > Update history. If you're on KB5124010 or later, the domain-trust bug is already fixed for you; the AC-3 and USB audio issues can still apply.
• For the AVD black-screen issue specifically, check whether your organization deploys FSLogix profiles — Microsoft says that's where it shows up "primarily."
• If a symptom isn't listed, file it through the Feedback Hub app so Microsoft can triage it as a new issue rather than treating it as already known.

What this means for IT administrators specifically

Three of the four issues disproportionately affect managed, enterprise environments rather than typical home PCs. The domain-trust bug only hit machines with Credential Guard and Machine Identity Isolation configured through Intune, Group Policy, or the registry — settings home users essentially never touch. The black-screen bug is explicitly tied to Azure Virtual Desktop deployments using FSLogix. And the Known Issue Rollback mechanism Microsoft recommends for both the domain-trust and black-screen bugs is itself an IT-administrator tool: it ships as a Group Policy template that has to be downloaded, installed and explicitly configured to "Disabled" before it takes effect, and devices need a restart afterward. Home users affected by the black-screen symptom have a simpler option — manually starting explorer.exe from Task Manager — but that's a session-by-session fix, not a permanent one.

For IT teams planning a 26H2 rollout, the practical checklist is: confirm devices are on KB5124010 or later before enabling Machine Identity Isolation enforcement; hold off deploying 26H2 broadly to FSLogix-based AVD pools until the KIR policy is tested, or deploy the KIR proactively; and audit for any software that depends on AC-3 decoding or legacy USB Audio Class 1.0 hardware before a wider push.

Why a short known-issues list still matters

Compared with some past Windows feature updates, 26H2's four tracked issues are a relatively light list, and one is already resolved. Microsoft has also described 26H2 publicly as a low-disruption release, since it ships through the same servicing technology as 24H2 and 25H2 rather than a full in-place upgrade. Still, two of the remaining three issues — the USB audio regression and the AC-3 decoding bug — have no shipped fix yet, and Microsoft hasn't given a date for either. For households and businesses running affected legacy audio hardware or software, that means living with the symptom or applying a manual workaround for at least a few more weeks.

It's also worth separating "known issue" from "widespread problem." Microsoft's own descriptions repeatedly scope these bugs narrowly — USB Audio Class 1.0 only (an aging spec most modern headsets and speakers don't use), AC-3 decoding specifically (most modern media apps use their own decoders), and AVD/FSLogix specifically for the black screen. None of the four entries describes a general 26H2 stability or performance problem affecting all upgraders. If you haven't installed 26H2 yet and are specifically worried about compatibility, our guide to getting the Windows 11 2026 Update covers eligibility and how the phased rollout reaches different devices.

What's next

Microsoft says fixes for both open issues — the USB Audio Class 1.0 failures and the AC-3 decoding crashes — are planned for "a future Windows update," without a committed date. Based on Microsoft's cadence for 24H2 and 25H2 known issues, a fix is most likely to land in an upcoming Patch Tuesday cumulative update rather than an out-of-band release, unless the impact is judged severe enough to warrant an expedited patch. Pandromeda will update this story as soon as Microsoft's release health page reflects a resolution for either issue.

Frequently asked questions

Is Windows 11 26H2 safe to install right now? Microsoft hasn't placed a broad safeguard hold on 26H2 itself; the four known issues affect specific hardware and configurations (older USB audio devices, AC-3 decoding software, and Azure Virtual Desktop/FSLogix environments) rather than all PCs.

Do I need to do anything about the domain-trust bug? Only if you manage domain-joined PCs with Credential Guard and Machine Identity Isolation enabled outside a Windows Server 2025 domain. Installing KB5124010 or later resolves it automatically.

Is there a fix yet for the USB audio problem? No. Microsoft lists it as "Mitigated" with no permanent fix, and says a future Windows update will address it; home users have no documented workaround beyond trying a different USB port or a USB Audio Class 2.0 device.

What should I do if my app crashes with AC-3 audio errors? Check whether the app has a setting to use its own built-in audio decoder instead of Windows' decoding; Microsoft confirms the bug but hasn't shipped a fix.

Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Felix MoreauAll Software & Guides coverage