Windows 11 Beta Build 26120.5761: Cross-Device Resume, Snipping Tool & Copilot+

Microsoft is rolling out Windows 11 Insider Preview Build 26120.5761 (KB5064093) to the Beta Channel for Insiders on Windows 11, version 24H2 — a staged preview that bundles a mix of incremental features, UI tweaks, and fixes while continuing to gate higher‑impact changes behind controlled rollouts and Copilot+ hardware requirements.

Background​

Windows 11, version 24H2 is the current feature baseline for these Beta Channel flights. Microsoft uses the Beta Channel to test servicing and feature delivery for 24H2 via an enablement package model (Build 26120.xxxx), and many capabilities in these previews are rolled out gradually using Controlled Feature Rollout (the “toggle” Insiders can opt into via Settings > Windows Update). That means not every Insider will see every change immediately; Microsoft monitors telemetry and feedback before widening availability.
This August 22, 2025 flight (Build 26120.5761 / KB5064093) is primarily a Beta update for Insiders on 24H2, not a full public servicing release. Microsoft’s blog post lists the build, the KB number, and the set of items being rolled out or staged in this channel. At the time of publication, the blog is the authoritative primary source for the details summarized below.

---

What’s new in Build 26120.5761 (KB5064093)​

This build mixes a handful of gradual rollout features (gated by toggle/telemetry) with a set of fixes and smaller UX changes that Microsoft is pushing to Beta Channel Insiders more broadly. The most notable items in the announcement are:

• Cross‑device Resume for Android apps (initially Spotify) — a taskbar “Resume alert” that lets you continue playback from your Android phone on the desktop Spotify app, including 1‑click install if the app isn’t present on the PC. Microsoft is building a Resume API so third‑party apps can opt in. (blogs.windows.com, windowslatest.com)
• New battery iconography on the lock screen — refreshed battery visuals and percentage display for at‑a‑glance status while the device is locked.
• Snipping Tool: window‑mode screen recording — Snipping Tool is receiving a window pick recording mode so the recorder snaps to a chosen app window and produces MP4 recordings of that fixed region. This feature surfaced in Insider channels previously and is now part of the Beta flight notes. (blogs.windows.com, windowsforum.com)
• Click to Do / Input / Auto Super Resolution (Auto SR) tweaks — Copilot‑adjacent experiences (Click to Do and Auto SR) are iteratively refined, including a new touch invocation for Click to Do on Copilot+ touch PCs and simplified Auto SR controls on Snapdragon Copilot+ devices. (blogs.windows.com, thurrott.com)
• New keyboard shortcuts and small input improvements — Microsoft added shortcuts to insert an en dash (WIN + -) and an em dash (WIN + Shift + -), with a caveat for Magnifier users (WIN + - still controls Magnifier zoom).
• Miscellaneous Settings and reliability fixes — improvements to Settings performance when loading installed apps, Windows Hello face recognition behavior, and gaming overlay performance on multi‑monitor systems. Plus targeted fixes for previously reported Start menu and File Explorer glitches.

Each of these items is being delivered either via the toggle‑gated gradual rollout (so only a subset of Insiders will see the feature immediately) or as part of the general Beta Channel updates that eventually reach all Insiders in the channel.

---

Deep dive: Cross‑Device Resume — what it is and how it works​

Apple Handoff, but for Android and Windows​

Microsoft’s new Resume capability aims to provide a Handoff‑like experience for Android → Windows continuity. The initial scenario calls out Spotify: start playing on an Android phone, unlock your Windows 11 PC, and a Resume alert appears on the taskbar that, when clicked, opens Spotify on the PC and continues playback at the same timestamp. If the desktop app isn’t installed, the alert triggers a one‑click Microsoft Store install and then restores playback after sign‑in. (blogs.windows.com, techspot.com)
Third‑party adoption is core to the plan: Microsoft is exposing a Resume API so apps can opt in and support the experience. Early reporting and leaks previously picked up evidence of toggles for Spotify and WhatsApp support, and pre‑release demos at Build hinted at the capability. Independent coverage by Windows‑focused outlets observed the feature in leaked demos and confirmed Microsoft’s intent to expand Resume beyond OneDrive‑based scenarios. (windowslatest.com, techspot.com)

Setup and practical limits​

Microsoft’s blog documents the setup steps Insiders must follow:

• Enable “Allow this PC to access your mobile devices” under Settings > Bluetooth & devices > Mobile devices.
• Pair and manage the Android phone in the Link to Windows app and permit background operation.
• Play a supported app (e.g., Spotify) on phone; watch for the Resume alert on the taskbar within the timeframe Microsoft permits.

Microsoft warns this will be a gradual rollout, so delays or phased exposure are expected. The feature’s reliance on matching accounts and background permissions means it will work best for users who keep Link to Windows active and grant the necessary background and notification permissions on Android.

Risks, gaps, and privacy considerations​

