Microsoft has shipped Windows 11 Insider Preview Build 26120.5751 (KB5064071) to the Beta Channel, a modest but meaningful update for Insiders on Windows 11, version 24H2 that refines Click to Do selection, softens some visual chrome in File Explorer, and continues Microsoft’s phased “controlled feature rollout” approach for AI-enabled experiences. The release, published on August 15, 2025, bundles a set of gradual-rollout improvements and fixes for both Click to Do and core shell areas while documenting a familiar set of known issues Insiders should be prepared for. (blogs.windows.com)
Microsoft’s Beta Channel updates for the 24H2 track use an enablement package model and rely heavily on its Controlled Feature Rollout mechanism. That means builds such as Build 26120.5751 (KB5064071) ship platform changes and a list of features that are either turned on for everyone in the Beta Channel or gradually rolled out to only those Insiders who opt-in to receive the very latest updates. Turning on the “get the latest updates as they’re available” toggle in Settings > Windows Update exposes more of those gradual-rollout items sooner. The blog post accompanying the release underscores that not every previewed feature is guaranteed to ship in final form. (blogs.windows.com)
This release follows a steady series of 26120.xxxx builds that expanded Copilot+ PC experiences, File Explorer AI actions, taskbar and Start menu improvements, and other platform refinements—changes that are still being turned on in waves for many Insiders. Threaded community summaries and prior release notes show a consistent pattern: Microsoft iterates quickly in Beta, pushes fixes based on feedback, and manages feature surfacing through staged rollouts. (blogs.windows.com)
Separately, some generative workflows that integrate with Microsoft 365 (for example, Summarize that ties into Office or Copilot experiences across Microsoft apps) require a Microsoft 365 Copilot license and corresponding tenant configuration. These are service-side requirements—local hardware and OS builds are necessary but not sufficient to unlock end-to-end Copilot app features. Microsoft’s Microsoft 365 Copilot requirements documentation covers licensing and tenant prerequisites in detail. (learn.microsoft.com)
Implications:
From a product lens, the introduction of Freeform and Rectangle selection modes is an example of quality-of-life improvements that compound over time. Individually small, these changes matter because they make AI-assisted tasks feel less awkward and more predictable—key for adoption. The larger question remains whether Microsoft can keep the incremental builds stable enough for broad enterprise testing while continuing to develop performant, private, on-device AI experiences that are accessible beyond the narrow set of Copilot+ hardware.
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5751 (Beta Channel)
Background / Overview
Microsoft’s Beta Channel updates for the 24H2 track use an enablement package model and rely heavily on its Controlled Feature Rollout mechanism. That means builds such as Build 26120.5751 (KB5064071) ship platform changes and a list of features that are either turned on for everyone in the Beta Channel or gradually rolled out to only those Insiders who opt-in to receive the very latest updates. Turning on the “get the latest updates as they’re available” toggle in Settings > Windows Update exposes more of those gradual-rollout items sooner. The blog post accompanying the release underscores that not every previewed feature is guaranteed to ship in final form. (blogs.windows.com)This release follows a steady series of 26120.xxxx builds that expanded Copilot+ PC experiences, File Explorer AI actions, taskbar and Start menu improvements, and other platform refinements—changes that are still being turned on in waves for many Insiders. Threaded community summaries and prior release notes show a consistent pattern: Microsoft iterates quickly in Beta, pushes fixes based on feedback, and manages feature surfacing through staged rollouts. (blogs.windows.com)
What’s new in Build 26120.5751 — the headline items
Click to Do: smarter selection modes
The most visible addition in this flight is new selection modes for Click to Do. Microsoft added:- Freeform Selection — draw with a pen or finger to lasso arbitrary shapes.
- Rectangle Selection — drag a box to select everything inside the rectangle.
- Ctrl + Click multi-select — combine multiple different entity types (text, images, etc.) into a single selection. (blogs.windows.com)
File Explorer: cleaner “Open with” context menu
The context-menu “Open with” list no longer draws accent-colored backplates behind packaged-app icons (for example, Snipping Tool). The icon treatment results in larger, more readable icons and a slightly cleaner context menu visual. This is a UI polish rather than a functional overhaul, but it’s the kind of small improvement that matters in frequent interactions. (blogs.windows.com)Taskbar & animations
Small taskbar animation changes were introduced—mouse-over animations for grouped apps on the taskbar were updated to feel smoother and more responsive. These are subtle UX changes that contribute to a more modern, responsive shell. (blogs.windows.com)Stability and bug fixes
The release includes a set of fixes that are gradually rolling out to Insiders who have the “get the latest updates” toggle turned on, including:- Fixes for Start menu behavior (smaller layout regressions, safe mode opening).
- Fixes for login/lock screen icon rendering and lock screen hangs.
- Fixes for DWM crash increases reported in the prior flight.
- A Click to Do crash fix (Text and image actions not working after Build 26120.5742). (blogs.windows.com)
Known issues and installation caveats (what to watch for)
Microsoft lists several known issues in the blog post; key items to note before installing:- 0x80070005 rollback on some devices: a subset of Insiders experienced rollbacks while installing recent 26120 updates. Users encountering that error are advised to try Settings > System > Recovery > “Fix issues using Windows Update.” The issue is acknowledged and Microsoft is working on a fix. (blogs.windows.com)
- Recall (EEA-specific issues): Insiders in the European Economic Area may find Recall not functioning in some flights; the blog describes a reset path via Settings when this occurs. Given Recall’s privacy sensitivity (it depends on snapshot collection), expect Microsoft to apply extra caution and regional controls while the feature is matured. (blogs.windows.com)
- Xbox controller Bluetooth bugcheck: some users reported bugchecks (system crashes) when using Xbox Bluetooth controllers. The blog documents a device-driver workaround: uninstall the oemXXX.inf (XboxGameControllerDriver.inf) driver via Device Manager. While a workaround exists, this is a severe class of issue (bugcheck), so Insiders using Bluetooth controllers should delay installing if they rely on that hardware. (blogs.windows.com)
- File Explorer UI/behavior quirks: cases such as Shared showing empty sections and color problems in dark mode persist for some users—these are being tracked and fixed gradually. (blogs.windows.com)
What this means for Copilot+ PC and AI features
A central reality of the 24H2-era Beta Channel work is that many new AI experiences are targeted at Copilot+ PCs—devices equipped with a high-performance Neural Processing Unit (NPU) capable of performing 40+ trillion operations per second (TOPS). Several Click to Do and other AI features either depend on Copilot+ hardware for full functionality or will be partially degraded on non‑Copilot devices. Microsoft’s hardware guidance and Copilot+ documentation explicitly list the hardware thresholds and the feature set supported only on Copilot+ devices. If your goal is to test the full set of on-device AI experiences, a Copilot+ PC meeting the published requirements is necessary. (support.microsoft.com, learn.microsoft.com)Separately, some generative workflows that integrate with Microsoft 365 (for example, Summarize that ties into Office or Copilot experiences across Microsoft apps) require a Microsoft 365 Copilot license and corresponding tenant configuration. These are service-side requirements—local hardware and OS builds are necessary but not sufficient to unlock end-to-end Copilot app features. Microsoft’s Microsoft 365 Copilot requirements documentation covers licensing and tenant prerequisites in detail. (learn.microsoft.com)
Implications:
- Individuals using consumer PCs without a qualifying NPU will still see many interface and shell improvements, but advanced on-device AI capabilities (e.g., Paint Cocreator, some Photos enhancements, Recall at full fidelity) will remain limited or unavailable. (support.microsoft.com)
- Organizations evaluating Copilot workflows must plan for licensing and network endpoints (Copilot integrates with Microsoft 365 and may require connectivity to additional services). (learn.microsoft.com)
Installation checklist and recommended prep (for Insiders)
Installing Beta Channel builds is straightforward but not risk-free. Adopt the following checklist to lower the chance of data loss and to streamline recovery if something goes wrong:- Back up critical data. Use OneDrive, an external drive, or enterprise backup tools. Beta builds can trigger unexpected behavior—backups are the single most reliable safety net.
- Create a system restore point or full image. If you need an immediate rollback beyond the OS rollback mechanism, system images or full-disk backups accelerate recovery.
- Confirm peripheral compatibility. If you use Bluetooth Xbox controllers or specialized devices, check blog-known-issue notes and be prepared to defer the update until fixes are pushed. (blogs.windows.com)
- Update key drivers and firmware. Graphics drivers and firmware updates often fix install-time or runtime crashes. Use OEM update utilities or Windows Update driver catalog entries.
- Turn ON the Beta Channel “latest updates” toggle only if you want earlier controlled-rollout features. You can find it under Settings > Windows Update; toggling it exposes features that are gradually rolled out and may carry more risk. (blogs.windows.com)
- Know how to invoke the recovery workflow. If you hit 0x80070005 rollback or other install failures, go to Settings > System > Recovery > “Fix issues using Windows Update” to attempt the recommended repair path. (blogs.windows.com)
Enterprise and IT considerations
For IT pros and system admins, the Beta Channel remains a testing and compatibility validation environment—not production. A few specific points of interest:- Enablement package model and update cadence: The Beta Channel’s 24H2 enablement package approach means cumulative servicing changes and feature toggles can be delivered without changing the major OS version string. This reduces the surface for disruptive upgrades, but it still requires validation against your fleet’s imaging, driver, and security stacks. (blogs.windows.com)
- Copilot+ hardware and licensing: If your organization plans to leverage Copilot-driven productivity workflows, prepare for two separate investments: hardware (Copilot+ PCs with NPUs) and Microsoft 365 Copilot licensing and tenant configuration. Both are prerequisites for the full on-device and cloud-assisted Copilot experience. Align procurement, licensing, and security review timelines if pilot testing is on the roadmap. (support.microsoft.com, learn.microsoft.com)
- Controlled Feature Rollout limits reproducibility: Because many features are rolled out in waves via server-side flags, validating a user-visible feature across a pilot group can be harder—the feature may simply not be enabled on some machines even if the OS build is current. IT teams should plan for staged pilot groups and accept that deterministic QA for feature availability may require coordination with Microsoft or timing windows that span days or weeks. The blog and community reporting reinforce this operational nuance. (blogs.windows.com)
- Security posture and privacy: Features like Recall and local AI actions interact with sensitive data and may require additional policy review. Recall is opt‑in and has per-app and per-website filters, but its privacy surface area means security teams need to validate data flows, encryption, and consent mechanisms before wide deployment. (blogs.windows.com)
Risks, trade-offs, and critical analysis
Every Beta Channel post is an exercise in trade-offs. Build 26120.5751 illustrates several ongoing tensions in Microsoft’s Windows roadmap:- Rapid innovation vs. platform stability. The Click to Do selection improvements are useful and represent genuine progress for pen/touch workflows. But incremental UI changes rolled out quickly increase the risk of regressions; earlier 26120 builds had regressions that required emergency fixes. The 0x80070005 rollback reports and controller bugchecks are concrete reminders that preview builds can break critical devices. (blogs.windows.com)
- On-device AI dependence on new hardware. Copilot+ PC features are compelling, yet they favor users able to buy specialized hardware. That creates a tiered Windows experience—some users will get the fastest, most private AI processing on-device while others will see limited or cloud-dependent behavior. That fragmentation is sensible from a capability standpoint but complicates developer expectations and enterprise planning. Microsoft’s published Copilot+ hardware guidance makes the requirements clear, but it doesn’t change the reality that many devices in circulation will not qualify. (support.microsoft.com)
- Privacy and data governance. Features that capture local snapshots (Recall) or perform local AI actions still require careful governance in enterprise environments. Although Microsoft emphasizes local processing for many Clip/Click operations, integrations with Microsoft 365 services and tenant-level Copilot features require cloud connectivity and licensing; privacy teams should evaluate end-to-end flows. (learn.microsoft.com, blogs.windows.com)
- Rollout opacity. Controlled Feature Rollout is great for risk mitigation, but it can be frustrating for testers and admins who need deterministic feature exposure. Microsoft’s approach reduces blast radius but increases time-to-visibility for feature validation. The Beta Channel’s toggle helps, but it’s not a guarantee. (blogs.windows.com)
Troubleshooting quick wins (if you hit problems)
- If your update fails with 0x80070005, try Settings > System > Recovery > “Fix issues using Windows Update” first. Many Insiders have recovered using that flow. (blogs.windows.com)
- If Click to Do crashes after update, ensure your device has applied all cumulative updates; this flight includes a fix rolling out for that exact issue. If crashes persist, file Feedback Hub reports under Desktop Environment > Click to Do and include repro steps. (blogs.windows.com)
- For Xbox controller bugchecks, uninstall the oemXXX.inf (XboxGameControllerDriver.inf) device driver via Device Manager (View → Devices by Driver), as documented by Microsoft. This removes the offending Bluetooth driver until a patched version is distributed. (blogs.windows.com)
- If File Explorer shows odd UI colorations or the Shared pane looks empty, restarting explorer.exe or launching File Explorer to a specific folder (WIN + R → folder path) has been a pragmatic workaround while fixes are staged. Report persistent repros in Feedback Hub. (blogs.windows.com)
How this fits the bigger picture: where Windows is headed
Build 26120.5751 is another incremental step on Microsoft’s multi-pronged Windows strategy: modernize core shell interactions (Start, Taskbar, File Explorer), fold AI into everyday workflows via Click to Do / Copilot, and gradually expose larger capabilities to Copilot+ PCs. The cadence of Beta Channel updates shows Microsoft is balancing UX polish with iterative AI feature delivery, while still dealing with the perennial trade-offs of peripheral and driver compatibility. Community reporting and forum threads from the last several flights show that Insiders are engaging actively—reporting regressions and shaping the product with feedback that often surfaces in subsequent flights.From a product lens, the introduction of Freeform and Rectangle selection modes is an example of quality-of-life improvements that compound over time. Individually small, these changes matter because they make AI-assisted tasks feel less awkward and more predictable—key for adoption. The larger question remains whether Microsoft can keep the incremental builds stable enough for broad enterprise testing while continuing to develop performant, private, on-device AI experiences that are accessible beyond the narrow set of Copilot+ hardware.
Bottom line
Windows 11 Insider Preview Build 26120.5751 (KB5064071) is a conservative, practical update that improves Click to Do selection, cleans up File Explorer visuals, and patches stability regressions introduced in recent Beta flights. It’s an attractive update for testers focused on pen/touch workflows and anyone tracking the steady enrichment of Copilot-era features, but it’s still preview-level software: expect staged rollouts, intermittent regressions (notably the 0x80070005 install rollback and Bluetooth controller bugchecks), and hardware- or license-based gating for the richest AI experiences. Back up before installing, validate peripherals, and plan pilot timelines carefully if you’re evaluating Copilot+ workflows in an organizational setting. (blogs.windows.com, support.microsoft.com, learn.microsoft.com)Quick reference: where to look next
- For the official release notes and the full list of changes, consult the Windows Insider Blog entry announcing Build 26120.5751 (KB5064071). (blogs.windows.com)
- For hardware requirements and feature lists tied to Copilot+ PCs, review Microsoft’s Copilot+ hardware guidance. (support.microsoft.com)
- For Microsoft 365 licensing and tenant prerequisites for Copilot integrations, see the Microsoft 365 Copilot requirements documentation. (learn.microsoft.com)
- Community threads and forum summaries for prior 26120.xxxx flights provide pragmatic context about real-world regressions and fixes.
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5751 (Beta Channel)
