Microsoft on August 15, 2025, pushed Windows 11 Insider Preview Build 26200.5751 (KB5064071) to the Dev Channel, delivering a polished batch of user interface tweaks, fresh Click to Do selection modes, and a Snipping Tool window recorder. The flight continues the active 25H2 development cycle, where the company staggers Copilot+ AI features through its controlled rollout system. Insiders who flip on the “Get the latest updates as soon as they’re available” toggle will see the new features sooner, but the build also ships reliability fixes that apply broadly.

This release is more than a cosmetic refresh: it introduces flexible content selection gestures, a long-requested screen-recording refinement, and targeted fixes for crashes that tripped up earlier 26200 builds. At the same time, Microsoft flags a fresh crop of known issues—including an install rollback error, Arm64 developer woes, and a Recall glitch in the European Economic Area—that remind Insiders why the Dev Channel is called a testing ground.

Click to Do Gains Freeform, Rectangle, and Ctrl+Click Selection

The most interactive change lands in Click to Do, Microsoft’s on-device productivity utility that surfaces contextual actions for on-screen content. Starting with this build, Insiders can select objects with three new methods:

  • Freeform Selection – draw a lasso with a pen, finger, or mouse to grab irregular groups of text, buttons, and images.
  • Rectangle Selection – drag a straightforward bounding box, the same gesture millions use in Snipping Tool.
  • Ctrl+Click multi-select – add or remove individual items from a selection, bringing keyboard-and-mouse precision to a tool initially designed for touch.

Microsoft’s internal testing shows the new modes dramatically reduce friction on hybrid devices where users toggling between pen, touch, and mouse no longer have to adapt to a single rigid selection metaphor. Once a user selects the mixed content, they can apply Click to Do actions—summarize, remove background, copy, or extract text—regardless of whether the selected bits are images, UI controls, or lines of body text.

Not all actions run on every PC. The blog post reiterates that advanced Click to Do capabilities require a Copilot+ PC with on-device NPU acceleration. For users on standard x86 or Arm hardware without a qualifying neural processing unit, only a subset of actions will be available. Microsoft encourages Insiders to file feedback under Desktop Environment > Click to Do in the Feedback Hub.

Snipping Tool’s Window-Mode Recorder Removes the Guesswork

Screen recording inside Snipping Tool (version 11.2507.14.0 and later) now supports a dedicated window-mode option. Instead of manually dragging a rectangle or selecting the entire screen, users choose Record > Recording area > Window mode, pick any open app window, and capture begins framed tightly to that window. The recording area does not follow the window if it moves—once recording starts, the frame stays fixed—so users must position the app before hitting record.

For tutorial authors, IT support staff, and developers logging reproducible bugs, the addition eliminates the guesswork of cropping later. Microsoft confirms the update is rolling out gradually across both Dev and Canary channels, so not every Insider will see it immediately. The Feedback Hub category for any recording quirks is Apps > Snipping Tool.

File Explorer and Taskbar Polish Smooth Daily Interactions

Two quiet but noticeable UI adjustments land in this build:

  • Open with context menu – The colored backplate behind packaged-app icons has been removed. Icons now appear larger and cleaner, making it easier to identify the right handler when you right-click a file and thumb through the list.
  • Taskbar animations and fixes – Mouse-over transitions on app group buttons feel more fluid, and a regression that caused pinned apps to unpin after upgrading has been stamped out. A separate bug that showed duplicate additional clocks in the date/time tooltip also gets a fix.

These tweaks won’t rewrite productivity workflows, but they reflect the ongoing “sweat the details” phase of the 25H2 Dev cycle. For insiders who rely heavily on visual context cues—accessibility users, for example—the front-of-box icon sizes and smoother taskbar feedback reduce daily friction.

Reliability Fixes Target Click to Do Crashes, Live Captions, and DWM

Build 26200.5751 arrives less than two weeks after 26200.5742, which introduced several stability regressions. Microsoft lists these resolved items:

  • Click to Do no longer crashes when invoking text or image actions, a problem that hit 26200.5742 adopters.
  • Live captions on Copilot+ PCs are stable again after a crash-on-attempt bug.
  • Desktop Window Manager (DWM) crash reports have been reduced from prior flights.
  • File Explorer’s drive space rendering in dark mode now displays accurate colors, even when storage is critically low.

All fixes are available to everyone on this build, regardless of whether they have opted into the “get latest updates faster” toggle. Microsoft notes that feature-specific fixes—like the Click to Do remedy—fall under the same controlled rollout umbrella as the features themselves, but for this release the crash fixes appear to be deployed widely.

Known Issues: 0x80070005 Rollback, WPF/Arm64 Crashes, and Recall EEA Glitch