• Resume requires matching account context (same app account across devices) and background access on the phone. That raises privacy questions if users don’t clearly understand what state is being synchronized or what data is transferred through Microsoft services or vendor APIs.
• Microsoft has emphasized a relatively short time window for resuming activity after switching devices (consistent with prior OneDrive resume behavior). Expect edge cases where resume won’t trigger (device locked for too long, app state not captured, or network/offline scenarios).
• Developers need to opt in for a smooth experience; until major apps adopt the Resume API, the feature will feel limited in day‑to‑day usefulness. Early reporting suggests Microsoft will initially focus on a few high‑value apps (Spotify, WhatsApp) before broadening support. (blogs.windows.com, windowslatest.com)

---

Snipping Tool’s window‑mode recording: practical improvements and limits​

The Snipping Tool’s new window pick recording option is an important quality‑of‑life upgrade for quick demos and app‑specific recordings. Instead of drawing a freeform rectangle, you can click an app window and have the recorder size the capture to that window’s geometry at the start of the recording. This delivers cleaner initial captures and reduces manual cropping post‑recording. (blogs.windows.com, windowsforum.com)
Important details and real‑world caveats:

• The capture area is fixed when recording starts — the recorder does not dynamically follow a moved or resized window. That design simplifies implementation and reduces CPU overhead, but it also means presentations that require moving windows mid‑recording will not be captured perfectly.
• Recordings are produced as MP4 files and can be previewed and trimmed in the app before saving. Early insider testing reports minor multi‑monitor offsets and boundary glitches on some systems; those are typical for newly introduced capture implementations and may be corrected in future flights.
• The Snipping Tool improvements continue Microsoft’s push to make basic content creation available without third‑party tools. For many users, the built‑in recorder already covers common tasks; power users will still rely on specialized software for advanced tracking, multi‑source capture, and editing workflows.

---

Copilot+, Auto SR, and the growing split in Windows features​

Build 26120.5761 continues Microsoft’s approach of differentiating certain AI‑driven and performance features for Copilot+ PCs (devices with specific hardware like Snapdragon X processors). The update includes:

• New touch invocation for Click to Do on Copilot+ touch PCs.
• Streamlined Auto Super Resolution (Auto SR) controls and toast‑based configuration for Snapdragon Copilot+ machines.
• Agent links in Settings that jump directly to relevant settings pages from the agent experience.

These changes underscore Microsoft’s strategy to tie some premium experiences to Copilot+ hardware while still iterating the broader Windows experience for all devices. Reporting from energy and device coverage outlets has tracked this trend: Copilot+ features are optimized heavily for specific silicon and are progressively gated to those devices. (blogs.windows.com, thurrott.com)
Practical point: if you’re an Insider on an Intel/AMD device you may still see certain Copilot features in preview, but full functionality (especially Auto SR performance gains) will be most visible on Copilot+ hardware. (blogs.windows.com, thurrott.com)

---

Fixes, known issues, and reliability notes​

Build 26120.5761 carries a set of fixes and still‑open known issues that Insiders should be aware of:

• Microsoft lists fixes for Settings performance (apps list), Windows Hello face recognition hiccups, and game overlay performance when multiple monitors have different refresh rates.
• Known issues in this flight include residual Recall problems (notably in the EEA where users might need to Reset Recall in Settings to restore the feature), some File Explorer Home “Shared” visibility oddities, and a Storage > Temporary files scanning hang that Microsoft is still working on. Xbox Controller Bluetooth usage causing bugchecks on some systems remains an area of active troubleshooting with documented workarounds.
• The Beta Channel remains a testing ground for servicing technology changes; Microsoft reiterates that some features previewed here may never ship or may change materially. Insiders should expect instability and be prepared to roll back or use recovery options if a flight causes critical problems.

Industry and community reporting has tracked recurring installation and stability problems across several 24H2 preview updates earlier this year, including occasional update rollbacks, black‑screen hangs during update boots, and device‑specific driver interactions. These community signals are useful early warning signs and reinforce the value of staged rollouts and broad user testing before public release. (windowslatest.com, reddit.com)

---

Who should install this build — and how to try the new features​

This build is intended for Windows Insiders in the Beta Channel who are running Windows 11, version 24H2 and who accept the instability and variability that comes with preview software. Specific recommendations:

• Turn on the Beta Channel toggle to receive the latest preview features as the feature gates are opened (Settings > Windows Update > Windows Insider Program > Beta Channel > Turn on “Get the latest updates as they are available”). This increases the odds you’ll be included in the gradual rollouts referenced in Microsoft’s announcement.
• If you want to try the Cross‑Device Resume Spotify scenario, pair your phone using Link to Windows, enable background permissions on the Android app, and keep the same Spotify account signed in on both devices. Expect a taskbar Resume alert if the feature has rolled out to your device. (blogs.windows.com, windowslatest.com)
• For Snipping Tool window‑mode recording: update Snipping Tool to the stated package versions (or wait for the staged rollout), then open Record → New → Recording area → Window mode and click the target window before starting recording. Remember the capture is set at start time and will not follow the window if you move it later. (blogs.windows.com, windowsforum.com)
• Back up critical data and create a system restore point (or full image) before installing Beta Channel cumulative updates. For production devices, avoid Beta builds unless you have an IT‑validated test environment. Community forums and earlier release notes have shown that updates can occasionally cause driver conflicts or boot issues on certain hardware. (windowslatest.com, reddit.com)

