Windows 11 Insider Build 26200.5751 Delivers Freeform Selection and App-Window Recording

Microsoft rolled out Windows 11 Insider Preview Build 26200.5751 (KB5064071) to the Dev Channel on August 15, 2025, unleashing a set of AI-powered selection and recording tools that blur the line between mouse and touch workflows. The update arrives as Redmond accelerates its push into Copilot-powered experiences, with gestures like freeform capture and app-window recording now baked directly into the OS.

Click to Do Gains Three New Selection Modes

Click to Do—Microsoft’s in-OS surface for extracting, summarizing, and acting on content—gets a significant interaction upgrade. The build introduces Freeform Selection, Rectangle Selection, and Ctrl+Click multi-select, broadening the ways users can group mixed content.

Freeform Selection lets you draw an arbitrary lasso with a pen or finger to capture text chunks, images, and UI elements in one fluid motion. Rectangle Selection works as expected: click and drag a box, and every entity inside becomes actionable. Ctrl+Click, meanwhile, enables keyboard-and-mouse users to cherry-pick disparate bits—a snippet of an email, a chart image, a code block—with surgical precision.

These additions address a long-standing friction point for knowledge workers. Before, Click to Do’s selectable regions were limited, making it tedious to assemble context from multiple visual sources. Now, a support engineer can lasso an error dialog and a log excerpt, then ask Copilot to analyze both in a single query. The productivity lift is tangible, but IT teams should note a few caveats.

Microsoft confirms that some accessibility features aren’t fully baked for preview features like Click to Do. Enterprises with accessibility testing mandates should run focused validation before piloting broadly. Additionally, data governance flags remain: when Click to Do routes selections to cloud-based Copilot models, admins need to confirm whether content is processed locally or shipped off-device. Microsoft’s historical approach has been to limit AI processing by hardware and region, so policies should be updated accordingly.

Snipping Tool’s Window-Mode Recording Ships

The other headline feature is a new recording mode inside Snipping Tool (version 11.2507.14.0 and higher). Toggling the “Window” option in the recording area dropdown snaps the capture region to the bounds of a chosen app window. Press record, and the tool grabs everything inside that rectangle—great for demos or instructional videos.

But there’s a catch: the recording region is fixed. If you drag the window across the screen, the capture stays glued to the original coordinates, leaving a black void. Microsoft’s blog acknowledges the limitation, and community testers have noted edge cases where overlay dimming behaves erratically or recordings cut short. For IT pros building automated screencasting pipelines, treat this as preview-grade and keep OBS as a fallback.

Despite the rough edges, window-mode recording is a natural evolution. Power users who’ve cobbled together third-party tools for app-only captures will welcome the native integration. Combined with the color picker that recently hit the app (which identifies HEX, RGB, or HSL values anywhere on screen), Snipping Tool is inching toward being a Swiss Army knife for visual content.

The Broader AI Wave: Context from Windows Central

While build 26200.5751 focuses on selection and recording, Microsoft is simultaneously flooding the channel with a raft of Copilot+ PC features. Windows Central’s coverage highlights several additions that, while not tied to this specific build, paint the bigger picture of where Windows is headed.

Copilot+ PCs—currently those with Snapdragon X processors—get an AI agent in Settings that understands natural language commands (“turn on quiet hours,” “connect my Bluetooth headset”). Click to Do itself will soon sprout new actions: Practice in Reading Coach, Read with Immersive Reader, and Draft with Copilot in Word, along with Microsoft Teams integration. Snipping Tool on Copilot+ machines can produce “perfect screenshots” using AI to cleanly select content, a feature that Windows Central’s Sean Endicott called “the first tool that makes me feel like I’m missing out by not having a Copilot+ PC.”

Other exclusives include Relight in Photos (add virtual light sources), a sticker generator in Paint, and Copilot Vision, which watches your screen and offers contextual advice. Vision is free within Edge but requires a $20/month Copilot Pro subscription for other apps—a detail that will matter in budgeting discussions.

Quick machine recovery, which Microsoft boasts can fix issues after unexpected restarts and reduce the Blue Screen of Death to a two-second flash, is also on the docket. All these features are rolling out gradually via Controlled Feature Rollout (CFR), so even Insiders won’t see them all at once.

