Microsoft shipped a new Windows 11 Dev Channel build on August 22, 2025, and the marquee addition is a cross-device resume capability that mirrors Apple’s Handoff. Build 26200.5761 (KB5064093) marks the first time Windows can detect activity on a paired Android phone and offer a taskbar prompt to continue that activity on the PC. For now, the feature is limited to Spotify and is rolling out gradually via Microsoft’s staged telemetry-controlled deployment model.

The build also packs a window-based screen recording mode for Snipping Tool, battery icon refinements on the lock screen, new keyboard shortcuts for en and em dashes, and under-the-hood work on Copilot+, Click to Do, and Automatic Super Resolution. As usual for the Dev Channel, many of these enhancements are gated behind the “get the latest updates” toggle and rely on telemetry to determine which Insiders see them first. This approach lets Microsoft collect real-world data while minimizing risk, but it also means two machines on the same build can behave differently.

Smooth Handoff from Android to Windows, Starting with Spotify

The headliner is a new cross-device resume system. When a user starts playback in the Spotify app on an Android phone, a “Resume from your phone” notification appears on the Windows taskbar if the phone is paired via Link to Windows. Clicking the notification opens the Spotify desktop app — or triggers a one‑click Microsoft Store install if it isn’t already present — and continues the song at the same point.

Microsoft first teased this capability at its Build 2025 developer conference, though the demo was later deleted. The Verge pointed out the similarity to Apple’s Handoff, which lets users transition tasks seamlessly between iPhone, iPad, and Mac. Unlike Handoff, Microsoft’s implementation is currently limited to a single app and requires identical Spotify accounts on both devices.

Technical requirements are explicit:
- A Windows 11 PC running Build 26200.5761 or later, with the “Allow this PC to access your mobile devices” option enabled in Settings > Bluetooth & devices > Mobile devices.
- An Android phone with Link to Windows installed and background permissions granted.
- The same Spotify account signed in on both endpoints.

The feature relies on Link to Windows for inter-device signaling, and the staged rollout means many Insiders won’t see the resume prompt even on a supported build. Microsoft is treating this as a low‑volume experiment to gauge reliability and interference patterns before broadening availability.

Why a Single App Makes Sense for the Pilot

Limiting the first iteration to Spotify reduces the blast radius. Account parity is straightforward, and a playback state is an atomic, well‑defined piece of context that rarely varies across platforms. Testing the handoff plumbing with a major media app gives Microsoft’s engineering team a representative workload without the fragmentation that would come from generically supporting documents, emails, or web pages.

Neowin and The Verge both note that the feature is essentially a streamlined version of a Windows Insider experiment from earlier preview events. By shipping it in a numbered build, Microsoft signals that the Resume API is stable enough for sandboxed partner adoption, even though end‑user visibility remains controlled.

Developer Impact and the Resume API

Under the hood, cross‑device resume is built on an API that third‑party apps can integrate. Once the Spotify experiment validates the basic flow, developers can add resume support to their own apps. The most critical integration points are:
- Consistent account linking logic that matches phone and PC identities.
- Reliable background services on Android that can send resume triggers without draining battery or infringing on protected Android activity states.
- A graceful install flow on Windows when the target desktop app isn’t already present.

Microsoft hasn’t published formal Resume API documentation yet, but the build notes confirm that the framework is designed to be extensible. The current narrow scope gives ISVs time to study the implementation and adjust their telemetry before the feature reaches the general public.

Snipping Tool Gets Window‑Mode Screen Recording

Another productivity win in this build is Snipping Tool’s new ability to record a specific application window. Instead of capturing the entire screen or manually lassoing a rectangle, users can select “Window mode,” and Snipping Tool will lock onto the chosen window. The resulting MP4 video stays pinned to that window even if other elements overlap or the window moves.

Microsoft deliberately chose a fixed‑region approach rather than dynamically following the window. That design ensures consistent framing for tutorials, bug reports, and how‑to videos where the recorder wants to show a single application without cropping surprises. For professionals who previously relied on third‑party tools to capture a single window, the change eliminates a step in the workflow and reduces post‑production trimming.

Real‑World Utility

