The Windows 11 26H2 update resets the support cycle to zero and sets Recall as an option

Following the backlash over the forced introduction of Copilot and the unintentional integration of Recall, Microsoft has released the 26H2 update, where both Copilot and its French counterpart Recall become optional features. However, this update activates existing settings on devices, shifting the burden of management onto administrators.

Recall was introduced on May 20, 2024, as a key feature of Microsoft’s Copilot+ PCs, which are equipped with a local AI chip. This feature captures screen snapshots to help users rediscover content they’ve viewed, but it was integrated without user consent while Copilot became a staple in Windows. The ensuing controversy was widely publicized. In response to the outcry, Microsoft announced on June 7, 2024, that they had heard user concerns and would simplify the activation choices and enhance privacy and security assurances, before directing the updates toward Insider program testers.

The 26H2 update further implements this response. It is installed via an activation package (KB5121794), meaning it serves as a lightweight patch to activate features already included in the system on the same maintenance branch as 24H2 and 25H2. Microsoft specifies that users must first install the cumulative update KB5124010 from September 22, 2026, or any later update.

Copilot and Recall as Optional Additions

In the announcement for 26H2, Microsoft does not mention Recall, Copilot, or Click to Do, the features allowing actions on screen content that had been elaborated upon in 2025. Instead, the update begins by highlighting new AI functionalities, including an agent in Settings and AI utilization metrics in the Task Manager.

As for Recall, Microsoft states that this feature remains off by default. Users must opt-in and authenticate with Windows Hello before using it. Additionally, the sensitive information filter is activated by default. In managed environments, the feature is disabled unless administrators choose to enable it. Thus, while users have the final decision, the option’s availability ultimately lies with administrators—this contrasts with 2024’s setup, where administrators could only disable the function.

Activation Enforces Legacy Identity Settings

Post installation of 26H2, Microsoft reports two open incidents. The first concerns the Machine Identity Isolation feature, which secures a device’s identity by linking it to its machine account within the directory. Windows now applies the configurations that enable this feature, whether they were set manually or dictated by policy. However, Microsoft supports this functionality only with domain controllers operating at Windows Server 2025 functional level or higher. A forthcoming patch aims to temporarily prevent these settings from being enforced, with the incident logged since September 16.

Specifically, devices protected by Credential Guard—a vault that isolates identity secrets—may lose their secure channel with the local Active Directory. Cached credential logins can continue, domain replication remains intact, and no servers are implicated. Microsoft recommends disabling this function using the method that activated it (Intune, Group Policy, or setting the MachineIdentityIsolation registry value from 2 to 0), restarting, and then repairing the channel using the Test-ComputerSecureChannel command.

This situation requires teams to document existing identity configurations on devices and confirm the functional level of their domain controllers. If a device loses its secure channel, it can still operate with cached credentials; however, administrators must restore its directory relationship. In addition to the first incident, a second was reported on September 24, regarding Azure Virtual Desktop sessions with FSLogix profiles, which sometimes display a black screen at login, particularly with existing profiles. Microsoft suggests a Known Issue Rollback via Group Policy or manually launching explorer.exe as a workaround.

Administrator Protection and Sysmon Still Require Activation

On the security front, Microsoft has added various components, most of which are disabled by default. Administrator Protection, which substitutes permanent administrator rights with temporary privileges, is off by default and must be activated via Intune or Group Policy. Sysmon, the system event logging tool now integrated into Windows, also remains disabled. The end of default trust for cross-signed drivers necessitates audits of at least 100 hours and three reboots before any blocking occurs.

Windows has added post-quantum algorithms ML-KEM and ML-DSA to its cryptography APIs, reigniting the focus on post-quantum cryptography for teams. Conversely, Windows settings backup is enabled by default for eligible professional devices. It stores configurations in the cloud and requires a Microsoft Entra ID account, along with a device joined to Entra or hybrid join, failing if policies like EnableActivityFeed, PublishUserActivities, or EnableCDP are turned off.

Three Versions Coexist with a Tight Support Schedule

There is only one monthly cumulative update that will refresh the 24H2, 25H2, and 26H2 versions. The 26H2 version essentially resets the support cycle. Microsoft will release the first security update for 26H2 on October 13, 2026, coinciding with the end of support for the 24H2 Home and Pro editions.

The 24H2 Enterprise will continue support until October 12, 2027, while 25H2 Enterprise will be supported until October 10, 2028. The 26H2 support cycle will last 36 months for Enterprise and Education, roughly until October 2029. Microsoft has not disclosed the end dates for the Home and Pro versions, which are set for 24 months.

For users, 26H2 introduces application-specific actions in the taskbar and improvements to the File Explorer. However, to access the summary in File Explorer, users must have a Microsoft 365 account and a Copilot license. Notably, 26H1 remains exclusive to new devices without an in-place upgrade.

Microsoft Addresses User Concerns While Maintaining Office Presence

The arrival of 26H2 is not happening in a vacuum. It is positioned amidst the climate of distrust stemming from the forced implementation of Copilot and Recall, with Microsoft responding by making features optional while tightening security guarantees. This maneuver appears aimed at discouraging the exodus of users to less restrictive systems. The shift focuses on methodology, favoring opt-in settings and sensitive information filters rather than scaling back ambitions, as AI continues to headline new features.

Despite this methodological retreat, three functions remain active by default: settings backup, taskbar actions, and File Explorer enhancements. These features also provide Microsoft with better visibility into user interactions, aiding in system adjustments. However, the disclosed documents do not specify which data is shared.

Scroll to Top