Windows 11 Insider Preview Build 26200.5751: New Click to Do, Snipping Tool, Fixes, and IT Guidance

  • Thread Author

Headline: Windows 11 Insider Preview Build 26200.5751 (KB5064071) — what’s new, what’s fixed, and what Insiders and IT should do next
Byline: Analysis for WindowsForum.com — published Aug 15, 2025
Lead
Today Microsoft released Windows 11 Insider Preview Build 26200.5751 (KB5064071) to the Dev Channel. The flight continues the 25H2-era Dev Channel pattern: small, targeted UX polish and reliability fixes mixed with incremental Copilot/Copilot+ feature rollouts that are being staged using Microsoft’s controlled feature rollout systems. The official Windows Insider blog post (Aug 15, 2025) lists the build’s headlines: new Click to Do selection modes, a Snipping Tool window-mode recorder, File Explorer and taskbar polish, several bug fixes, and known issues and workarounds for Insiders and developers. The release also reiterates Microsoft’s ongoing “gradual rollout” approach — turning on a Settings toggle lets some Insiders opt in to see staged features earlier. (Windows Insider Blog, Aug 15, 2025.)
What this build is (brief)
  • Target: Dev Channel (active development for Windows 11, version 25H2; enablement package series Build 26200.xxxx).
  • Package: Published as Build 26200.5751, carries cumulative content identified as KB5064071.
  • Scope: Mix of small feature improvements (many staged/gradual for toggle-on Insiders), fixes for crashes and stability issues, and app updates (Snipping Tool). The Dev Channel remains experimental — features here may change or be removed. The blog post authors are Amanda Langowski and Brandon LeBlanc (Windows Insider Blog, Aug 15, 2025).
Quick summary — the most user-visible items
  • Click to Do: New selection modes (Freeform, Rectangle, and Ctrl+Click multi-select) to let you select mixed content on-screen (text + images + UI elements) and apply Click to Do actions more naturally.
  • Snipping Tool: Window-mode recording added to the Snipping Tool recorder (select a single app window as the recording area).
  • File Explorer: “Open with” context menu icon back‑plate removal (icons appear larger, cleaner).
  • Taskbar: Animation polish when hovering over app groups; fixes to pinned-app unpinning regressions.
  • Reliability: multiple DWM/crash and Live Captions fixes; Click to Do crash fixes for those who updated to Build 26200.5742.
  • Known issues: 0x80070005 rollback errors for some Insiders during install, WPF/Visual Studio crashes on Arm64 in some scenarios, Xbox controller Bluetooth bugcheck reports, and other channel- and region-specific issues (see “Known issues” section and workarounds below).
Deep dive — what’s new and why it matters
1) Click to Do: selection modes that make on‑screen actions feel native
What changed: Click to Do now offers three new ways to select objects on screen — Freeform Selection (draw with pen/finger), Rectangle Selection (drag a box), and Ctrl+Click multi-select. That means you can now include multiple entity types (images, text, UI controls) in one selection gesture, then run Click to Do actions (summarize, remove background, copy, etc.). This is explicitly aimed at touch/pen and hybrid device workflows and reduces friction for mixed-content tasks.
Why it matters: Click to Do is a core part of Microsoft’s on-device interaction model for quick, contextual productivity tasks. Prior to this change, selection felt more brittle on touch devices and mixed-content layouts. Freeform and rectangular selection let creators and note-takers work more fluidly; Ctrl+Click brings parity with keyboard/mouse power users.
Feedback / testing notes: Microsoft asks Insiders to file Click to Do feedback in Feedback Hub under Desktop Environment > Click to Do. The release also calls out that some Click to Do actions require Copilot+ PC hardware or on-device NPU acceleration for the most advanced, local AI tasks. For the broader context about staged AI rollouts and hardware/licensing dependencies, see Microsoft’s notes on gradual rollouts and Copilot+ PCs. indow-mode screen recording
What changed: Snipping Tool (version 11.2507.14.0+) is getting a window-mode recorder: choose Record → Recording area → Window mode and pick a specific app window. The recorder sizes the capture tightly to the chosen window; once recording starts, the capture area remains fixed (it won’t follow the window if it moves).
Why it matters: For tutorials, bug repros, and focused app demonstrations this is a quality-of-life improvement: you don’t have to manually crop or set an arbitrary rectangle if you only want a single app captured. It’s especially helpful for app developers, support teams, and anyone who creates quick how‑tos.
Feedback: Snipping Tool feedback should be filed under Apps > Snipping Tool in Feedback Hub. Microsoft is rolling this Snipping Tool update to Canary and Dev channels.
3) File Explorer anolish
What changed: Microsoft removed the colored “backplate” behind packaged-app icons in the “Open with” context menu, which increases icon size and visual clarity. Other File Explorer fixes for dark mode color anomalies and home/Shared section visibility are listed in the release.
Why it matters: Small UI polish like this improves scanability and accessibility of context menus, particularly for users who rely on visual cues. It also reduces visual noise when many installed apps provide icons in the Open with list.
4) Taskbar & System Tray animations and fixes
What changed: Animation tweaks when mouse‑overing app groups in the taskbar are intended to make the interaction feel smoother. The build also includes fixes for pinned-app unpinning regression that affected previous Dev builds, and a fix for duplicate additional clocks in the date/time tooltip.
Why it matters: The taskbar is a heavily used surface; smoothing regressions and behavior inconsistencies reduces daily annoyance. If you were hit by the pinned-app bug in recent Dev builds the release should stop apps being unpinned after updating.
What Microsoft fixed (selected reliability items)
  • Click to Do: resolved crashes and non-working text/image actions introduced in Build 26200.5742.
  • Live captions: fixed crashes when attemn on Copilot+ PCs.
  • DWM crashes: reduced occurrences reported in prior flights.
    -mode color fixes for low-space drive rendering and other reliability improvements.
    These fixes are a mix of staged (toggle-on) and wide-rollout items; check the build notes to see which items Microsoft considers “gradual rollout” vs “for everyone”.
