Windows 11 Beta 26120.5751: AI features refine 24H2 with controlled rollouts

Today’s Beta-channel drop from the Windows Insider Program lands as a small but significant checkpoint in the Windows 11, version 24H2 servicing stream: Microsoft published Windows 11 Insider Preview Build 26120.5751 (packaged as KB5064071) to Beta Channel Insiders on Windows 11, version 24H2 — a routine cumulative flight intended to continue polishing the 24H2 code line while moving selected AI and quality features closer to mainstream release. (blogs.windows.com)

Background / Overview​

Microsoft’s preview release cadence in 2025 keeps the Beta Channel focused on stability and polish for features that are nearer to broad availability, while the Dev and Canary channels carry earlier, more experimental work. The 24H2 track uses an enablement/enablement-package-style servicing model (26120.xxxx builds) for staged feature delivery; Beta updates are typically incremental cumulative packages layered on that codebase. This build (26120.5751) is part of that same enablement-series pattern and appears as a checkpoint intended to deliver targeted fixes and small, controlled rollouts of features for testers.
This release should be read as polish-first rather than as a major feature milestone. The Beta Channel’s role is to stabilize and validate what will ship more widely, and Microsoft continues using a “Controlled Feature Rollout” approach to gate new capabilities to subsets of Insiders before enabling them for everyone. Expect some items to be turned on in waves or to remain gated entirely while others receive broader availability.

---

What Microsoft shipped (and what was announced)​

Microsoft’s official insider announcements in August have clustered several related 26120-series updates; the Aug. 8 Beta flight (Build 26120.5742, KB5064075) and the Aug. 14 Release Preview checkpoint for the 26100 code line set the context for this Aug. 15 Beta update. Those posts confirm the 24H2 servicing model, the two-bucket rollout practice (gradual vs. normal rollout), and a continued emphasis on AI features—Recall, Click to Do, Copilot+ experiences—while also listing stability and accessibility fixes. (blogs.windows.com) (blogs.windows.com)
Key items that are being validated across Beta and Release Preview flights this month include:

• Continued refinement of Copilot+ PC experiences and an on-device “agent” inside Settings (rolling out first to Copilot+ hardware).
• AI-driven interactions surfaced in File Explorer (image edits, Summarize), Click to Do onboarding improvements, and Recall UI updates — most of these features are gradual rollouts and require Copilot+ hardware or Microsoft 365/Copilot licensing for full functionality.
• A set of reliability and UI fixes across Taskbar, Start, File Explorer, and accessibility surfaces.

Note: The official announcement text we received for Build 26120.5751 described the release to the Beta Channel but contained truncated changelog text (“Changes in Beta Channel b…”). At the time of independent checking, the specific KB entry (KB5064071) and a granular online changelog for 26120.5751 were not clearly indexed across the typical third‑party trackers or Microsoft update catalog searches — treat any granular claim about this KB as provisional until Microsoft’s Flight Hub or update catalog lists the entry directly. This should be considered an area of incomplete independent verification.

---

What to expect: features, fixes, and rollout behavior​

Gradual vs. normal rollout: what that means for your PC​

Microsoft separates Beta-channel changes into two buckets:

• Gradual rollout: new user-facing features or AI experiences that are gated and will appear over days or weeks to a subset of Insiders who have enabled the “get the latest updates” toggle. These changes are monitored and adjusted based on feedback.
• Normal rollout (for everyone): stability fixes and quality improvements that are broadly applied to all Beta devices that install the update.

The consequence: if you install Build 26120.5751 and don’t immediately see new AI features or UI experiments, that’s expected — the feature may still be gated. Conversely, fixes for crashes, UI glitches, or accessibility problems will more often land broadly.

AI features in preview (Copilot+, Recall, Click to Do)​

The 24H2 development stream continues to push AI features that depend on both hardware (Copilot+ certified NPU-equipped devices) and cloud/service entitlements (Microsoft 365 Copilot licensing for deep integrations). Expect:

• File Explorer right‑click AI actions (Blur Background, Erase Objects, Remove Background, Visual Search, Summarize) — Summarize ties to Microsoft 365/Copilot licensing.
• Click to Do onboarding improvements and first-run tutorial for Copilot+ hardware; some actions may be slower on first-run or when on new AMD/Intel Copilot+ models.
• An on-device Settings agent that understands natural-language queries and can suggest or perform changes — rolling out to Copilot+ AMD/Intel devices initially.

These capabilities are being measured for privacy, performance, and enterprise manageability as they are validated in Beta/Release Preview. Admin controls and policies are continuing to expand but are not yet locked down to enterprise-grade defaults in all cases.

