Microsoft has released Windows 11 Insider Preview Build 26120.5761 (KB5064093) to the Beta Channel, a targeted quality-and-polish update for Windows 11, version 24H2 that layers a handful of incremental features, Copilot-era refinements, and several important fixes — while continuing Microsoft’s staged “Controlled Feature Rollout” approach that will enable many items only for sampled Insiders.
Microsoft’s Beta Channel for Windows Insiders now maps to the Windows 11, version 24H2 servicing stream (the 26120.xxxx enablement series). Updates published to this track are intentionally incremental: they combine broad stability fixes with gradual rollouts of experimental features that may be toggled on per-device via Microsoft’s staged feature flags. This model aims to gather telemetry and limit regressions, but it also means that two identical PCs on the same build can behave differently depending on whether the new experiences have been enabled for that device.
This build continues work on three long-term priorities for Windows:
Key practical notes:
Why this matters: Click to Do is a core productivity surface for quick context-aware actions (summarize, extract, describe) and Microsoft is optimizing selection and entry points for pen- and touch-first workflows. Independent reporting and community threads show Microsoft is iterating rapidly here and prioritizing ergonomics on hybrid devices.
Independent technology coverage and analyst write-ups reinforce the point: Copilot+ is a hardware-and-software co-design story. The 40+ TOPS requirement distinguishes devices that can run heavier on-device models (Live Captions, Recall, Auto SR, full Windows Studio Effects) from legacy or non‑NPU machines that must rely on cloud processing or reduced functionality. This is crucial for IT planners and power users evaluating whether to buy new Copilot+ hardware or to expect limited local AI functionality on current devices. (itpro.com, wired.com)
For Insiders: try the update on a non-critical device, validate your peripherals (especially Bluetooth controllers), and toggle the “get the latest updates” option if you want earlier staged feature exposure. For IT teams: plan Copilot+ procurement only after verifying hardware compatibility and evaluate whether on‑device AI capabilities are business-critical before committing to broad refresh cycles. The Beta Channel remains the place to watch how Microsoft stitches small, practical improvements together — but it’s also the place to expect the occasional regression while that stitching happens. (blogs.windows.com, microsoft.com)
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5761 (Beta Channel)
Microsoft’s Beta Channel for Windows Insiders now maps to the Windows 11, version 24H2 servicing stream (the 26120.xxxx enablement series). Updates published to this track are intentionally incremental: they combine broad stability fixes with gradual rollouts of experimental features that may be toggled on per-device via Microsoft’s staged feature flags. This model aims to gather telemetry and limit regressions, but it also means that two identical PCs on the same build can behave differently depending on whether the new experiences have been enabled for that device. This build continues work on three long-term priorities for Windows:
- Integrating Copilot-era workflows (Click to Do, Agent in Settings, Recall) and device-level AI experiences for Copilot+ PCs.
- Improving cross-device continuity for Android-to-PC handoff and media resume scenarios.
- Polishing visual and accessibility rough edges while addressing several stability regressions reported by Insiders.
What’s in Build 26120.5761 (KB5064093)
The official release notes list a mix of small new features, tweaks to Copilot-adjacent surfaces, Snipping Tool improvements, input shortcuts, and several fixes and known issues. Below is a functional summary of the most relevant changes and how they land in practice.Cross-device resume for Android apps (initially Spotify)
Microsoft is beginning a gradual rollout that lets Windows 11 PCs resume activity started on an Android phone: the first-capability surfaced in this build is resume playback from Spotify. When Spotify is playing on the phone, a “Resume” alert may appear on the PC taskbar; clicking it opens (or installs) Spotify on the PC and continues playback from the same spot. The experience requires the same Spotify account on both devices, Link to Windows on Android, and the PC to have “Allow this PC to access your mobile devices” enabled. Microsoft’s post explains the setup steps in detail.Key practical notes:
- The feature is rolling out gradually and will not appear for all Insiders immediately.
- If Spotify is not installed on the PC, clicking the Resume alert triggers a one‑click Microsoft Store install and then opens the app.
- Microsoft invites developers to integrate Resume into their Android apps; the platform-level API is documented for app makers. Expect additional apps to adopt the capability over time as developers add integration. Independent coverage reiterates this cross-device continuity direction as a recurring theme in midsummer Insider updates.
Click to Do (Preview) and Copilot+ interactions
Click to Do continues to be refined for touch, pen, and mixed‑input workflows on Copilot+ PCs. This build introduces new touch invocation gestures (press-and-hold with two fingers to launch Click to Do and select the entity under the fingers) and deeper agent navigation links inside Settings for Copilot+ devices. Many Click to Do enhancements are tied to Copilot+ hardware and staged rollout toggles; expect behavior to vary by device.Why this matters: Click to Do is a core productivity surface for quick context-aware actions (summarize, extract, describe) and Microsoft is optimizing selection and entry points for pen- and touch-first workflows. Independent reporting and community threads show Microsoft is iterating rapidly here and prioritizing ergonomics on hybrid devices.
Agent in Settings, Automatic Super Resolution, and other AI polish
- Agent in Settings: better navigation from natural language query results directly to the relevant Settings pages on Copilot+ PCs.
- Automatic Super Resolution (Auto SR) on Snapdragon Copilot+ devices: simplified controls and toast-driven configuration options for on-device super-resolution.
Snipping Tool: window-mode screen recording
Snipping Tool receives a useful update: a window-mode recorder lets you pick a single app window as the recording target. The recording region snaps to the selected window’s bounds; once recording starts, the region remains fixed and will not follow the app if it moves. The update is rolling out to Beta and Release Preview Insiders via the Snipping Tool app update (version 11.2507.14.0+).Lock screen battery icons and input shortcuts
- New battery iconography and battery percentage on the lock screen: a visual polish designed for faster at-a-glance status.
- New keyboard shortcut for en dash and em dash: WIN + Minus inserts an en dash (–) and WIN + Shift + Minus inserts an em dash (—). Note: WIN + Minus remains Magnifier zoom-out when Magnifier is active.
Windows Share pinning and File Explorer UI polish
- Windows Share now experiments with pinning favorite apps for quicker sharing.
- File Explorer context menu “Open with” icon backplates are being removed so icons appear larger and clearer in the list — a small multi-theme visual polish.
Fixes and known issues to watch
Microsoft published several targeted fixes alongside a list of known problems customers should consider before installing:- Recall: Insiders in the European Economic Area (EEA) may see Recall stop working; Microsoft provides a Reset Recall instructions under Settings to recover.
- File Explorer: “Shared” section may show empty content for some users.
- Xbox controller Bluetooth bugcheck: some Insiders have reported system crash (bugcheck) when using Xbox controllers via Bluetooth. Microsoft documents a Device Manager workaround (uninstalling the oemXXX.inf XboxGameControllerDriver.inf) but the presence of a bugcheck class issue makes this a severe stability concern for users dependent on Bluetooth controllers.
- General installation caveats: earlier 26120-series flights experienced rollbacks with error 0x80070005 for a subset of Insiders; Microsoft has previously suggested using Settings > System > Recovery > “Fix issues using Windows Update” as a remediation step. Community reporting continues to surface install rollback incidents on some hardware.
The Copilot+ PC context: why hardware matters
A recurring theme across recent Beta/Dev Channel updates — and explicitly referenced by Microsoft — is that several of the newer AI features depend on Copilot+ PC hardware. Microsoft’s Copilot+ PC guidance requires devices to include an NPU capable of 40+ TOPS (trillion operations per second), along with a baseline of RAM and storage (16 GB RAM, 256 GB SSD as a typical minimum) for the full on-device AI experience. These hardware requirements mean that a significant portion of existing PCs will see degraded or absent local AI behaviors unless they meet the Copilot+ spec. (microsoft.com, prod.support.services.microsoft.com)Independent technology coverage and analyst write-ups reinforce the point: Copilot+ is a hardware-and-software co-design story. The 40+ TOPS requirement distinguishes devices that can run heavier on-device models (Live Captions, Recall, Auto SR, full Windows Studio Effects) from legacy or non‑NPU machines that must rely on cloud processing or reduced functionality. This is crucial for IT planners and power users evaluating whether to buy new Copilot+ hardware or to expect limited local AI functionality on current devices. (itpro.com, wired.com)
Critical analysis — strengths, trade-offs, and risks
Strengths and positive signals
- Focused quality work: Build 26120.5761 is polish-first, addressing well-worn friction points (File Explorer polish, battery icon clarity, Snipping Tool improvements) while progressively enabling higher-value features. That approach reduces surprise regressions while adding measurable daily-use benefits.
- Cross-device continuity: The Android-to-PC resume flow (starting with Spotify) is a practical extension of Microsoft’s mobile-to-PC surface; if it scales to other apps it will be genuinely useful for media, navigation, and productivity continuity.
- Copilot+ platform maturation: Agent-in-Settings refinements, Auto SR controls, and Click to Do improvements point to Microsoft iterating on discoverability and ergonomics rather than purely adding more features. This attention to human factors suggests readiness for broader, enterprise-aware rollouts once stability is assured. (blogs.windows.com, windowscentral.com)
Trade-offs and risks
- Staged enablement means fragmentation. Two machines on the same build can present different UIs and functionality depending on flight flags. That reduces predictability for testers and admins and complicates support and automation. File-search community analysis and Microsoft’s notes explicitly describe this behavior as a design choice to reduce regression blast radius — but it’s a support headache for IT teams.
- Hardware gating for Copilot+ features effectively creates two classes of Windows 11 experience: full on-device AI on 40+ TOPS NPUs versus degraded/cloud-dependent behavior elsewhere. That will slow enterprise-wide adoption unless organizations account for the upgrade cycle. Independent analyses and Microsoft documentation both stress this hardware divide. (microsoft.com, pcworld.com)
- Stability and peripheral risks remain real. The documented Xbox controller Bluetooth bugcheck is a severe issue for users relying on controller input; the prior appearance of 0x80070005 install rollbacks on the 26120 track highlights that Beta builds still carry risk for day-to-day productivity if installed on primary machines. Community threads corroborate rollback reports.
Privacy / compliance considerations
- Recall (preview) is regionally controlled and has raised privacy questions since its early previews. Microsoft’s staging of Recall and the EEA-specific reset guidance reflect continued caution but also mean administrators must evaluate data retention, indexing scope, and enterprise policy controls before enabling Recall on managed devices. Treat Recall as a preview capability not yet ready for broad enterprise deployment without policy review. (blogs.windows.com, microsoft.com)
Unverifiable or future-facing claims (flagged)
- Broader app support for Resume beyond Spotify is plausible and explicitly invited by Microsoft (developer docs exist) — but the timeline and list of apps that will actually implement Resume are not yet verifiable. Consider any statements that suggest an immediate, wide app rollout as speculative until developers publicly confirm integration.
Guidance for Insiders, IT pros, and power users
If you’re an Insider on a personal device
- Decide whether your machine is a spare/test device or a daily driver. Beta Channel installs are moderately stable but still have real regressions (rollback, bugchecks).
- If you want to try the new Resume-Spotify flow: enable Settings > Bluetooth & devices > Mobile devices > Allow this PC to access your mobile devices, pair your Android phone with Link to Windows, and play Spotify on your phone to watch for the Resume alert on the taskbar. The experience will appear only if the staged feature has been enabled for your device.
- Don’t enable Beta on mission-critical hardware if you rely on Bluetooth Xbox controllers or have heavy automation tied to specific UI behaviors. If you do encounter the Xbox controller bugcheck, Microsoft documents a manual driver uninstall workaround via Device Manager.
If you manage Windows for an organization
- Treat Build 26120.5761 as a preview-quality checkpoint. Validate key workflows (automation scripts, UI-scraping, assistive technology compatibility) on representative hardware before broad distribution. Staged flags may mean that the same build behaves differently across a test fleet — plan accordingly.
- For Copilot+ planning: if your organization expects on-device AI features (Recall, Auto SR, full Studio Effects), procure hardware that meets Microsoft’s Copilot+ spec (40+ TOPS NPU, 16 GB RAM, 256 GB storage) or expect to rely on cloud‑backed alternatives that may introduce latency or additional licensing requirements. (prod.support.services.microsoft.com, microsoft.com)
- Include rollback and recovery procedures in your test plan. Previous 26120-series installs reported 0x80070005 rollbacks for a proportion of devices; make sure IT helpdesk scripts include the “Fix issues using Windows Update” Recovery path Microsoft recommends.
The small but important details IT and power users will want to know
- KB/Build identifiers: the update is published as Build 26120.5761 and packaged under KB5064093 in the Beta Channel release post. This is the precise designation to match update catalog entries or WSUS records.
- Snipping Tool behavior: window-mode recordings fix the capture region at start time; recordings will not follow a moved window. That design choice simplifies capture but limits dynamic recording of moving apps.
- Input shortcut caveat: WIN + Minus for en dash will conflict with Magnifier zoom out if Magnifier is active; the behavior is intentional but may surprise users.
- Controlled Feature Rollout toggle: Insiders who want earlier access to staged features should toggle on “Get the latest updates as they are available” in Settings > Windows Update; otherwise staged items will reach devices over time as Microsoft ramps them.
Broader implications and what to watch next
- Continued convergence on Copilot+ hardware: Microsoft’s insistence on 40+ TOPS NPUs for many experiences signals the company’s strategy to build Windows features that assume a baseline of on-device AI capability. Watch OEM availability and pricing of Copilot+ certified devices — enterprise procurement cycles will dictate adoption pace. (microsoft.com, pcworld.com)
- Drain on compatibility testing: the feature-gating and staged enablement model expedites iterative improvement, but increases the burden for ISVs and enterprise testers who must validate functionality across both staged and non-staged environments. Expect more incremental compatibility advisories in the months ahead. Community observations and forum threads have already highlighted this testing complexity across the 26120 series.
- Incremental UX wins vs. fragmentation: small visual and interaction improvements (File Explorer icon polish, lock screen battery icons) add polish, but the staged delivery mechanism can produce inconsistent experiences that feel unfinished to users who see partial changes (dark chrome in file dialogs in some cases, but legacy light buttons elsewhere). The risk: perceived regression even when the underlying aim is cautious rollout.
Conclusion
Build 26120.5761 (KB5064093) is emblematic of Microsoft’s current Insider-era posture: controlled, iterative polishing that nudges Windows 11 forward on cross-device continuity and Copilot-era ergonomics while remaining conservative about mass enablement. The arrival of Android-to-PC resume for apps (starting with Spotify), Snipping Tool window-mode recording, Click to Do refinement, and agent-driven Settings navigation are meaningful incremental wins for hybrid and touch-first users. However, the update also underlines two persistent realities: important AI features are being gated behind Copilot+ hardware (40+ TOPS NPUs), and staged rollouts — while safer — introduce fragmentation and testing complexity for users and admins.For Insiders: try the update on a non-critical device, validate your peripherals (especially Bluetooth controllers), and toggle the “get the latest updates” option if you want earlier staged feature exposure. For IT teams: plan Copilot+ procurement only after verifying hardware compatibility and evaluate whether on‑device AI capabilities are business-critical before committing to broad refresh cycles. The Beta Channel remains the place to watch how Microsoft stitches small, practical improvements together — but it’s also the place to expect the occasional regression while that stitching happens. (blogs.windows.com, microsoft.com)
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5761 (Beta Channel)