Microsoft rolled out Windows 11 Insider Preview Build 26200.5751 (KB5064071) to the Dev Channel on August 15, 2025, packing a modest but meaningful set of improvements: Copilot-era selection tools for Click to Do, visual refinements across File Explorer and the taskbar, an enterprise store-app removal policy, and a bundle of stability fixes. The update also brings window-mode screen recording to the Snipping Tool for Insiders, though it lands as a separate app update rather than part of the cumulative build. As with any Dev Channel flight, the feature rollout is staggered—some functions require toggling “Get the latest updates as soon as they’re available” in Settings, while others remain gated by Copilot+ PC hardware or regional availability.
Click to Do, the on-screen productivity assistant exclusive to Copilot+ PCs, gains three new selection modes aimed at making mixed-content capture faster and more natural. Freeform Selection lets you draw arbitrary shapes with pen or touch to grab any on-screen entities. Rectangle Selection restores the classic marquee for rectangular regions. Ctrl + Click enables multi-select of disparate items via keyboard and mouse. These additions directly target users who frequently extract text, images, or hybrid content from documents, web pages, or presentations, reducing the need to switch between capture tools. The official announcement blog highlights the modes as part of a broader push to make AI-powered screen interactions more context-aware, though such features remain tethered to Copilot+ hardware and are not available on all devices.
File Explorer receives a subtle but welcome visual polish. The “Open with” context menu no longer shows accent-colored backplates behind packaged-app icons. Instead, the icons appear larger and without a colored background, improving legibility in both light and dark themes. Taskbar and system tray animations have been refined, particularly the hover behavior for app groups. These micro-interactions make the multitasking flow feel smoother without fundamentally altering the taskbar’s functionality.
The Snipping Tool update mentioned in the build notes is actually delivered through the Microsoft Store, independent of the OS cumulative update. It introduces window-mode screen recording, allowing Insiders to select a specific application window and record only that region. This targeted recording avoids the need to crop footage after capture and is especially handy for tutorial creators or support personnel. The tool sizes the recording area to match the selected window, eliminating guesswork.
IT admins gain a notable enterprise control: the ability to remove select pre-installed Microsoft Store apps on Enterprise and Education devices using Group Policy or MDM CSP. Microsoft has published a KB article detailing the implementation, which lets administrators slim down fleet images by stripping unwanted apps—such as consumer-facing utilities or promotional content—that are otherwise baked into the OS. This move addresses a long-standing pain point for managed environments where bloatware removal required complex scripting or third-party tools.
The build addresses a swath of reliability issues uncovered in earlier flights. Taskbar fixes resolve duplicate clock and tooltip displays when additional clocks are enabled. Start menu corrections prevent a layout regression that caused temporary shrinking, improve safe-mode launch behavior, and fix contextual menu positioning. File Explorer’s dark mode color glitches, including low-space indicator hues, have been corrected. Login and lock screen stability is bolstered, and an issue causing blank icons for certain authentication options is squashed. Live captions on Copilot+ PCs no longer crash during live translation, and DWM (Desktop Window Manager) crash frequency has been reduced. Click to Do itself gets a regression fix where text and image actions could fail or cause crashes after previous flights.
Before updating, Insiders and IT evaluators should weigh several known issues. Some devices may encounter a rollback during installation with error 0x80070005 via Windows Update. Microsoft is actively investigating and suggests using Settings > System > Recovery > “Fix issues using Windows update” as a workaround. Arm64 PCs face a potential showstopper: Visual Studio may crash in WPF-dependent scenarios following recent Dev builds. Developers relying on WPF-heavy workloads should avoid this flight on Arm64 until a fix is confirmed. The Recall feature (Copilot’s snapshot timeline) may misbehave on EEA Insiders, though a Settings reset path is available. Lingering quirks like File Explorer’s Shared view not rendering correctly, Settings scanning stuck on Temporary files, and Xbox controller Bluetooth bugchecks remain in the flight notes.
These caveats underscore the Dev Channel’s nature as a fast-feedback loop where features often arrive via Controlled Feature Rollouts and enablement packages. What lands for one Insider may not reach another immediately, and some experimental features may never ship broadly. The announcements for Build 26200.5751 make explicit that certain AI-powered experiences are tied to Copilot+ certification and specific processors, and that regional availability varies.
For enthusiasts tracking Microsoft’s AI-driven Windows roadmap, Build 26200.5751 signals continued investment in contextual on-device intelligence. Click to Do’s richer selection modes are small but practical pieces of a larger strategy that lets users interact with on-screen content in more nuanced ways before handing it off to Copilot or other assistants. Together with the Snipping Tool’s window recording, they point toward a future where capturing, refining, and acting on screen content happens in fewer steps.
Admins should note the privacy implications. Several intelligent features—especially those performing complex image understanding or text actions—may involve cloud-hosted models or model downloads. While Microsoft documents that some text actions use secure cloud endpoints, the precise data flows and retention policies vary. Organizational privacy guidance and opt-out controls should be reviewed before broadly enabling Copilot-powered features. Assume cloud processing unless Microsoft explicitly declares on-device-only modes.
Instability risks are real. The update rollback bug and Arm64 developer tool crashes highlight the trade-offs of rapid iteration. Organizations using Insider builds for compatibility testing must isolate test hardware and avoid exposing production systems. Device and regional fragmentation further complicate cross-platform QA: Copilot+ exclusives behave differently on Snapdragon vs. x86 Copilot+ SKUs, and some features remain limited to specific markets.
Insiders eager to test the new capabilities should enable the Dev Channel only on dedicated, disposable hardware. Verify that the machine is listed as Copilot-capable if targeting Click to Do or other AI features. For Arm64 developers, stick with Beta or Release Preview channels until Visual Studio/WPF stability is confirmed. If the 0x80070005 rollback strikes, try the Recovery workaround and file Feedback Hub reports with diagnostic logs.
Looking ahead, the Dev Channel cadence suggests weekly or bi-weekly flights through the 25H2 finalization. Expect more discrete app updates—Snipping Tool, Paint, Photos—to arrive via the Microsoft Store independently. Key items to monitor: resolution of the 0x80070005 installation rollback, expansion of Click to Do and Copilot features beyond initial hardware gates, stabilization of developer tooling on Arm64, and more granular privacy documentation clarifying which AI flows are on-device versus cloud-assisted.
Build 26200.5751 is a typical Dev Channel increment: pragmatic UI tune-ups, meaningful AI tooling enhancements, and a batch of targeted fixes. For Windows enthusiasts, it’s a tangible peek at how Copilot-era interactions are being woven into the OS shell. For IT teams, it’s a reminder to plan testing across hardware variants, stay on top of known issues, and treat Dev flights as early warning systems rather than production candidates. Microsoft’s direction is unmistakable—deepen the integration of AI and Copilot experiences while iterating rapidly with Insider feedback. Whether that accelerates user productivity or introduces new friction depends heavily on hardware, region, and the speed at which known issues are resolved.