Microsoft shipped Windows 11 Insider Preview Build 26120.5761 (KB5064093) to the Beta Channel on August 22, delivering a slate of incremental but tangible improvements that span cross-device continuity, on-device AI, and everyday usability. The update is a targeted quality-and-polish release for version 24H2 that doubles down on the Copilot+ hardware story while introducing a long-awaited handoff feature: the ability to resume Spotify playback from an Android phone directly on a Windows 11 PC.

The build lands in the 26120.xxxx enablement series that maps to the 24H2 servicing stream. It exemplifies Microsoft’s controlled feature rollout (CFR) strategy—many of the new capabilities will appear only for a subset of Insiders as the company phases them in. That means two identical machines on the same build can show different feature sets, a design choice that limits regressions but complicates testing and support.

Cross-Device Resume Brings Spotify to the Taskbar

The headline feature is a new cross-device resume flow that lets a Windows 11 PC pick up media playback from an Android phone. In this first iteration, the only supported app is Spotify. When Spotify is playing on a linked Android device, a “Resume” alert may appear on the PC taskbar. Clicking it triggers a one-click install via the Microsoft Store if Spotify isn’t already present, then opens the app and continues playback from the exact point left off on the phone.

Setup requires the same Spotify account on both devices, the Link to Windows app on Android, and the PC setting “Allow this PC to access your mobile devices” enabled under Settings > Bluetooth & devices > Mobile devices. Microsoft has published developer documentation for the underlying API and is actively inviting third-party apps to integrate. While Spotify is the only launch partner, the mechanism is generic—if adoption follows, we could see resume support for navigation, productivity, and messaging apps within months.

Practical testing by Insiders reveals that the resume toast is not yet universally available even for those who meet the prerequisites, consistent with Microsoft’s gradual rollout. The feature is a direct extension of the mobile-to-PC surface Microsoft has been building for years, and it stands to meaningfully reduce friction for users who frequently switch between phone and desktop.

Snipping Tool Gains Window-Mode Recording

Snipping Tool receives a welcome update in this build: window-mode screen recording. The updated app (version 11.2507.14.0 and later) lets users select a single application window as the recording target. The capture region snaps to the window’s bounds and remains fixed once recording begins. If the window is moved, the recorded area stays put—it does not follow the app. This design simplifies capture but may surprise users expecting dynamic tracking.

The improvement arrives alongside the build for Beta and Release Preview Insiders, and it addresses a long-standing request from tutorial creators, developers, and support staff who need to isolate a single window without cropping in post-production.

Copilot+ AI Features Get Incremental Polish

For Copilot+ PCs, Build 26120.5761 doesn’t introduce major new AI capabilities but instead refines discoverability and usability of existing ones.

Click to Do, the on-screen action menu that lets users summarize, extract, and interact with content, now supports new touch invocation gestures. A press-and-hold with two fingers launches Click to Do and automatically selects the entity under the fingers. This is a significant ergonomic improvement for pen- and touch-first workflows on devices like the Surface Pro.

The Settings Agent likewise sees better navigation: natural language queries now route more accurately to the relevant settings page on Copilot+ PCs. And for Snapdragon-powered Copilot+ devices, Automatic Super Resolution (Auto SR) gains simplified controls and toast-based configuration options that make it easier to toggle and understand when the feature is active.

These changes underscore Microsoft’s shift from big-bang feature drops to friction reduction. The underlying on-device models—Recall, Auto SR, Windows Studio Effects—are hardware-gated, requiring an NPU capable of 40+ trillion operations per second (TOPS).

Hardware Gating: The 40 TOPS Divide

Microsoft’s Copilot+ PC specification, detailed on its business devices page, mandates an NPU with at least 40 TOPS, 16 GB of RAM, and a 256 GB SSD. This baseline enables the full suite of on-device AI experiences: Recall snapshots, Live Captions, Auto SR, and advanced Windows Studio Effects.

Recall, still in preview, captures encrypted snapshots of the active screen every few seconds and stores them locally. It uses 25 GB of storage by default on a 256 GB drive—roughly three months of history—and automatically purges the oldest snapshots when the limit is reached. Users can search snapshots via natural language or a timeline, and Click to Do surfaces actions on recognized text and images within those snapshots.

