Microsoft has released KB5064081, an optional preview update for Windows 11 version 24H2, pushing out build 26100.5074 on August 29, 2025. The package bundles an updated servicing stack with cumulative fixes and a raft of new feature code — but don’t expect every device to see the same changes. Server-side rollouts and hardware gating mean the most visible AI additions will trickle out gradually, a deliberate strategy to limit risk while Microsoft collects telemetry before wider deployment.

This is not a production update. It is intended for pilot rings, Release Preview testers, and organizations willing to validate upcoming changes on representative hardware. The code is here, but the experience is not yet uniform.

What’s Actually New in Build 26100.5074

The update touches three broad areas: consumer-facing AI integrations, enterprise housekeeping, and foundational servicing improvements. The cumulative payload includes an updated Servicing Stack Update (SSU) — a critical component that hardens the update pipeline itself. SSUs are permanent once installed, so administrators must treat this package with extra caution and have recovery images ready.

AI and Productivity Integrations

File Explorer gains AI-powered context actions. Right-click on a file and you’ll now see options to blur backgrounds, erase objects, remove backgrounds, and perform a visual search on images. For documents, a Summarize action appears — but it requires a valid Copilot or Microsoft 365 subscription, and the heavy lifting happens in the cloud. On-device processing handles the image edits, while summarization relies on Microsoft’s back-end AI. This split means enterprises must validate data flow policies before enabling the feature.

Recall gets a new homepage. No longer just a snapshot viewer, Recall now offers a personalized landing page with Recent Snapshots, Top Apps and Websites, and a left navigation bar linking to Home, Timeline, Feedback, and Settings. Snapshot collection remains opt-in and filterable, but IT managers should test retention and export controls in managed environments. Export workflows may require an export code in some regions, adding a layer of privacy protection.

Click to Do expands with a first-run tutorial. The feature now guides users through its local on-device actions for text and images: summarize text or remove image backgrounds without leaving the flow. More advanced actions still demand Copilot integration, so licensing continues to be a gate.

UI Polish and Usability Tweaks

Permission dialogs have been redesigned to dim the screen and center consent prompts, reducing accidental acceptance. The taskbar and search experience get minor upgrades: a larger optional clock in the notification center, grid image view for search results, and clearer indexing status indicators. But the most immediately noticeable change for Dark Mode users is the extension of the dark palette to legacy file-operation dialogs — those copy, move, and delete prompts that previously burned white in an otherwise dark UI. Early testers call it a marked improvement in perceived polish.

Enterprise-Focused Changes

Windows Backup for Organizations nears general availability. This Intune and Entra ID-centric tool restores user settings and Microsoft Store app lists on managed devices. It does not back up traditional Win32 applications, so large-scale migrations still require supplemental deployment tools. Tenants must enable the feature and test restores in a lab environment before putting it into production workflows.

PowerShell 2.0 begins its long goodbye. The legacy engine is being removed from Windows images starting with this build wave. Organizations must inventory scripts and automation that explicitly target PS 2.0 and migrate them to PowerShell 5.1 or 7.x. If immediate migration isn’t feasible, isolating legacy workloads in virtual machines or containers is the recommended stopgap.

MDM enrollment gets a subtle reporting shift. During Out-of-Box Experience (OOBE), certain older devices will now report an ApplicationVersion equal to BuildVersion + 1. This indicates the device is restore-capable after the OOBE update path runs. MDM servers that expect specific Update Build Revision (UBR) values must adjust their logic, or enrollment may stall. Testing Autopilot flows on representative hardware is critical.

The SSU Factor and Installation Paths

KB5064081 is not a simple cumulative update. It contains a Servicing Stack Update that modifies how Windows updates itself. Because SSUs cannot be removed separately, rollback options are limited. Microsoft recommends downloading the MSU files from the Microsoft Update Catalog and applying them carefully.

Two methods are documented. You can place all MSU files in a single folder and use DISM to install them together, with DISM automatically ordering the prerequisites. Or you can install each MSU file individually in a specific sequence: windows11.0-kb5043080-x64.msu first, then windows11.0-kb5064081-x64.msu. For offline images, the same DISM commands apply. The update can also be applied via Windows Update Standalone Installer, but for IT pros, command-line deployment with DISM remains the most controllable path.

