Microsoft closed out August 2025 with two Windows 11 updates that pack more AI into everyday tasks and quietly start pulling a decades-old scripting engine. The Patch Tuesday release KB5063878 (build 26100.4946) and the optional preview KB5064081 (build 26100.5074) together introduce a revamped Recall app, AI actions in File Explorer, and the long-anticipated removal of Windows PowerShell 2.0 from the 24H2 image. While the security fixes are routine, the feature payload signals Microsoft’s determination to weave Copilot into the OS fabric—and to purge legacy components that keep IT shops awake at night.

What Shipped: A Two-Part August

August followed Microsoft’s now-standard dual-release cadence. On August 12, KB5063878 landed as the mandatory security update, bundling fixes with a servicing stack update (SSU) and quality improvements. Two weeks later, on August 29, the optional non-security preview KB5064081 arrived, offering a broader set of staged features meant for validation before the September Patch Tuesday.

Both updates target Windows 11 version 24H2. The SSU+LCU combo has become the norm, merging the servicing stack directly into the cumulative package. While this cuts down installation failures, it changes the rollback calculus: SSUs are applied in place, making a return to a previous state more rigid. IT teams must adjust their imaging and recovery plans accordingly.

Insider channels also saw heavy activity—Dev builds in the 26200 series, Beta in 26120, and Release Preview snapshots. These flights test interface tweaks, deeper Copilot hooks, and the cross-device resume features that are now trickling into stable builds.

AI Muscles Its Way into File Explorer and Beyond

The most visible changes are the AI-powered productivity tools. Recall, reborn as a “personalized resumption hub,” now surfaces recent snapshots, frequently used apps, and websites. All data stays local, encrypted, and locked behind Windows Hello. Microsoft has positioned it as a privacy-first memory aid, but admin controls are essential for organizations handling sensitive information.

Click to Do gets a first-run tutorial and tighter integration. Users can now summon AI actions—summarizing text or removing image backgrounds—without leaving the current app. Some operations run on-device, while others require cloud backing and a Copilot subscription. The feature is designed to minimize context switching, but licensing gating means not everyone will see the same options.

File Explorer’s AI integration is where the rubber meets the road. Select an image or document, and you can trigger visual search, object removal, background blur, or document summarization—all within the Explorer ribbon. These capabilities lean heavily on Copilot for Microsoft 365 entitlements and Copilot+ hardware, so a visible button may prompt for a license upgrade. For licensed users, the promise is a jump from a file manager to an AI-powered workspace.

Copilot’s home screen gets a redesign emphasizing recent files and summarization, while semantic file search expands to understand natural language queries. Some early reports link these changes to experimental “Smart mode” model routing, but Microsoft hasn’t publicly detailed the architecture. Treat such claims with cautious interest.

Cross-Device Resume Ties Your Phone to Your PC

A new taskbar “Resume alert” appears when an activity on a linked Android phone can continue on the PC. Spotify is the first partner app, but Microsoft’s Resume APIs open the door for broader adoption. The feature requires Link to Windows and a consistent Microsoft account. For now, it’s a niche convenience, but it hints at a future where mobile and desktop workflows blend seamlessly.

Dark Mode Finally Gets Comprehensive

File Explorer’s dark theme, long a patchwork of light elements, makes substantial progress. Copy/move dialogs, confirmation prompts, and warning windows now respect the dark palette in Insider builds. Not every child dialog has been converted, but the improvement is palpable for those who live in dark mode.

Taskbar and Accessibility Tweaks

Search now displays image results in a grid and warns when indexing is incomplete. Windows Hello receives a visual refresh for biometric sign-in, purchase authentication, and passkey management, aiming to smooth the passwordless transition. Task Manager standardizes CPU workload metrics across all views, with a legacy CPU Utility column available for traditionalists. These may be small touches, but they reduce daily friction and support calls.

The Enterprise Housecleaning: PowerShell 2.0 Is Out

The biggest backend change is the removal of Windows PowerShell 2.0 from the 24H2 image. Deprecated years ago, the aging engine will no longer be preinstalled starting with August’s cumulative updates. Any scripts or third-party tools that explicitly invoke PowerShell 2.0 hosts will break. Microsoft recommends migrating to PowerShell 5.1 or the standalone PowerShell 7.x.