Known issues you should know about (and immediate workarounds)
  • Install rollback 0x80070005: Some Insiders may see the update roll back with error 0x80070005. Microsoft suggests using Settings > System > Recovery > “Fix issues using Windows update” as a suggested remediation while they work on a fix.
  • Visual Studio / WPF crashes on Arm64: Reports continue for some WPF scenarios on 00.5722 and higher — developers using Arm64 machines should test critical workflows before adopting this flight.
  • Recall (EEA): Some Insiders in the European Economic Area reported Recall not working; Microsoft advises resetting Recall via Settings > Privacy & security > Recall & snapshots > Advanced settings > Reset Recall to restore functionality. Recall continues to be an opt‑in, staged feature with privacy filters — exercise caution before enabling it on machines that handle sensitive information.
  • Xbox Controller Bluetooth bugchecks: If you see bugchecks when using an Xbox controller over Bluetooth,ound: View > Devices by driver → find and uninstall the oemXXX.inf (XboxGameControllerDriver.inf) entry for that driver.
  • Shared in File Explorer Home may show when empty: Microsoft listed this as a new, under-investigation issue.
    If you’re a developer or admin, factor these issues into any test plan before installing on production hardware.
Guidance for Insiders — how to get the build and how to control staged rollouts
  • Dev Channel Insiders on the 25H2/enablement package track (Build 26200.xxxx) will receive the update via Windows Update. The Windows Insider blog reiterates that many features are being rolled out gradually using Microsoft’s Control Feature Rollout system; Insiders who want to see staged features as soon as possible can enable the toggle at Settings > Windows Update > “Get the latest updates as soon as they’re available.” If you are managed (e.g., via Windows Update for Business), that toggle may be unavailable.
  • If you hit a severe problem: create a system restore point before installing preview builds, back up critical data, consider r virtual machine for Dev Channel flights, and enroll only devices you’re willing to recover if needed.
Enterprise / IT admin considerations
Although this release is Dev Channel and not a production servicing channel, several items are relevant to IT pros and admins planning staging or compatibility tests:
  • Copilot/Copilot+ dependencies: Some AI actions and the most advanced Click to Do features may require Copilot+ PC hardware and/or Microsoft 365 Copilot licensing. If you plan to evaluate these features in a corporate pilot, inventory hardware capabilities (on-device NPU / Copilot+ compatible silicon) and licensing prerequisites first.
  • Group Policy/MDM: Microsoft now allows removal of selected pre-installed Microsoft Store apps by Group Policy/MDM CSP on Enterprise/EDU devices (cinked in the Insider blog for the CSP/policy details). This makes it easier to manage the out-of-box app footprint for devices in your tenant.
  • Pilot ring advice: Because features are staged, Microsoft’s Controlled Feature Rollout means you’ll see behavior differences across devices. For enterprise pilots, incrcise your key app compatibility scenarios (WPF apps, ReFS or advanced storage, VPN and remote desktop paths) and plan a rollback strategy. Community histories of fast Insider flights show rapid identification of driver/agent incompatibilities; keep a ring‑based rollout with clear telemetry and rollback processes.
Privacy and security — what to consider before enabling AI features
  • Recall and snapshot features capture screen content; Microsoft designs Recall as opt‑in with filters and Windows Hello authentication, but it is still capturing snapshots of app and web activity when enabled. For devices used with sensitive data (banking, healthcare, legal), administrators and users should avoid enabling Recall until they’ve reviewed policy controls and encryption/tenant settings. Independent reporting and some browser vendors have signalled cautious default responses to Recall-style snapshot collection, so admins should test behavior with your browser fleet and privacy posture in mind.
  • On-device AI vs cloud: Some Click to Do and Copilot experiences run on-device (requiring Copilot+ silicon), while other summarization or M365-integrated actions may use cloud services bounensing. This split matters for data governance — decide whether cloud‑based analysis is acceptable for your data flows before enabling enterprise-wide Copilot integrations.
Actionable checklist — before you install this Dev build
  • If you’re an enthusiast Insider:
  • Back up critical data or use a VM/test device.
  • Turn ON the toggle in Settings > Windows Update if you want to grlier — but understand it may expose experimental behaviors.
  • If impacted by the 0x80070005 rollback, run Settings > System > Recovery > “Fix issues using Windows update” and file feedback if the problem persists.
  • If you’re an IT pro evaluating:
  • Inventory hardware for Copilot+ requirements if you want to test the new Click to Do selection capabilities with on-device AI.
  • Test your WPF/.NET apps on Arm64 devices if you have Arm deploymreports were raised).
  • Pilot on a small ring and monitor telemetry for DWM, File Explorer, and device drivers (GPU, input, external GPUs over Thunderbolt have had past regressions).
  • Validate Group Policy/MDM removal of packaged apps if you plan to use that capability.
How to report issues and give feedback
  • File Feedback Hub reports (WIN + F) for specific areas: Click to Do feedback under Desktop Environment > Click to Do; Snipping Tool under Apps > Snipping Tool; other issues in the category most closely matching yooducible crashes, include repro steps, build number (26200.5751), and attach logs or ETL traces when possible. Microsoft’s Insider docs and Flight Hub contain links to support tips and known-workaround steps.
Verdict — who should install and why
  • Early adopters and power users who enjoy testing new UI/AI interactions and who are comfortable with occasional breakage will find value in the improved Click to Do selection model and Snipping Tool enhancements.
  • Developers and IT admins should not deploy Dev Channel builds to production devices; instead, use a controlled pilot to validate compatibility especially for WPF/Arm64 applications and any scenarios that interact with device sensors, VPN, or specialized storage (ReFS).
  • Privacy-conscious users and organizations should carefully evaluate Recall and other snapshot-based features before enabling them; they are opt-in but may capture sensitive content.
References and context (selected)
  • Windows Insider Blog: Announcing Windows 11 Insider Preview Build 26200.5751 (Dev Channel), Amanda Langowski & Brandon LeBlanc, published Aug 15, 2025 (official build notes and screenshots).
  • Background on gradual rollout, Copilot/Copilot+ hardware and licensing dependencies, and enterprise cautions.
  • Snipping Tool and Dev/Canary rollout context and build‑by‑build notes for recent 26200 series flights.
  • Practical breakdowns of recent 26200.xxxx Dev Channel flights and their feature deployment model (how to turn on the “get the latest updates” toggle and what “gradual rrly analysis and advice for admins (pilot rings, rollback procedures, Windows Backup / enterprise feature sider posts).
Closing / next steps
Build 26200.5751 is another incremental Dev Channel flight that smooths outstanding bugs, polishes the UI, and advances the Copilot-driven interactionble steps. If you’re a Windows Insider on the Dev Channel and you want to try these updates, enable the “get the latest updates” toggle and instal but do so on a non‑critical device or in a controlled pilot. If you manage devices for others, read the build notes carefully, inventory Copilot+ hardware/licensing implications, and pilot before broader deployment.
If you’d like, I can:
  • Produce a short step‑by‑step troubleshooting guide for the most common issues in this build (0x80070005 rollback, Xbox controller bugcheck, Recall reset).
  • Generate a one‑page checklist IT teams can use to pilot Dev Channel builds safely across a 3–4 week test window.
    Which would you prefer?

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26200.5751 (Dev Channel)