Microsoft rolled out Windows 11 Insider Preview Build 26120.5751 (KB5064071) to the Beta Channel on August 15, 2025, injecting new freeform and rectangle selection modes into Click to Do, polishing File Explorer’s context menu, and delivering a batch of stability fixes. The build continues the 24H2 branch’s controlled feature rollout cadence, turning on enhancements in waves for Insiders who toggle on “get the latest updates as they’re available.” While the update adds genuine productivity touches, especially for pen and touch users, it also carries familiar Beta Channel risks—install rollbacks, Bluetooth controller crashes, and regional feature gaps that require careful preflight checks.

Click to Do Gains Smarter Selection Tools

The most visible addition is a trio of selection improvements that transform Click to Do from a simple text/image picker into a more flexible intelligent overlay. Insiders can now choose between:

  • Freeform Selection – Lasso any irregular shape with a pen or finger, making it natural to grab complex diagrams, handwritten notes, or mixed content without boxing in unintended areas.
  • Rectangle Selection – Drag out a rectilinear marquee for fast, predictable selection of blocks, tables, or images.
  • Ctrl + Click Multi-selection – Hold Ctrl and click multiple entities—text blocks, images, graphs—to combine them into a single Click to Do action. This lets users, for instance, select a paragraph and an inline picture, then invoke a “summarize” or “draft” action that spans both.

These modes are particularly appealing for touchscreen and stylus-driven workflows. On the Surface Pro or similar convertible devices, Freeform Selection eliminates the friction of trying to frame non-rectangular content, while Rectangle Selection gives precision that a finger tap can’t always achieve. Microsoft included toolbar buttons for each mode and brief usage tips in the official blog post, signaling a push toward making Click to Do feel less clunky and more like a core system utility rather than an experimental overlay.

File Explorer and Taskbar Get Subtle UI Refinements

Build 26120.5751 also removes the accent-colored backplates behind packaged-app icons in the File Explorer “Open with” context menu. Icons for apps like Snipping Tool now display larger and cleaner, without the colored square backgrounds that sometimes clashed with dark mode or custom accent colors. It’s a small change, but for anyone who right-clicks files dozens of times a day, the cleaner menu reduces visual noise and makes icon recognition faster.

The taskbar receives mouse-over animation tweaks for grouped apps that feel smoother and more responsive. The update doesn’t alter the fundamental UX, but the micro-animations contribute to a perception of polish and fluidity that power users notice—especially when rapidly switching between multiple Edge windows or Office documents.

Stability Fixes and Gradual Rollouts

Alongside the feature additions, Microsoft included a pack of fixes that are gradually rolling out to Insiders who have the latest updates toggle enabled:

  • Start menu layout regressions and a safe-mode opening problem that surfaced in prior 26120 builds are patched.
  • Lock screen icon rendering bugs and occasional login hangs are addressed.
  • A bump in Desktop Window Manager (DWM) crashes reported in the previous flight is mitigated.
  • A specific Click to Do crash where text and image actions stopped working after Build 26120.5742 is fixed.

These corrections reflect the Beta Channel’s iterative nature. Community forum threads show that Insiders actively flagged the DWM and Click to Do issues, and Microsoft responded within the usual two-week release cadence. The quick turnaround reinforces that feedback is being actioned, but it also means that each new build carries the risk of new regressions—a trade-off Beta testers accept.

Known Issues: Installation Hurdles and Hardware Conflicts

Microsoft’s blog post is unusually frank about several nuisances Insiders should expect:

  • 0x80070005 Rollbacks: A subset of devices hit an install rollback when trying to apply recent 26120 updates. If you encounter this error, Microsoft advises navigating to Settings > System > Recovery > Fix issues using Windows Update. The company acknowledges the bug and is working on a root cause fix, but no timeline is given. Community reports confirm that the workaround works for many, though some machines required multiple attempts.
  • Xbox Bluetooth Controller Bugchecks: Connecting an Xbox controller via Bluetooth can trigger a system crash (blue screen). The documented workaround is to uninstall the oemXXX.inf (specifically XboxGameControllerDriver.inf) driver through Device Manager (View → Devices by Driver). This removes the offending driver until a patched version arrives. For gamers who rely on wireless controllers, this is a severe class of issue—system crashes are unacceptable on a daily-driver machine.
  • Recall Limitations in the EEA: Insiders in the European Economic Area may find Recall non-functional in certain flights. The blog notes a reset path via Settings, but given Recall’s privacy sensitivity (it captures activity snapshots), Microsoft appears to be applying extra regional controls while the feature matures.
  • File Explorer UI Quirks: Some users still see empty sections when clicking “Shared” or encounter color inconsistencies in dark mode. Restarting explorer.exe or launching File Explorer to a specific folder via WIN + R has served as a pragmatic workaround while fixes are staged.

These aren’t edge cases—0x80070005 and the controller bugcheck have generated notable discussion in Windows forums, and Insiders relying on Bluetooth audio or gamepads should consider deferring this flight until the issues are resolved.

Copilot+ PC and AI: Hardware Requirements and Licensing

A central undercurrent of the 24H2 Beta channel is the tight coupling between new AI experiences and Copilot+ PC hardware. Many Click to Do and on-device AI capabilities demand a Neural Processing Unit (NPU) capable of 40+ trillion operations per second (TOPS). Microsoft’s official Copilot+ hardware guidance lists qualifying processors, memory (at least 16 GB), and storage requirements. Without a Copilot+ PC, advanced features like Recall at full fidelity, Paint Cocreator, and certain Photos enhancements remain limited or entirely absent.