Note: If you’re updating Windows installation media with Dynamic Update, ensure all companion packages (SafeOS Dynamic Update, Setup Dynamic Update) come from the same month’s release. If not available, use the most recent version of each.

Staged Rollouts Create Testing Headaches

The most significant operational challenge is variability. Two machines on build 26100.5074 may show different feature sets because Microsoft activates new capabilities via server-side flags, not local build content alone. This complicates functional testing, UI automation, and accessibility validation. A feature that works on one test device may be absent on another, leading to false confidence or unnecessary troubleshooting.

Accessibility regressions are already surfacing. While many legacy dialogs now respect dark mode, inconsistent focus indicators and leftover light-themed microcomponents have popped up in early hands-on reports. These are real accessibility risks. Organizations that depend on screen readers, high-contrast modes, or keyboard navigation should test thoroughly and file Feedback Hub reports for any regression.

Automation tooling may also break. The theming changes and shift in control metrics can confuse UI automation scripts and RPA workflows. Test suites need to cover both themed and unthemed scenarios, and selector strategies may require updates.

A Pragmatic Pilot Checklist

For IT teams preparing to evaluate KB5064081, a structured approach reduces risk:

  • Inventory and risk assessment: Audit all PowerShell dependencies immediately. Identify any scripts that call PS 2.0 and schedule migrations. If you rely on legacy automation, isolate it in VMs or defer the update on those machines until migration is complete.
  • Pilot and test rings: Deploy to a small, diverse group — include Copilot+ and non-Copilot+ hardware to surface hardware-gated feature disparities. Verify OOBE and Autopilot flows closely, watching for the ApplicationVersion +1 pattern in MDM enrollment logs.
  • Backup and recovery readiness: SSUs are permanent. Before deploying, ensure recent system images and WinRE recovery media are available and tested. If something goes wrong, a full restore may be the only safe path.
  • Privacy and compliance validation: Test Recall snapshot exports and retention behavior in a lab tenant. Confirm whether any AI action routes data to Microsoft’s cloud and ensure that aligns with your data governance and contractual obligations.
  • Automation and accessibility validation: Run UI automation, keyboard navigation, and screen reader tests on updated machines. Compare results with pre-update baselines.
  • Communication and training: Notify helpdesk staff about visible changes — darkened file dialogs, new right-click actions, potential Copilot subscription prompts. Equip them to handle user confusion over missing features due to staged rollouts.
  • Monitor telemetry and feedback: Use Feedback Hub, Insider forums, and your own telemetry to watch for regressions. Hold off mass deployment until test metrics meet organizational thresholds.

Real Benefits, Real Risks

For end users, the most tangible win is the dark mode consistency. No more blinding file operations dialogs in an otherwise dark-themed workspace. The AI integrations — when they work on-device — genuinely speed up common tasks, but the constant licensing and hardware gates may frustrate users who don’t see the promised features.

For IT, Windows Backup for Organizations offers a first-party restore path that simplifies device refreshes in Intune-managed environments, limited as it is. PowerShell 2.0 removal reduces the platform’s legacy attack surface, a long-overdue security improvement. And the SSU hardening should make future updates more reliable.

The risks are equally real. Staged enablement means you cannot assume feature parity across your fleet. Accessibility regressions can impact vulnerable users. Cloud-backed AI features introduce new data flow questions that compliance teams must answer. And the permanence of the SSU makes rollback complex — a failed deployment might force a full system recovery.

Looking Ahead

KB5064081 is a snapshot of Microsoft’s current development philosophy: ship the code early, activate features slowly, and use telemetry to decide which ones to broaden. The AI features here are clearly still maturing, but their presence in the shell signals where Windows is headed. For organizations, the update is a reminder to accelerate legacy script migration, refine MDM enrollment logic, and treat every preview build as a validation milestone rather than a production candidate.

Pilot widely, validate relentlessly, and prepare your recovery plans. The AI era in Windows is arriving, but it’s arriving in stages. This is one of them.