Enterprises evaluating Recall must consider data retention and compliance requirements. Microsoft’s documentation notes that the feature is not yet ready for broad deployment without policy review, particularly in the European Economic Area where regulatory scrutiny is higher.

The 40 TOPS threshold effectively splits the Windows 11 install base into two tiers: full local AI on Copilot+ hardware, and cloud-dependent or feature-limited behavior on older PCs. Independent analysts have pointed out that this hardware requirement will slow enterprise adoption until organizations refresh their fleets, and it leaves many high-end “AI PCs” from 2023—with NPUs in the 10–20 TOPS range—without access to the newest experiences.

Other Usability Improvements

  • Lock screen battery icons: A redesigned battery icon with percentage readout now appears on the lock screen, providing at-a-glance status without signing in.
  • Keyboard shortcuts for dashes: A new system-wide shortcut inserts typographic dashes. WIN + Minus types an en dash (–), and WIN + Shift + Minus types an em dash (—). Note that WIN + Minus still zooms out in Magnifier when the tool is active, so the shortcut conflicts in that scenario.
  • Windows Share pinning: The share dialog experiments with pinning favorite apps for faster access.
  • File Explorer clarity: The “Open with” submenu in the context menu loses its icon backplates, making app icons larger and easier to distinguish in both light and dark themes.

Critical Fixes and Persistent Bugs

Microsoft’s changelog includes several targeted fixes alongside a list of known issues that Insiders should weigh before installing.

  • Recall reset for EEA users: Insiders in the European Economic Area may see Recall stop working. A Settings-based reset option is available as a workaround.
  • File Explorer empty Shared section: Some users may see no content under the Shared tab even when files have been shared.
  • Xbox controller Bluetooth bugcheck: The most severe documented issue is a system crash (bugcheck) when using Xbox controllers over Bluetooth. Microsoft provides a manual driver uninstall workaround via Device Manager (removing the oemXXX.inf XboxGameControllerDriver.inf), but the presence of a bugcheck-class problem is a red flag for users who depend on wireless controllers for gaming or accessible input.
  • Installation rollbacks: Earlier 26120-series builds experienced rollbacks with error 0x80070005 for a subset of hardware. Microsoft previously recommended using Settings > System > Recovery > “Fix issues using Windows Update” as remediation. Community reports suggest the issue may persist in this build, so it’s advisable to have a backup before upgrading a primary machine.

Guidance for Insiders and IT Pros

For individual Insiders, the build is best tested on a spare or secondary device. The Bluetooth controller bugcheck alone is reason enough to avoid installing on a gaming rig or any PC where controller input is critical. To try the Spotify resume flow, ensure both the phone and PC are configured as described, and be prepared that the staged nature of the rollout may delay the feature’s appearance.

IT administrators should treat Build 26120.5761 as a preview-quality checkpoint. Validate automation scripts, UI-scraping tools, and assistive technology compatibility on representative hardware, and remember that staged feature flags can cause different behavior across a test fleet. For Copilot+ planning, procure hardware that meets the spec if on-device AI is a business requirement; otherwise, factor in the latency and licensing implications of cloud-based alternatives. Rollback and recovery procedures must be included in any deployment test plan, with the “Fix issues using Windows Update” path pre-scripted for helpdesk staff.

The Broader Implications

Build 26120.5761 reinforces three long-term trends in Windows development. First, cross-device continuity is moving from a theoretical promise to practical, app-specific integrations, and Spotify serves as a template for what’s to come. Second, Copilot+ is cementing itself as a hardware-software co-design platform that will increasingly define the premium Windows experience, leaving older hardware behind. Third, Microsoft’s controlled feature rollout model—while safer—introduces a testing and support burden that will only grow as more features are staggered across the Insider rings and eventually production.

The small UI polishes—battery icons, dash shortcuts, File Explorer tweaks—may seem minor, but they accumulate into a more refined daily experience. Meanwhile, the bugcheck and rollback issues remind us that Beta Channel builds remain a work in progress. Organizations and power users should stay engaged, test carefully, and plan for the hardware transition that Copilot+ demands.