The takeaway for IT planners: the Copilot+ PC ecosystem is fragmenting rapidly. Snapdragon devices get first crack at many AI tools, while AMD and Intel-based Copilot+ systems lag behind. Organizations evaluating a fleet refresh should factor in this staggered delivery schedule.

Enterprise and IT Administrator Notes

Beyond the shiny features, the build includes a critical policy change: enterprises and education customers can now remove select preinstalled Microsoft Store apps via Group Policy or MDM CSP. This gives admins more control over bloatware without resorting to custom images. The exact list of removable apps lives in a separate KB article, so reference it when updating provisioning packages.

Microsoft is explicit that Dev Channel builds are experimental and built on the Windows 11, version 25H2 enablement package. Features can vanish or mutate, so treat this channel as a sandbox. The recommended rollout rings:

• Ring 0 (lab): technicians validate imaging, sysprep, and drivers.
• Ring 1 (developers): test Click to Do, Snipping Tool, and Copilot flows, with special attention to Visual Studio WPF on Arm64.
• Ring 2 (small business group): UX validation of taskbar, Start, File Explorer changes.
• Ring 3 (broader internal): wait for stabilization.

WSUS, Configuration Manager, and Intune admins should isolate Dev builds in a separate pilot channel and never push them through standard production servicing. VM snapshots and system image restores are non-negotiable safety nets.

Fixes and Known Issues: The Operational Reality

The build patches several regressions, including Click to Do crashes from the previous flight (26200.5742), taskbar apps being mysteriously unpinned after updates, and DWM crashes that plagued heavy UI sessions. These are quality-of-life wins for Insiders who stuck with the Dev stream.

However, the known-issues list is long enough to give pause:

• 0x80070005 rollback: Some machines see the update fail and roll back with this error. Microsoft suggests running the recovery fixer at Settings > System > Recovery > “Fix issues using Windows update.” If that doesn’t stick, fall back to system image restore.
• Visual Studio crashes on Arm64 with WPF: Developers on Surface Pro X or other Arm64 hardware who rely on WPF workflows should block the update until Microsoft delivers a fix. Stock crash dump collection is advised for those reporting through Feedback Hub.
• Xbox controller bugchecks: Pairing an Xbox controller over Bluetooth may trigger a blue screen. The workaround is to uninstall the oemXXX.inf (XboxGameControllerDriver.inf) driver via Device Manager (View > Devices by driver). Fleet managers should distribute this procedure or delay the build for gaming-adjacent workstations.
• Recall breaks for EEA Insiders: European Economic Area users might find Recall unresponsive. A reset under Settings > Privacy & security > Recall & snapshots > Advanced settings typically resolves it.
• File Explorer quirks: The Shared section appears but remains empty; temporary file scans may hang. These are cosmetic or performance annoyances rather than blockers, but feedback via the Hub is encouraged.

A practical mitigation summary:

Should You Install This Build?

For production machines, the answer is a hard no. Dev Channel flights are meant for testing and feedback; they can and do break critical workflows. The laundry list of known issues, from update rollbacks to developer tool crashes, reinforces that risk.

For pilot rings, however, this build offers a meaningful advance in daily productivity tools. The Click to Do selection modes, once hardened, could become a power-user staple. Snipping Tool’s window recording, while imperfect, finally provides a first-party solution for app demos—something that’s been missing since the old Problem Steps Recorder. Enterprises that can stomach the instability will gain early visibility into the AI-enhanced Windows interface that will eventually land in 24H2 or later releases.

The Road Ahead

This build is a snapshot of Microsoft’s dual-track strategy: infuse classic in-box apps (Snipping Tool, Paint, Photos) with AI smarts while layering a new interaction paradigm (Click to Do, Copilot Vision) atop the desktop. The staggered rollout—Snapdragon first, then AMD/Intel, with CFR gating—means IT teams must become comfortable with asynchronous feature delivery, a far cry from the monolithic service packs of old.

For the immediate term, test Click to Do’s new selection modes on pen and touch hardware, validate Snipping Tool recordings under various GPU drivers, and brace for a crash or two if you’re on Arm64. Keep a VM snapshot handy, and file feedback aggressively. The promise of a seamlessly intelligent desktop is compelling, but as this Dev Channel build shows, we’re still very much in the bumpy “insider” phase.