---

What to watch next: rollout patterns and the verification gap​

Microsoft’s staged delivery approach means insight into exact rollout timing and global availability is limited. Two operational points to watch:

• Controlled Feature Rollout (toggle) — features listed as “gradually being rolled out with toggle on” may appear for a small subset of toggle‑enabled Insiders at first and expand over weeks. That behavior is intentional and designed to detect problematic interactions before broad exposure.
• KB metadata and support pages — the blog references KB5064093 as the label for this build’s cumulative update. Historically, Microsoft often posts a separate Microsoft Support KB article (with file details and known issues) after or alongside the blog announcement. At the moment of writing, the Windows Insider blog is the authoritative release note for Build 26120.5761; if a standalone Support page for KB5064093 appears later, administrators and IT pros should consult it for file‑level details and download links. If you need to validate exact file versions and SSU dependencies for enterprise deployment, check the Microsoft Update Catalog and the Support site as the canonical follow‑ups. (blogs.windows.com, support.microsoft.com)

Note: If Microsoft does not immediately publish a standalone Support KB article for KB5064093, that is not unusual for preview releases; the blog post is the canonical notification for Insiders. Still, administrators should expect the Support and Update Catalog pages to appear shortly after the initial Insider announcement for completeness.

---

Strengths and strategic implications​

• Meaningful cross‑device continuity — Resume represents a significant push to blur device boundaries for common tasks (music, messaging), and the Spotify example shows Microsoft is targeting high‑utility scenarios that can demonstrate clear value to end users early. This is a logical area for Microsoft to compete with Apple’s Handoff and to deepen Windows + Android interoperability. (blogs.windows.com, techspot.com)
• Incremental UX polish — iconography refinements (battery on lock screen), input niceties (dash shortcuts), and Snipping Tool improvements are incremental but cumulatively improve day‑to‑day usability across many users. These are the kinds of changes that improve perception even when they’re not headline features. (blogs.windows.com, windowsforum.com)
• Schism between device classes — the Copilot+ hardware tie‑ins and Auto SR optimizations continue Microsoft’s strategy of differentiating OS experiences by silicon, which may accelerate capability adoption on partner premium hardware but also risks fragmenting feature availability and confusing consumers about what “Windows” can do on a given device. (blogs.windows.com, thurrott.com)

---

Risks, limitations, and what could go wrong​

• Rollout fragility — preview cumulative updates have historically produced device‑specific installation or boot problems for some users. Insiders and IT pros should expect transient regressions, driver conflicts, and performance variability. Always back up before installing Beta builds. (windowslatest.com, reddit.com)
• Privacy and permission complexity — cross‑device Resume requires careful consent and background permissions on phones. If users misunderstand what is being shared between devices, that could lead to unexpected behavior or privacy concerns. Microsoft should continue to make the permission model and data flow transparent.
• Feature gating and perception — gating premium features by Copilot+ hardware and region might produce confusion or frustration among users who expect parity across Windows devices. Clear messaging from Microsoft about hardware dependencies will be critical. (blogs.windows.com, thurrott.com)
• Developer adoption lag — Resume’s true utility depends on app developer integration. Until a meaningful catalog of apps supports the Resume API, the feature will be visible only in a handful of scenarios. Microsoft must push developer outreach and provide robust SDK documentation to accelerate adoption.

---

Practical checklist for Insiders and IT pros​

• Back up important data and create an image or restore point before joining the Beta Channel.
• If testing Cross‑Device Resume, enable Link to Windows and grant background permissions on your Android device; use the same app account on both devices.
• Update Snipping Tool to the latest Insider version when available to try window‑mode recording; remember the capture is fixed at start.
• Monitor Feedback Hub and community forums for reports of driver conflicts or update installation issues; gather logs if you file feedback.
• For production environments, do not install Beta Channel builds on mission‑critical machines.

---

Conclusion​

Build 26120.5761 (KB5064093) is a classic Beta Channel flight: a mix of tangible productivity quality‑of‑life improvements, a clear push toward cross‑device continuity with Resume, and ongoing Copilot+/AI feature refinements that continue to differentiate Windows by hardware class. For Insiders, the build offers real new capabilities to test — especially cross‑device Resume and Snipping Tool window recording — but the staged rollout and known issues mean this is still a preview for experimentation rather than enterprise deployment. Keep backups handy, follow the staged toggle approach to get features sooner if you want them, and expect Microsoft to iterate quickly based on Insider feedback as these preview features ramp toward broader availability. (blogs.windows.com, windowslatest.com, windowsforum.com)

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.5761 (Beta Channel)