Microsoft’s optional KB5064081 preview update for Windows 11 24H2 drops a long-overdue fix that finally makes Task Manager’s CPU readings match reality, while simultaneously rolling out AI-powered productivity tools like a redesigned Recall homepage and right-click File Explorer intelligence. The update, which pushes systems to build 26100.5074, is part of the monthly non-security “C” release cycle—an opportunity for enthusiasts and IT pros to test fresh features and reliability improvements before they become mandatory in the next Patch Tuesday rollout.

Unlike the standard cumulative updates that dominate Microsoft’s monthly cadence, KB5064081 bundles a Servicing Stack Update (SSU) alongside the payload. That packaging increases installation robustness but also makes rollbacks more complex, as the SSU is persistent once applied. The company is also employing a gradual rollout model for many user-facing features, meaning not every device will see all the new toys on day one. Hardware, licensing entitlements, and server-side gating all play a role in what gets enabled—a detail that will matter to anyone trying to plan a deployment.

The CPU Fix Power Users Have Waited For

For years, Windows 11’s Task Manager Processes tab used a legacy “Processor Utility” metric that could show a single-threaded process pegging a multi-core chip at 100%, while the Performance and Users tabs told a completely different story. The discrepancy confounded troubleshooting and made the tool borderline useless for quickly sizing up system load on modern processors. KB5064081 standardizes the CPU calculation across all Task Manager panes, adopting the industry-conventional formula:

CPU % = (Δ Process CPU Time) ÷ (Δ Elapsed Time × Logical Processors)

With this change, per-process totals become additive and directly comparable to the overall system utilization shown in the Performance tab, as well as to WMI counters and third-party monitoring tools. A 25% reading for a single application in the Processes list now means it’s chewing up 25% of total logical processor capacity, not an ambiguous fraction of a single thread. For sysadmins who have scripted Task Manager data parsing, this also eliminates a major source of inconsistency.

If you’re nostalgic for the old numbers, Microsoft retains the legacy metric as an optional “CPU Utility” column in the Details tab. But for most users—especially those managing high-core-count workstations or virtual machines—the new reporting is a straightforward quality-of-life improvement that should have shipped years ago.

AI Features Creep Into the Shell

KB5064081 expands Microsoft’s generative AI ambitions by embedding small-scale intelligence directly into Windows’ core surfaces. Three additions stand out:

  • Recall homepage: The much-debated snapshotting feature gets a personalized landing page that surfaces recent snapshots, top apps, and frequently visited websites for fast task resumption. Snapshot collection is strictly opt-in, filterable by app or content, and encrypted locally behind Windows Hello. Enterprise admins will still want to run a privacy impact assessment before enabling it broadly, but the controls are there.
  • Click to Do tutorial: An interactive first-run walkthrough demonstrates contextual actions for text and images, making the feature more discoverable. You can summarize a paragraph, remove an image background, or erase objects with a right-click—if your hardware and licensing stack aligns.
  • File Explorer AI actions: Right-click menus gain an “AI actions” flyout with image editing tools (Blur Background, Remove Background, Erase Objects) and a “Summarize” command for documents. The summarization engine calls Copilot cloud backends, which means it requires a Microsoft 365 or Copilot license; unlicensed accounts will see degraded or redirected functionality. On-device actions, like background removal, lean on Neural Processing Units (NPUs) found in Copilot+ certified PCs, so older machines won’t see the same menu entries.

These features are gated not only by hardware—Copilot+ chips with integrated NPUs are mandatory for many on-device experiences—but also by Microsoft’s server-side feature flags. The split between local and cloud processing, and the licensing checkpoints, means feature availability can vary wildly even between two machines running the same build. It’s a model that gives Microsoft room to iterate, but it complicates support and user expectations.

Quality-of-Life Tweaks Across the UI

Beyond the headliners, the preview shifts multiple smaller levers that cumulatively smooth out daily interactions:

  • Windows Hello redesign: A cleaner sign-in interface makes passkey and device selection more intuitive, reducing friction during authentication.
  • Taskbar and notification updates: The notification center now optionally shows a clock with seconds, and taskbar search gains an image grid view plus clearer indexing status messages.
  • Lock screen personalization: Widget options expand, letting users tailor the glanceable info that appears before sign-in.
  • Settings and privacy controls: A new “Text and Image Generation” page under Privacy & security lists third-party apps that recently used Windows’ generative models, with per-app toggles to keep them in check.
  • Explorer polish: Context menus get dividers, and the Activity column in file listings displays people icons for quicker collaborator identification.

The collection of UI refinements isn’t revolutionary, but it does signal that Microsoft is still willing to sand down rough edges even as it pushes into territory like AI-infused shell extensions.