Additionally, generative workflows that integrate with Microsoft 365—such as summarizing an Office document via Click to Do—require a Microsoft 365 Copilot license and corresponding tenant configuration. The Microsoft 365 Copilot requirements documentation spells out those prerequisites. So even if you have the latest build and a Copilot+ PC, lacking a license will gate some cloud-assisted AI actions.

This hardware and licensing stratification creates a tiered Windows experience. Users with standard hardware will still see shell improvements and basic Click to Do actions, but the richest AI features remain locked behind a paywall and a hardware buy-in that excludes most existing PCs.

Preparing for Installation: A Checklist for Insiders

Beta Channel builds aren’t for the faint of heart. To minimize disruption, follow this preflight checklist:

  1. Back up critical data. Use OneDrive, an external drive, or full-image backup tools. Beta builds can corrupt user profiles or trigger boot failures.
  2. Create a system restore point. If the update fails catastrophically, a restore point can get you back to a working state without a full reinstall.
  3. Verify peripheral compatibility. If you depend on Bluetooth Xbox controllers, gaming wheels, or specialized drawing tablets, scan the known issues and be ready to defer the update.
  4. Update key drivers and firmware. Chipset, graphics, and Bluetooth driver updates often prevent install-time crashes. Check OEM update utilities or the Windows Update driver catalog.
  5. Toggle the latest updates switch with intent. Under Settings > Windows Update, turning on “Get the latest updates as they’re available” exposes you to features that are still in gradual rollout and may carry higher risk. Only enable it if you actively want to test those features.
  6. Know the recovery path. If the 0x80070005 rollback hits, go to Settings > System > Recovery > Fix issues using Windows Update as a first step. If that fails, a system image or Windows reinstall may be necessary.

These steps are pragmatic, not paranoid. Build 26120.5751 addresses several crashes, but the Beta Channel remains a sandbox where regressions routinely appear.

Enterprise Perspective: Testing and Validation in the Beta Channel

For IT admins, the Beta Channel is a crucial forward-compatibility testing ground—but not a production environment. Key operational considerations include:

  • Enablement package model: Cumulative updates like KB5064071 use an enablement package approach, meaning feature toggles and servicing changes are delivered without altering the major OS version. This reduces upgrade surface but still requires validation against your fleet’s imaging, driver, and security configurations.
  • Copilot+ hardware and licensing alignment: Organizations planning to pilot Copilot-driven productivity must budget for both supported hardware and Microsoft 365 Copilot licenses. Procurement, legal, and security reviews need to align early; without both pieces, the user experience will be incomplete.
  • Controlled Feature Rollout opacity: Because features are turned on in waves via server-side flags, deterministic validation is difficult. A feature that works on one machine may not appear on an identical build due to rollout timing. IT teams should plan for multi-week pilot groups and accept that feature availability isn’t immediate or guaranteed.
  • Security and privacy posture: Recall’s snapshot collection, even when opt-in and locally processed, introduces a new data surface. Before deploying Copilot+ PCs broadly, security teams must evaluate encryption at rest, per-app/web filtering, and consent mechanisms. The Microsoft 365 Copilot requirements also highlight cloud connectivity needs of integrated features, which may require firewall or proxy adjustments.

Analysis: Innovation at the Cost of Stability?

Build 26120.5751 encapsulates Microsoft’s current Windows strategy: push AI-enhanced productivity tools quickly, polish the core UI incrementally, and manage risk through staged rollouts. The Click to Do selection modes are genuine quality-of-life upgrades; Freeform lassoing makes the tool feel less like a proof-of-concept and more like an indispensable overlay for digital inking. The File Explorer icon cleanup is similarly welcome—small details that accumulate into a noticeably more modern interface.

Yet the Beta Channel’s recurring rough edges—repeated 0x80070005 rollbacks, controller-triggered bugchecks, and regional Recall gaps—underline the cost of rapid iteration. Each build that adds features can break something fundamental, and the workaround for the Xbox controller bug (uninstalling the driver) is a serious, productivity-killing measure for mainstream users.

The hardware-dependent nature of full AI experiences also raises fragmentation concerns. Insiders on older Surface Pros or standard laptops will see Click to Do improvements but won’t access the most compelling AI capabilities unless they invest in a new Copilot+ PC. That’s a defensible technical requirement, but it segments the Windows 11 user base and could slow adoption of features that developers are expected to target.

Troubleshooting Quick Wins

If you do install 26120.5751 and run into trouble, these proven workarounds can get you back on track:

  • 0x80070005 failure: Run Settings > System > Recovery > Fix issues using Windows Update. Many Insiders recovered with this path; if it fails, a system image restore or a Windows repair install from USB may be needed.
  • Click to Do crashes: Ensure all cumulative updates are applied (this flight includes the fix). If crashes persist, file a Feedback Hub report under Desktop Environment > Click to Do with repro steps.
  • Xbox controller bugcheck: Open Device Manager, switch to View → Devices by Driver, find oemXXX.inf / XboxGameControllerDriver.inf and uninstall it. This removes the Bluetooth driver temporarily.
  • File Explorer UI glitches: Restart explorer.exe from Task Manager or launch File Explorer directly to a folder path (WIN + R, type C:\). Persistent issues should be reported via Feedback Hub.

What This Build Signals for Windows’ Future

Build 26120.5751 is not a landmark release, but it’s a meaningful step in the incremental enrichment of Windows 11’s AI and shell layers. The Click to Do selection evolution shows Microsoft listening to usability feedback; the taskbar and File Explorer tweaks prove attention to craft. The known issues and hardware gating, however, remind us that the Copilot+ era is still taking shape—exciting, but unforgiving for those who jump in without preparation. Insiders who treat each Beta flight as an experiment, keep full backups, and stay aware of the documented pitfalls will get the most out of this and future 24H2 builds.