IT teams must inventory scheduled tasks, logon scripts, and automation that depend on the old engine. The update doesn’t rip out PowerShell 2.0 from existing installations immediately—it’s phased—but fresh deployments and future updates will exclude it. This is a security win, reducing attack surface and forcing modernization, but it demands immediate attention.

Practical migration steps:
- Inventory all on-device scripts and scheduled tasks calling PowerShell 2.0 hosts.
- Test scripts under PowerShell 5.1 or 7.x, addressing deprecated cmdlets and behavior changes.
- Engage vendors to confirm compatibility or provide updated tools.
- Stage the change in pilot rings and include rollback plans for critical automation.

Windows Backup for Organizations Goes GA

Windows Backup for Organizations graduated to general availability, offering a streamlined path for device transition during refresh cycles. It backs up settings, apps, and files, then restores them on a new machine. While handy, it’s not a replacement for full-fledged backup solutions; evaluate it against existing MDM and backup strategies before adopting wholesale.

Secure Boot Certificate Expiry Looms

Microsoft’s August guidance repeated a dire warning: Secure Boot certificates on many devices start expiring in mid-2026. Without firmware updates, boot validation can fail, bricking systems. This is not a Windows Update fix—it requires OEM firmware patches. Coordinate with hardware vendors, image teams, and security ops now. Treat June 2026 as a hard deadline for remediation.

Quick Machine Recovery and the ‘Black Screen’

A new automated recovery tool, Quick Machine Recovery, ships in the August updates. It diagnoses and repairs boot failures and post-update crashes without a full reinstall. Paired with it is a cosmetic shift: the error screen reportedly moves from blue to black, with faster detection. While not bulletproof, it should cut down technician visits for common boot hiccups.

Governance Headaches: Feature Gating and Fragmentation

Microsoft’s staged rollout model means two identical Windows 11 PCs may show wildly different feature sets. AI capabilities depend on Copilot+ hardware, Microsoft 365 licensing, and server-side enablement. Buttons in File Explorer or Recall panels may appear grayed out or prompt for subscriptions, creating confusion. Help desks need playbooks to handle “ghost UI” questions.

Recall snapshots, while opt-in and local, capture screen content that may include sensitive data. Organizations must weigh productivity gains against privacy risks and regulatory exposure. Admin controls to filter capture and list apps that call generative models are emerging, but they’re not yet mature.

Risks and Trade-offs

August’s updates bring real improvements but also new complexities. The PowerShell 2.0 removal is a long-term security plus but may break legacy automation. Secure Boot certificate expiry is an external dependency that could cause widespread boot failures if neglected. AI fragmentation across licenses and hardware will irritate users and complicate support. Recovery tools are improved but no substitute for tested backup and restore processes.

What IT Teams Should Do Now

  • Pilot the optional preview: Deploy KB5064081 to a test ring and validate AI features, especially Recall and File Explorer actions.
  • Audit PowerShell 2.0 usage: Identify scripts and scheduled tasks referencing the old engine. Migrate to PowerShell 5.1 or 7.x.
  • Test Windows Backup for Organizations: Don’t replace existing backups without a full evaluation.
  • Contact OEMs for Secure Boot firmware updates: Start the dialogue now; don’t wait until 2026.
  • Revise imaging and rollback procedures: Acknowledge the SSU+LCU permanence and update standard operating procedures.
  • Communicate with end users: Prepare guidance on staged rollouts, Recall privacy settings, and licensing requirements.

For Enthusiasts and Power Users

Insider builds offer a sneak peek at rapid experimentation, but features may vanish. Don’t be alarmed if AI buttons demand a Microsoft 365 subscription—that’s by design. Use the August optional preview on a spare machine; snapshots and recovery features can touch system-level data, so back up first.

Why August Matters

Microsoft didn’t reinvent Windows in August 2025, but it accelerated a deliberate pivot. By baking AI into the shell, it’s transforming Copilot from a chatbot into a system-level fabric. The removal of PowerShell 2.0 and the Secure Boot warnings show a company tackling technical debt while improving resilience. The path is gradual, fragmentation is real, and licensing dependencies are messy—but the direction is clear. For IT decision-makers, the immediate job is disciplined testing and communication to harness the gains without tripping over the gating and legacy pitfalls.