Enterprise Signals: Backup, PowerShell 2.0, and More

KB5064081 carries several payloads that matter more to IT departments than to casual users:

  • Windows Backup for Organizations: The service is moving toward general availability. It backs up curated Windows settings and Store app lists for Entra-joined devices, integrating with Intune for restore during Autopilot or OOBE flows. It is not a full-image or file backup—admins need to confirm that their provisioning workflows can depend on it before turning off existing backup tools.
  • PowerShell 2.0 removal begins: The legacy engine is being excised from 24H2. Scripts, installers, or automation chains that still call the 2.0 runtime must be migrated to PowerShell 5.1 or 7.x. A failure to inventory these dependencies before deploying the update could break custom tooling.
  • Settings home changes: A Device Card appears for Microsoft account users in the U.S., and an Advanced page consolidates developer and system toggles. While minor, these changes underscore that Settings remains a moving target for enterprise group policies.

Known Issues to Watch

No preview ships perfectly clean, and KB5064081 inherits some baggage from the wider August update cycle:

  • CertEnroll event log noise: Systems may log repeated CertificateServicesClient errors (Event ID 57) claiming the “Microsoft Pluton Cryptographic Provider” failed to initialize. Microsoft says there is no functional impact and is gradually rolling out a fix to stop the logging, but admins may still see the entries on unfixed machines.
  • NDI streaming regressions: Related security updates (like KB5063878) introduced severe stuttering and dropped frames for users relying on NDI (Network Device Interface) streaming—a critical protocol for live production setups using OBS, vMix, or similar tools. The official workaround is to switch NDI Receive Mode from RUDP to TCP or UDP until a platform fix lands. Any workstation involved in broadcast workflows should be tested specifically for this before the update is approved.
  • Other minor issues: The release notes flag transient problems with audio services, certain Explorer crashes, and IME edge cases. Most were addressed in this same update, but pilot testing on a representative hardware set is still wise.

The gradual rollout model itself is an operational consideration: the absence of a feature on a test device doesn’t mean the update failed; it may simply not have been gate-enabled yet. Rely on Microsoft’s Insider Release Preview notes and your tenant’s feature flags for deterministic planning.

How to Install and Pilot

Because KB5064081 is an optional preview, it won’t install automatically unless you have the “Get the latest updates as soon as they’re available” toggle flipped in Windows Update settings. Otherwise, head to Settings > Windows Update > Check for updates, and when the preview appears, click “Download and install.”

For IT teams, the recommended approach is a structured pilot:

  1. Inventory hardware and licensing: Identify Copilot+ machines (if you intend to test on-device AI), confirm TPM/Windows Hello readiness, and map Microsoft 365/Copilot entitlements across tenants.
  2. Build a representative test ring: Include a mix of consumer laptops, managed corporate units, high-core workstations, and any devices involved in NDI streaming.
  3. Validate core scenarios: Confirm that Task Manager CPU readings align with PerfMon/WMI; test Recall opt-in, snapshot viewing, and export behavior; exercise File Explorer AI actions for both licensed and unlicensed accounts; stress-test NDI pipelines.
  4. Secure privacy sign-off: Get compliance and legal teams to review snapshotting controls and generative AI usage telemetry.
  5. Roll out in stages: Move from pilot to a broader group, monitoring upgrade success rates, Explorer stability, and any unexpected restart errors. Because an SSU is baked in, prepare image snapshots and offline deployment media to enable robust rollback if needed.

Analysis: Progress at a Price

The KB5064081 update is a microcosm of where Windows 11 sits in late 2025: steadily improving in ways that matter to real users (accurate CPU metrics, smoother authentication, smarter shell actions) while layering on features that depend on cloud services, hardware accelerators, and subscription licenses. The Task Manager fix alone will win over sysadmins who have been complaining about the metric mismatch for years. The AI additions, though gated, show that Microsoft is serious about making generative assistance a first-class part of the OS rather than a sidebar applet.

But the story isn’t all positive. The staged rollout model, combined with hardware and licensing fences, creates a fragmented experience that can frustrate early adopters and complicate enterprise planning. Bundling the SSU adds friction to rollbacks. And the known streaming regression tied to other August updates is a real hazard for content creation pipelines—one that deserves more prominent communication from Microsoft.

For now, KB5064081 is exactly what a preview should be: a chance to test tomorrow’s Windows, warts and all, before the changes become compulsory. Power users will appreciate a Task Manager that finally tells the truth; IT shops will need to do their homework; and everyone should keep an eye on that NDI workaround if live video is part of their workflow.