Quality and reliability fixes you’ll likely see​

Beta builds in this series repeatedly emphasize fixes in these areas:

• Taskbar and Start reliability (thumbnail previews, accidental-click fixes).
• File Explorer stability and performance (context-menu speed, tab duplication flashes, icon mirroring in RTL languages).
• Notification and Notification Center enhancements (calendar + seconds displayed on secondary monitors, finer controls to suppress notification suggestions).

---

Known issues and troubleshooting (what Insiders should watch for)​

Microsoft continues to publish known issues alongside each Beta flight. Across the 26120-series builds you should be aware of the recurring problem types and the documented workarounds:

• Update rollback with error 0x80070005: A subset of Insiders have experienced a rollback when installing certain 26120-series updates. Microsoft’s guidance is to use Settings > System > Recovery > “Fix issues using Windows Update” as an initial step. If you are a production user or depend on a specific device, delay installing Beta-channel cumulative updates until you’ve validated lab scenarios. (blogs.windows.com)
• Click to Do instability and long first-run waits on Copilot+ hardware: Text and image actions in Click to Do have crashed or been slow to initialize for some AMD/Intel Copilot+ systems after model or build updates; Microsoft has indicated the issue will be fixed in subsequent flights. If you rely on Click to Do, expect a delay between build install and smooth operation.
• Xbox controller Bluetooth bugchecks: Some Insiders reported bugchecks when using Xbox controllers via Bluetooth. The interim workaround is to uninstall the offending oemXXX.inf (XboxGameControllerDriver.inf) driver via Device Manager until Microsoft ships a fix. (blogs.windows.com)
• Live captions may crash during live translation on some Copilot+ PCs. The live-translation path is still in preview; Insiders relying on live captions for accessibility should test thoroughly before relying on this functionality in critical scenarios. (blogs.windows.com)

If you run into any of these or similar problems, file actionable feedback via Feedback Hub with repro steps — Insider engineering teams triage that telemetry and feedback heavily when a flight is active.

---

Enterprise implications and management considerations​

Build 26120.xxxx-series Beta flights are a signal for IT that features are approaching wider distribution, but that stability testing and policy planning remain essential. The Release Preview and Beta announcements over the last week included a few enterprise-facing signals:

• PowerShell 2.0 deprecation: Microsoft has signaled that Windows PowerShell 2.0 will no longer be included in the OS image beginning with 24H2 (August 2025). Organizations using legacy scripts or systems dependent on PowerShell 2.0 must migrate or bundle compatibility components before broad deployment. Validate scripts and CI/CD pipelines. (blogs.windows.com)
• Windows Backup for Organizations: Windows Backup for Organizations moved toward GA in the Release Preview stream; this has clear value for device lifecycle operations but requires planning for storage, compliance, and restore verification. (blogs.windows.com)
• Controlled Feature Rollouts and policy coverage: Some Copilot and AI features ship behind toggles and may be controlled at the tenant or device management level only in later flights. IT teams should:
• Draft and run targeted Canary/Beta test plans on non-production Copilot+ hardware.
• Validate Group Policy / MDM controls to disable or limit AI features if required by data governance.
• Train helpdesk staff on scenarios such as Windows Hello PIN loss when switching Insider channels and on the common update rollback troubleshooting steps.
• Update delivery and rollback planning: The improved Servicing Stack and “Rollback First” strategies being trialed aim to reduce failed installs and simplify reversion, but IT should still plan for image-based rollbacks and point-in-time recovery when testing Beta flights. Create a documented rollback and recovery runbook for tester devices.

---

Practical recommendations: what Insiders and IT admins should do now​

• If you are a casual Insider on a daily-driver device, treat Beta builds as semi-stable but not final. Back up user data before installing and consider using a secondary test PC for these flights.
• For IT pros planning pilots:
• Create a dedicated pilot ring of Copilot+ and non‑Copilot hardware.
• Validate critical line-of-business apps and device attestation flows.
• Confirm group policy/MDM controls for Recall, Click to Do, and Copilot agent features.
• If you experience 0x80070005 during install:
• Try Settings > System > Recovery > “Fix issues using Windows Update.”
• If unresolved, capture setup logs (setupact.log, setuperr.log) and Feedback Hub traces before rolling back.
• For Copilot+ features:
• Confirm device hardware (NPU / Copilot+ certification) and the needed Microsoft 365/Copilot licenses for functionality such as Summarize in File Explorer.
• Expect initial indexing and runtime model downloads; allow time for first-run tasks to complete.
• Monitor Flight Hub and Microsoft update channels for the official KB detail and for the update catalog entry of KB5064071; if you manage many devices, avoid broad deployment until the update is documented in the catalog and validated in a pilot ring. (At the time of writing, KB5064071 is referenced in the Insider announcement, but independent catalog indexing for that KB was not fully confirmed.)