Support techs and educators stand to gain the most. Recording an application window that might be partially obscured by a notification or a chat pop‑up is a common frustration, and Snipping Tool now handles it natively. The fixed‑region behavior also sidesteps odd encoding artifacts that can occur when a recording region constantly resizes. Combined with Snipping Tool’s existing annotation features, the window recorder makes Windows a more self‑sufficient platform for lightweight screen capture.

Copilot+, Click to Do, and Auto SR Adjustments

Build 26200.5761 continues to refine the Copilot+ experience on compatible hardware. A new touch invocation for Click to Do — press and hold with two fingers — launches the context‑sensitive selection tool on Copilot+ touchscreens. It joins the existing mouse and keyboard triggers, giving touch‑first users parity with traditional input methods. The change is rolling out gradually to devices that opt into the latest updates.

On Snapdragon‑powered Copilot+ PCs, Microsoft simplified Automatic Super Resolution controls. Toast notifications now surface streamlined configuration options, making it easier to toggle Auto SR on or off without diving into deep settings menus. The goal is to make image and texture upscaling more discoverable while reducing intrusion during graphics‑intensive tasks. These device‑specific tweaks reflect ongoing collaboration with OEMs to balance visual quality and power efficiency.

Small but Meaningful Input and UI Tweaks

Not every change needs a keynote. Three minor adjustments in this build add up to noticeable quality‑of‑life gains:

  • En dash and em dash shortcuts: Windows now supports WIN + – for an en dash and WIN + Shift + – for an em dash. The caveat is that Magnifier users who rely on WIN + – for zooming will find the dash shortcut overridden; Magnifier takes precedence.
  • Lock screen battery iconography: The battery indicator on the lock screen now includes a percentage and clearer status visuals. It’s a cosmetic change, but it eliminates the need to unlock the device just to check the charge level.
  • Windows Share refinements: Building on earlier improvements, the share experience continues to get small, iterative polish that speeds up the act of sending links and files between apps.

These micro‑improvements signal Microsoft’s focus on the cumulative effect of hundreds of small friction removers rather than a single dramatic overhaul.

Reliability Fixes and Hardening

Beyond the feature work, KB5064093 addresses several nagging issues:

  • Settings performance: The Apps > Installed apps list now loads faster, a long‑standing complaint for users with large application catalogs.
  • Windows Hello facial recognition: Multiple reports of the login screen requesting a PIN even after a successful face scan prompted a targeted fix. Insiders who experienced this regression should see more consistent authentication.
  • Gaming overlay performance: An under‑the‑hood change reduces frame‑rate hits when overlays like Game Bar are active on multi‑monitor setups with mismatched refresh rates.

These fixes are typical of a hardening build. Microsoft encourages Insiders to file Feedback Hub reports with traces if any regression persists, as the data helps stabilize the feature experiments running in parallel.

Security and Privacy Considerations

Every new cross‑device signal introduces a potential data pathway, and the Resume feature is no exception. Because the initial implementation relies on identical Spotify accounts, the risk of cross‑account data leakage is low. However, the Link to Windows background channel that enables the resume notification does collect metadata about activity states. Key questions remain:

  • How long is resume metadata stored, and is it retained after the session ends?
  • Which telemetry fields report resume attempts, and do any identifiers leave the local device pairing?
  • What minimum Android permissions does Link to Windows require for the background behavior (e.g., notifications, activity recognition, network state)?

Microsoft has not yet published a privacy whitepaper detailing the Resume telemetry model. Until that documentation appears, enterprise security teams and privacy‑conscious users should treat Resume as an opt‑in convenience that demands background permissions and pairing trust. Shared or corporate devices warrant extra caution; a resume prompt on a team PC could inadvertently surface personal activity from a linked phone.

Mitigations and Attack Surface

The pairing mechanism adds an attacker surface if authentication is weak. Strong device pairing — enforced through Microsoft account multi‑factor authentication and Link to Windows confirmation dialogs — is the primary defense. Microsoft’s UI prompts should always identify the initiating device and account before any resume action proceeds. For enterprises, fine‑grained Group Policy or Intune controls would allow disabling resume for specific apps or entirely. Those controls aren’t yet present in the build, but policy templates tend to follow feature stabilisation, so IT admins should monitor the release notes for Mobile device access and Resume‑related settings.

Enterprise and IT Admin Notes

Dev Channel builds are experimental by definition. They belong on test hardware only. If an organization must evaluate this build:

  • Use dedicated VMs or secondary devices, never production machines.
  • Validate Windows Hello behavior, device management policies, and imaging workflows early, as authentication fixes can interact with configured security baselines.
  • Check that corporate‑managed Android phones with conditional access policies don’t block Link to Windows’ background permissions or account parity requirements.
  • Watch for new entries in Group Policy and Intune related to Mobile device access, Resume, and Copilot+ toggles.

The absence of explicit enterprise controls for cross‑device resume means this feature is not yet ready for regulated environments. Data loss prevention frameworks that inspect network activity may need rule updates once resume signals are better understood.

Testing Guidance for Insiders and Power Users

If you’re curious to explore Build 26200.5761, follow these practical steps:

  • Use non‑critical hardware: The Dev Channel can break drivers, sign‑in flows, or peripheral compatibility at any time.
  • Enable the latest updates toggle: This increases the probability that telemetry‑gated features like the Spotify resume prompt will appear.
  • Document everything for Feedback Hub: Screenshots, clear reproduction steps, and UWP/Win32 traces dramatically accelerate Microsoft’s triage.
  • Test the Spotify resume flow end‑to‑end: Verify the install prompt, account sign‑in, and playback continuation on a fully paired setup.
  • Experiment with Snipping Tool window recording on common targets such as browsers, Remote Desktop sessions, and games. Note any performance or stability anomalies.

Risks and Known Caveats

Several trade‑offs are inherent in this release:

  • Fragmented experience: Telemetry gating means your friend’s identical build may lack features you have, making troubleshooting inconsistent.
  • Android background permissions: Resume relies on Link to Windows’ ability to run background tasks. Users who restrict background activity may find the feature unreliable; those who grant broad permissions increase their privacy exposure.
  • Account lock‑in: Requiring the same Spotify account simplifies continuity but excludes family‑shared devices and users with multiple accounts.
  • Missing enterprise governance: Organizations will need policy controls before cross‑device resume can be safely deployed in regulated settings.

These limiting factors are part of Microsoft’s deliberate, low‑risk approach. The company is sacrificing short‑term feature breadth for long‑term reliability and trust.

The Bigger Picture: Windows as the Cross‑Device Hub

Build 26200.5761 isn’t revolutionary, but it clarifies Microsoft’s direction. The push toward Android‑to‑PC continuity — even if it starts with a single app — signals that Windows is intended to be the center of a user’s digital life, bridging the gap between phone and desktop. Apple’s ecosystem has long benefited from tight integration; Microsoft is now building a similar fabric but must do so across a hardware landscape it doesn’t fully control.

The success of this strategy hinges on a few factors: developer adoption of the Resume API, transparent privacy controls, and enterprise governance that keeps pace with consumer features. For now, the Spotify experiment is a manageable seed. Whether it grows into a genuine Handoff competitor depends on how quickly Microsoft expands the supported app list and how well it communicates the privacy and security model to IT admins.

Recommendations for Different Audiences

  • Enthusiasts and testers: Grab the build on a spare machine, opt into latest updates, and file detailed Feedback Hub reports. Your logs directly shape the release.
  • Developers: Watch for the Resume API documentation. Start planning how your app could leverage account‑linked continuity, keeping background permission models and install flows front of mind.
  • IT pros and enterprise admins: Treat this build as a preview of coming cross‑device capabilities, not a deployment candidate. Begin a threat‑model analysis of Link to Windows background channels and monitor policy channels for new controls.
  • Privacy‑conscious users: Review Link to Windows permissions on your Android device. Consider limiting or disabling the resume feature if you’re uncomfortable with the background signaling, at least until detailed privacy documentation is available.

Build 26200.5761 (KB5064093) is available now to Dev Channel Insiders. Staged features appear only to a subset of opted‑in devices; those who want to try the new experiences should enable the latest updates toggle and follow the setup steps for Link to Windows and device pairing.