BlackTree Security · Infrastructure · Automation · AI

A Windows Security Update Can Break Domain Trust Even When the Password Is Right

Update, 31 October 2026: Microsoft now marks the September domain-trust issue resolved by the 22 September updates and later cumulative releases. The repair temporarily prevents Machine Identity Isolation enforcement. Administrators should update first and reserve the workaround below for older affected builds.

A user enters correct domain credentials after a Windows security update, yet the PC reports a broken trust relationship with its domain. A helpdesk might suspect the password, the account or a domain controller. Check the device’s update history first. Microsoft now records the confirmed September problem as fixed from the Windows updates issued on 22 September 2026.

Microsoft’s current notice covers Windows 11 versions 24H2, 25H2 and 26H2. Its 26H1 notice covers that version separately. For 24H2, 25H2 and 26H2, the resolving update is KB5124010. For 26H1, it is KB5124006. These updates, and later cumulative releases, remove the need for this issue’s workaround.

The resolution temporarily switches off enforcement of Machine Identity Isolation, or MII, while Microsoft improves the feature. That means current devices should receive the latest applicable cumulative update before administrators disable policy or repair the trust channel. Devices still running an older affected build may need the documented recovery steps if the trust relationship has already failed.

There is now an edition boundary too. Windows 11 24H2 Home and Pro reached end of updates on 13 October 2026 and need a supported feature release, not an indefinite stay on a September repair. Its Enterprise and Education editions remain supported until 12 October 2027.

A dormant security setting became an active dependency

The September security updates caused Windows to honour an existing MII setting. They did not switch on enforcement by themselves. This is why two PCs on the same update could have different outcomes. A patch inventory alone cannot establish which policy was applied, when it reached the device or whether it was later replaced.

Microsoft’s feature guide explains that MII relocates a computer’s domain secret into Credential Guard’s isolated environment. That limits exposure of the secret to code running in the normal Windows environment. It is a meaningful protection for machine identities, not a cosmetic policy switch. The feature guide also retains an older April warning about machine-password rotation. That separate notice must not override the current September-incident resolution.

The issue depended on the domain as well as the Windows build. Microsoft limits MII to domains at the Windows Server 2025 functional level or newer. On affected pre-resolution builds, an existing enforcement setting in an unsupported domain could cause the client to lose its trust channel. Cached sign-in might still work, while AD replication and services on domain controllers remained unaffected.

Confirm the failure before changing authentication policy

Start with the affected device, its Windows version and update history, the time of its first failed sign-in, and how MII policy reached it. Confirm whether the device has the resolving update or a later cumulative release. Check the domain functional level and which domain controller the client is reaching. Record the current policy and registry state before changing either. These checks distinguish the vendor-confirmed condition from ordinary causes of a broken trust relationship, such as a separate machine account problem.

On a domain member that an administrator can access, Test-ComputerSecureChannel -Verbose checks the trust channel and returns true or false. Microsoft warns that this cmdlet gives misleading errors on domain controllers, so use it on the affected workstation. Preserve relevant Windows System and authentication logs, the policy assignment, update history and the result of that initial test before resetting the channel. This evidence can show whether recurrence followed policy reapplication, a reboot or a different change.

The symptom is separate from BlackTree’s September Remote Desktop service failure and the Citrix and FSLogix black-screen condition. Those separate incident histories concern session transport or desktop loading. Their linked reports include dated mitigation states; use current vendor guidance rather than transferring an old status to this trust failure. A repaired Remote Desktop connection cannot establish that a workstation’s AD trust is healthy.

Update first, then recover older affected builds

Install the latest applicable Windows update. Devices with the resolving update or a later cumulative release do not need this issue’s workaround. The resolving update blocks MII enforcement for every configuration while Microsoft improves the feature.

For an affected device that must remain on an earlier build, Microsoft’s recovery order is to turn off MII through the same route that enabled it, restart, then repair the trust channel. A Known Issue Rollback is another documented option for managed devices. If direct registry configuration was used, back up the registry and establish its restore procedure before making changes. Follow the current version-specific Microsoft instructions rather than applying an old registry example across the fleet; the current manual example names a Windows 11 26H2 device. If the setting came from Intune or Group Policy, change the controlling assignment there. A local change that the next policy refresh reverses is an unstable recovery.

The PowerShell reference documents Test-ComputerSecureChannel -Repair -Credential (Get-Credential) for a broken member-computer channel. Repair requires local administrator rights and suitable domain credentials. Before restarting, establish a local administrative route, confirm the device can reach a domain controller, and make sure the recovery credentials are available to the operator. Cached sign-in alone does not give the organisation a working route to restore online trust.

There is a recovery caveat. Microsoft’s feature documentation says a device previously configured for enforcement has to leave and rejoin the domain when the feature is disabled. Microsoft’s issue notice nevertheless places trust-channel repair after disabling the setting and restarting. Follow the issue-specific sequence first. If repair fails, escalate through the organisation’s device recovery procedure and Microsoft support before a domain rejoin. Preserve management and recovery details before any rejoin, then test the approach on one affected system before repeating it across a fleet.

Disabling MII removes its extra protection for the computer’s domain secret. On current builds, the Windows resolution already prevents enforcement while Microsoft improves the feature. Keep any manual exception limited to affected older builds, give it an owner and review date, and avoid a broad Credential Guard shutdown or removal of a cumulative security update. If a business-critical device still cannot operate, route any exceptional rollback through incident change control and record the security protections it would remove.

Prove recovery after the next reboot

For each repaired device, run the secure-channel test again, complete an online domain sign-in and confirm access to a domain resource that depends on the machine’s trust. Reboot once more in a controlled window, then repeat those checks. Verify that Intune or Group Policy reports the intended setting and that the client is receiving current security updates. Keep a record of temporary exceptions so they can be retired deliberately.

The immediate rollout action is now straightforward: bring Windows 11 devices to a supported release and its current applicable update, then investigate any remaining trust failure as a device-specific incident. Keep the older workaround available only for systems that cannot yet take the resolving update.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *