Microsoft shipped Windows 11 Insider Preview Build 26200.5761 (KB5064093) to the Dev Channel on August 22, 2025, delivering a targeted set of Copilot‑era AI enhancements, visual polish, and reliability fixes. The update lands as the 26200 series continues to serve as the active development stream for the 25H2 enablement package, blending under‑the‑hood stability work with visible user‑facing refinements that address real friction points for Insiders. This cumulative release does not introduce a single blockbuster feature but instead sharpens the interaction model around Click to Do, extends the Snipping Tool with a long‑requested window‑mode recording option, and quietly corrects a series of shell and compositing regressions that have dogged recent flights.

Like most Dev Channel drops, Build 26200.5761 arrives with staged feature rollouts and hardware‑dependent capabilities. Two identical machines running this build may expose different functionality depending on Microsoft’s server‑side feature flags and whether the device meets Copilot+ specifications. Insiders who have been tracking the 26200 pipeline will recognize a familiar rhythm: incremental improvements that aim to make daily workflows feel more fluid across touch, pen, and mouse, while enterprise administrators gain new policy levers to control built‑in Store apps.

What’s Inside Build 26200.5761

The official release notes and community reports highlight five core areas of change:
- Click to Do enhancements – Three new selection modes (freeform, rectangle, and Ctrl+Click multi‑select) plus stability fixes for Copilot‑driven actions.
- Snipping Tool window‑mode recording – A companion app update that lets users capture a fixed application window without post‑crop work.
- File Explorer and context‑menu polish – Removal of the accent‑colored backplate on packaged‑app icons, making icons larger and improving scanability.
- Taskbar, Start, and animation refinements – Smoother hover animations for taskbar app groups, a fix for pinned‑app unpinning regressions, and Start menu layout corrections.
- Reliability fixes – Targeted patches for DWM crashes, Live Captions crashes on Copilot+ PCs, and Click to Do crash regressions from earlier 26200 flights.
- Enterprise controls – Group Policy and MDM CSP options now allow removal of select built‑in Store apps on Enterprise and Education editions.

None of these changes rewrite the Windows 11 playbook, but they address pain points that power users and IT admins have flagged repeatedly. For Insiders willing to accept the inherent risks of the Dev Channel, the build offers practical, immediately noticeable benefits.

Click to Do Gains Freeform Input and Multi‑Select

The most consequential user‑facing change in this update lands inside Click to Do, Microsoft’s lightweight on‑screen assistant that ties into Copilot workflows. Previously, selecting on‑screen content for AI‑powered actions felt constrained. Build 26200.5761 expands the selection toolkit with three new modes:
- Freeform Selection – Draw an arbitrary shape using pen or touch to capture mixed entities (text blocks, images, UI fragments).
- Rectangle Selection – Classic drag to define a rectangular capture area.
- Ctrl + Click – Multi‑select disparate items with a keyboard‑mouse combination.

For hybrid‑content workflows—note‑taking, quick summarization, one‑shot edits—these modes are transformative. They remove the stilted step of switching between snipping tools and Copilot, particularly on pen‑capable devices like the Surface Pro. Instead of approximating a rectangular crop around a flowchart, a user can now lasso precisely the diagram fragments and embedded text they want to act on.

Alongside the new interaction models, Microsoft has baked in fixes for known Click to Do crashes that surfaced in earlier 26200 flights. Insiders who rely on these AI actions should see fewer interruptions. However, the feature remains partially hardware‑gated: advanced Click to Do actions that require on‑device NPU acceleration are only available on Copilot+ PCs, and even then, availability may be controlled via server‑side flags. Administrators and privacy‑conscious users should verify whether content is processed locally or routed to cloud endpoints, as public documentation on telemetry and encryption for these actions remains sparse.

Snipping Tool Adds Window‑Mode Recording

The Snipping Tool companion app update bundled with this build introduces a long‑requested window‑mode recording option. When a user initiates a recording, they can now select a specific application window, and the capture area remains locked to that window’s boundaries for the duration. The feature streamlines the creation of short demos, troubleshooting recordings, and app‑specific step‑throughs without requiring a full desktop capture and subsequent cropping.

Practical implications are mixed. On the plus side, the targeted capture eliminates post‑production steps and reduces file sizes. On the other hand, the recording is truly fixed: if the source window is moved or covered, the recording does not follow it and will capture only the obscured area. This is preview‑quality behavior, and early Insider feedback has flagged edge cases involving overlay dimming, inconsistent recording lengths, and unexpected stops when windows are minimized. Microsoft has not yet published a formal Known Issue for these quirks, but community reports suggest that users should thoroughly test the feature in their specific scenarios—presentation recordings, multi‑monitor setups, and application overlay situations—before relying on it for critical work.

Subtle UI Polish Across File Explorer and Taskbar

Build 26200.5761 includes a series of small visual tweaks that collectively improve the feel of Windows 11. The most visible change appears in File Explorer’s “Open with” context menu, where the accent‑colored backplate behind packaged‑app icons has been removed. Icons are now larger, unadorned, and more legible across light and dark themes, reducing visual noise during routine file operations. Related work includes dark‑mode color fixes and reliability improvements for the Home view.

On the taskbar, hover animations for app groups have been smoothed out. A regression that prevented some pinned apps from unpinning correctly is now addressed, and Start menu layout inconsistencies that crept into earlier 26200 builds have been corrected. These may sound like footnote items, but over long work sessions, micro‑stutters in shell animations and minor layout glitches chip away at perceived performance. The cumulative effect of these fixes is a desktop that feels more responsive and intentional.

Reliability Work Targets DWM, Live Captions, and Copilot Crashes

Under the hood, the build bundles targeted fixes for three areas that have been problematic in the fast‑moving Dev Channel:
- DWM crashes and rendering instability – Desktop Window Manager crashes could manifest as transient black screens, flickering, or compositing failures. The fixes aim to stabilize the graphics stack.
- Live Captions crashes on Copilot+ PCs – Users running live translation on NPU‑enabled devices reported intermittent crashes. This update addresses those regressions.
- Click to Do crash regressions – As mentioned, several crash paths introduced in prior flights have been corrected.

The focus is clear: reduce the instability inherent in rapid iteration. For Insiders who use these builds as daily drivers, fewer unexplained shell restarts translate directly to higher productivity.

Known Issues That Refuse to Die

Despite the polish, Build 26200.5761 carries forward a set of persistent known issues that demand attention before installation:
- Install rollback with error 0x80070005 – Some upgraders encounter this permissions‑style error, causing the update to revert. Microsoft recommends navigating to Settings > System > Recovery > “Fix issues using Windows Update” as an immediate remediation, but no permanent fix has been issued yet. Lab managers and IT pros should postpone Dev Channel adoption on critical machines until this is resolved.
- Visual Studio/WPF crashes on Arm64 – Developers using Arm64 devices report that Visual Studio crashes in WPF‑dependent scenarios after recent Dev flights. Microsoft acknowledges the issue; in the meantime, developers on the Arm64 platform should validate their toolchains in isolated test environments before rolling out broadly.
- Xbox controller Bluetooth bugchecks – A subset of machines with Xbox wireless controllers connected via Bluetooth may trigger system bugchecks. This is under investigation and appears hardware‑ or firmware‑dependent.
- Recall behavior in the EEA – The snapshot feature (Recall) exhibits region‑specific quirks in the European Economic Area, though details remain vague in official notes.
- Snipping Tool edge cases – As noted, window‑mode recording can produce odd behavior with overlays, minimization, and multi‑monitor spanning.

These are not one‑off anomalies; they represent the kind of platform‑specific fragility that is par for the course in Dev Channel builds. The guidance remains consistent: snapshot or image test devices before installing, use segmented pilot rings, and maintain documented rollback paths.

KB Mapping Ambiguity: A Word of Caution for IT Administrators

Community archives have occasionally mapped KB5064093 to Build 26120.5761 (Beta Channel) in some reporting, while other sources correctly associate the same KB label with the 26200‑series Dev Channel flight arriving in the same distribution window. This discrepancy can confuse administrators who track exact KB‑to‑build relationships for change control. Microsoft’s official documentation for KB5064093 explicitly ties it to Build 26200.5761 in the Dev Channel, but the parallel existence of similarly numbered Beta builds underscores the need to verify against the Microsoft Update Catalog or official KB articles before deploying any update to production images. Community‑sourced mappings should be treated as provisional until confirmed by an authoritative source.

Enterprise and IT Guidance: Evaluation‑Only at This Stage

For organizations, Dev Channel builds remain strictly evaluation‑only, suitable for lab and pilot environments. Build 26200.5761 introduces no new servicing stack or security hardening that would warrant production deployment, but it does deliver the new Group Policy and MDM CSP options for removing selected built‑in Store apps—an improvement for Enterprise and Education image hygiene. IT admins preparing test plans should include:

  • Backup and snapshot strategy: Create full VM snapshots or disk images before upgrading. Keep documented restore procedures handy.
  • Developer tool validation: Test Visual Studio, WPF workflows, and build/CI pipelines on both x64 and Arm64 targets.
  • Feature gating awareness: Do not assume uniform behavior across a fleet; controlled feature rollouts mean some devices will see new features while others will not.
  • Peripheral and media testing: Validate Bluetooth Xbox controllers, external monitors, and live‑translation workflows that have surfaced as fragile in recent flights.
  • Policy configuration: Incorporate the new Store‑app removal policies into provisioning images where appropriate to reduce bloat and attack surface.
  • Help‑desk preparation: Arm frontline staff with knowledge of rollback error 0x80070005 and Snipping Tool recording quirks so they can triage Insider‑related calls quickly.

Strengths: Where Microsoft Is Hitting the Mark

Build 26200.5761 exemplifies the approach Microsoft has taken with Windows 11’s Dev Channel over the past year: focused, iterative refinement over flashy overhauls. The strengths are tangible:
- User‑visible polish that compounds: Small UI tweaks—icon legibility, animation smoothing, context‑menu clarity—reduce daily friction for both power and casual users. These changes are simple to implement but improve overall perception of quality.
- Productivity‑first AI ergonomics: The expanded Click to Do selection modes reflect a pragmatic understanding that AI workflows need humble input affordances before they become magical. Freeform lasso and Ctrl+Click multi‑select make the assistant genuinely more useful on touch and pen devices.
- Enterprise‑friendly controls: The ability to remove built‑in Store apps via Group Policy or MDM CSP addresses long‑standing requests from managed environments and helps curb unwanted software drift.
- Incremental stability work: Fixes targeting DWM, Live Captions, and Click to Do regressions directly address pain points introduced by rapid iteration. This balancing act between feature velocity and reliability is critical for maintaining Insider engagement.

Risks and Open Questions

The build also carries several risks and unresolved concerns that should give Insiders and IT managers pause:
- Channel volatility: The presence of an install rollback error and platform‑specific crashes (Arm64 Visual Studio, Xbox Bluetooth bugchecks) underscores the experimental nature of Dev builds. They are not intended for stability‑sensitive environments.
- Hardware gating complexity: Copilot+ features remain a two‑tier experience. Without an NPU‑enabled device, users cannot access on‑device AI processing for Click to Do actions, creating a perception gap even among Insiders on the same build.
- KB mapping confusion: The recurring ambiguity around KB numbers and channel assignments complicates change control for administrators who track update compliance via KB artifacts.
- Incomplete AI privacy documentation: While Microsoft has publicly emphasized on‑device processing for certain Copilot+ capabilities, technical details around telemetry, encryption, and cloud fallback behavior are not yet detailed in preview notes. Enterprises handling sensitive data should treat AI‑assisted workflows with extra caution until explicit documentation is published.

What to Watch Next

Looking ahead, several threads from this release will likely evolve in subsequent Dev Channel flights:
- Widening Click to Do and Recall availability – As staged rollouts expand, more Insiders will see these features, and Microsoft will hopefully clarify which actions run locally versus in the cloud.
- Snipping Tool maturation – Expect iterative bugfixes for the window‑mode recording feature as community feedback rolls in, especially around overlay and multi‑monitor behavior.
- Official KB documentation – Microsoft will eventually publish the KB5064093 support article with the definitive build mapping, resolving community confusion for IT change control.
- Arm64 and peripheral stability – Continued fixes for Visual Studio/WPF on Arm64 and Xbox Bluetooth controller bugchecks will be critical for developers and gamers who use Windows on diverse hardware.

Conclusion

Windows 11 Insider Preview Build 26200.5761 is a textbook example of how Microsoft now iterates on Windows: a compact, cumulative update that prioritizes productivity polish and AI‑assisted interaction while maintaining the experimental character of the Dev Channel. For Insiders and power users, the build delivers meaningful improvements—especially the Click to Do selection ergonomics and the Snipping Tool window‑recording enhancement—but it does so alongside installation rollbacks, hardware‑gated behaviors, and device‑specific regressions. Enterprise IT teams should confine testing to isolated lab rings, snapshot everything, and wait for clearer KB documentation before formal evaluations. The 26200 series continues to inch Windows 11 toward a more AI‑aware, device‑aware future, but that path runs through sandboxes, not production floors.