No Dev Channel release is without its cautionary notes, and 26200.5751 comes with a list Insiders should review before updating:

  • Install rollback with error 0x80070005 – Some machines may see the update download but then roll back with this generic access-denied code. Microsoft’s immediate workaround: open Settings > System > Recovery > “Fix issues using Windows update” and retry. A permanent fix is in development.
  • Visual Studio / WPF crashes on Arm64 – Building on reports that started in build 26200.5722, some Windows Presentation Foundation scenarios still trigger crashes on Arm64. Devs running 14-inch or 15-inch Snapdragon X laptops should test mission-critical .NET apps in a sandbox before deploying this flight.
  • Recall not working in the EEA – Insiders in the European Economic Area have reported Recall failing to activate. The remedy is a reset: Settings > Privacy & security > Recall & snapshots > Advanced settings > Reset Recall. Microsoft emphasizes that Recall remains opt-in, privacy-filtered, and should only be enabled on devices that don’t handle highly sensitive data.
  • Xbox Controller Bluetooth bugchecks – If connecting a wireless Xbox controller via Bluetooth triggers a blue screen, the suggested fix is to remove the oemXXX.inf (XboxGameControllerDriver.inf) entry in Device Manager under “View > Devices by driver.”
  • Shared section in File Explorer Home may appear when empty – A new, unaddressed cosmetic bug that Microsoft is still investigating.

IT administrators and power users should weigh these against the feature improvements before adding 26200.5751 to any pilot ring.

How to Get the Build and Control What You See

Dev Channel Insiders on the 26200.xxxx enablement package track will receive the update automatically through Windows Update. Microsoft’s Controlled Feature Rollout means not every device will see the new Click to Do or Snipping Tool features on day one. To jump the queue, head to Settings > Windows Update and turn on “Get the latest updates as soon as they’re available.” Machines managed via Windows Update for Business or MDM policies may not expose this toggle.

If the update fails or causes critical bugs, the usual advice applies: create a system restore point before installing, back up important data, and consider running Dev Channel builds in a virtual machine or on a secondary device. Recovery from a rollback error like 0x80070005 is possible with the built-in repair tool, but full reinstallation is the fallback.

Enterprise and IT Admin Considerations

Although the Dev Channel is not a production servicing branch, this build delivers several signals for IT pros planning future rollouts:

  • Hardware and licensing dependency – Advanced Click to Do actions and many Copilot experiences demand Copilot+ PC silicon (Snapdragon X, Intel Core Ultra 200V, or AMD Ryzen AI 300 series) plus an NPU. Some cloud-dependent actions may also require a Microsoft 365 Copilot subscription. Before piloting, inventory your fleet’s hardware capabilities and licensing posture.
  • Group Policy / MDM app removal – Windows now supports removing selected pre-installed Microsoft Store apps via Group Policy or MDM CSP on Enterprise and Education editions. This gives admins cleaner control over the out-of-box app footprint, but requires testing against your gold image.
  • Pilot ring strategy – Staged rollouts mean two devices on the same build can behave differently. Test key line-of-business scenarios (WPF apps, VPN clients, ReFS volumes, external GPU docks) in a small ring with clear telemetry. Have a rollback plan that doesn’t rely solely on Windows Recovery.
  • Privacy and Recall – Recall snapshots remain a liability for organizations in regulated sectors. Despite opt-in design and Windows Hello authentication, enabling Recall captures screen content. Independent reports have noted cautious browser vendor responses to snapshot-style collection. Admins should test Recall behavior with their specific browser fleet and data governance policies before approving even a pilot.

Verdict: A Worthwhile Step for Testers, but Not for Production

For Windows enthusiasts and developers who enjoy living on the bleeding edge, Build 26200.5751 is a meaningful upgrade. The new Click to Do selection gestures turn the feature into a truly multimodal tool, and Snipping Tool’s window recorder fills a gap that third-party utilities often handled. The UI polish in File Explorer and the taskbar contributes to a more cohesive desktop feel.

For IT departments and privacy-conscious users, the known issues demand caution. WPF crashes on Arm64, the 0x80070005 rollback, and the Recall reset requirement are not trivial. Microsoft has provided workarounds for each, but they underscore why the Dev Channel should never touch production workloads. If you manage a fleet, confine your experiments to a dedicated test group, monitor feedback channels, and wait for fixes to land in a more stable build before broad adoption.

Microsoft will continue refining these features in subsequent flights, with the final 25H2 feature update expected later this year. The Insider team has asked testers to log feedback through the Feedback Hub (WIN + F) with detailed repro steps and build number for any crashes or unexpected behavior. The official announcement blog post, authored by Amanda Langowski and Brandon LeBlanc, remains the authoritative resource for the complete changelog.