---

Privacy, data, and security — the Copilot+ dimension​

As Microsoft deepens on-device and cloud-assisted AI experiences, the privacy and security posture becomes central to adoption decisions. The engineering teams have started to expose more granular privacy controls for AI features and Copilot integration, but two practical checks remain important:

• Data residency and telemetry: AI features like Recall and Click to Do may require cloud services or local model components. Verify whether snapshots, summaries, or model prompts transmit to Microsoft services or whether they remain on-device; use tenant-level controls where available. This is especially material for regulated workloads.
• Credential and Windows Hello behaviors: Several Insider reports and Microsoft notes have flagged PIN or biometric credential resets when switching channels. Keep a documented recovery method for Windows Hello credentials and ensure testers can recreate PINs or enroll biometrics after channel changes. This is a practical risk to include in pilot SOPs.

Security-minded organizations should hold Copilot-enabled features to the same scrutiny as any third-party integration: risk assessment, threat modeling, logging of AI-related operations, and incident response plans that factor in AI-enabled automation. The visibility and policy surface are still evolving, so conservative opt-in strategies are sensible until controls mature.

---

What we verified and what remains provisional​

• Verified: Microsoft is actively releasing 26120-series builds to the Beta Channel and using a two-bucket rollout model (gradual vs. normal). Recent Beta and Release Preview posts confirm the focus on Recall, Click to Do, Copilot+ agent experiences, and numerous quality fixes. (blogs.windows.com)
• Verified: Known issues (0x80070005 rollback, Click to Do first-run slowness/crashes on Copilot+ hardware, Xbox controller Bluetooth bugchecks, live-captions translation instability) have been repeatedly documented in Microsoft’s Insider posts and tracked by community resources. (blogs.windows.com)
• Provisional / unverified: The specific KB number “KB5064071” as the cataloged cumulative update for Build 26120.5751 is cited in the announcement we received, but at the time of follow-up verification the KB entry and its full independent catalog changelog were not consistently indexed across the update catalog and third‑party trackers. For administrators who require the canonical KB documentation, confirm the KB in Microsoft’s Update Catalog or Flight Hub before blanket deployment.

If any claim above appears inconsistent with your local experience (for example, if you see different KB numbers or an immediate feature rollout on your device), that variance is consistent with Microsoft’s phased enablement approach and regional/hardware gating.

---

Final analysis — why this matters​

This Beta-channel flight is a continuation of Microsoft’s dual-track strategy: accelerate AI-enabled features while simultaneously tightening quality and manageability for mainstream release. Build 26120.5751 (KB5064071) is not a watershed feature drop; its value lies in steady improvements that make those larger AI scenarios more reliable and enterprise-ready.
Strengths:

• The Beta Channel continues to deliver meaningful reliability and accessibility fixes that directly improve day-to-day usability.
• Microsoft’s controlled rollout approach reduces blast radius for risky features and provides a mechanism to tune privacy and enterprise controls before general availability.

Risks and friction points:

• AI features still depend on a mix of hardware (Copilot+ certification), cloud services, and licensing; this complicates both end-user expectations and IT planning.
• Known update and driver-related instability (rollback errors, device-specific bugchecks) remain a real risk for Insiders running production workloads. Admins must continue cautious pilot deployments and robust rollback plans. (blogs.windows.com)

Practical takeaway:
For enthusiasts and testers, this Beta build is worth installing on test hardware to validate Copilot+ behaviors and to help Microsoft refine rollout criteria via Feedback Hub. For IT organizations, treat this flight as an advance preview of what may be coming to general releases and use it to stress-test image compatibility, policy controls, and backup/restore procedures — but avoid broad production deployment until the KB has been cataloged and the Flight Hub notes are confirmed.

---

Windows 11’s 24H2 servicing continues to be a delicate balance between ambitious AI integration and disciplined quality control. Build 26120.5751 (KB5064071) is another step in that journey: a stabilizing cumulative flight that nudges Copilot-driven experiences closer to mainstream readiness while highlighting the practical tasks that administrators and early adopters must still manage. Monitor Flight Hub and the Microsoft Update Catalog for the finalized KB documentation, keep Backup/Recovery and pilot policies current, and use Feedback Hub reports to help shape the next round of fixes.

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5751 (Beta Channel)