Microsoft has quietly begun testing a cross-device handoff feature in Windows 11 that lets users pick up Spotify playback on their PC right where they left off on their Android phone—with a single click. The new "Resume from your phone" capability landed in Windows Insider Preview builds 26200.5761 (Dev) and 26120.5761 (Beta) on August 22, 2025, via update KB5064093, and is rolling out gradually to Insiders who have opted into receiving the latest updates as soon as they are available.

The feature places a small taskbar prompt on a Windows 11 PC linked to an Android phone via Link to Windows and the same Microsoft account. When a user starts playing music in the Spotify app on their phone, the prompt appears; clicking it opens the Spotify desktop app—or triggers a one-click install from the Microsoft Store if it's missing—and resumes playback at the exact track and timestamp. Microsoft describes this as a context handoff, not streaming or mirroring, relying on short-lived AppContext tokens that convey the session state without running an entire Android runtime on the PC.

How the handoff works under the hood

The handoff architecture is deliberately lightweight. The phone publishes a time-boxed AppContext—essentially a deep link or intent—that identifies the current app activity. Windows then launches the native desktop app (or a web fallback) directly into the matching state. This avoids the heavy emulation overhead that doomed the Windows Subsystem for Android (WSA), which Microsoft deprecated on March 5, 2025. Instead of running Android apps locally, Windows now asks third-party developers to integrate with a Cross-Device Resume or Continuity SDK to expose their app’s state in a way that the OS can hand off.

For the initial preview, only Spotify is supported, but the model is designed to scale. Microsoft explicitly invited developers to adopt the SDK, signaling that messaging, note-taking, and document apps could be next. The one-click install path from the taskbar further reduces friction: if the desktop app isn't present, Windows can pull it from the Store and sign the user in automatically, all without manual searching.

Setup: what you need to try it now

The preview requires a very specific configuration, as detailed in Microsoft’s Insider blog and forum reports:

  • Windows PC: Must be enrolled in the Dev or Beta Insider channel and running build 26200.5761 (Dev) or 26120.5761 (Beta) with KB5064093 installed. The “Get the latest updates as soon as they’re available” toggle must be on to increase the chance of being included in the staged rollout.
  • Android phone: Must have Link to Windows installed, allowed to run in the background, and paired via Settings > Bluetooth & devices > Mobile devices on Windows.
  • Spotify account: The same account must be signed in on both the phone and the PC for the handoff to work.

Users report that the Resume prompt can be unpredictable because it depends on Link to Windows background reliability. Android OEM battery optimizations often kill the service, so Microsoft recommends excluding Link to Windows from battery-saving policies. Even with correct setup, the feature is being A/B tested—not all eligible Insiders will see it immediately.

Why Microsoft chose context handoff over Android emulation

The demise of WSA was a turning point. Originally positioned as Android app support via the Amazon Appstore, WSA ended support in 2025 after three years of lukewarm reception. Without Google Play Store access and burdened by engineering complexity, it never became a must-have feature. Microsoft’s new strategy embraces the reality that users don’t need to run Android apps on Windows—they just need to continue tasks seamlessly.

By shifting to context transfer, Microsoft trades broad app compatibility for a lighter, more secure, and more maintainable model. The taskbar-level prompt makes the capability discoverable, and the SDK approach puts the onus on developers to opt in. This aligns with the broader industry trend toward cross-device continuity, a space Apple has dominated with Handoff since iOS 8.

How it compares to Apple Handoff and rivals

Apple Handoff leverages deep OS integration across iOS, iPadOS, and macOS, syncing activities via iCloud. The user sees a Dock or lock screen icon and can resume Safari browsing, Mail composition, or document work with a tap. Microsoft’s Resume is conceptually similar—a shell-level prompt that opens the right app on the PC—but it operates in a more fragmented ecosystem.

Google’s Phone Hub for Chromebooks and Samsung’s “Continue apps on other devices” offer comparable functionality, but Microsoft’s advantage is Windows’ dominant desktop share. By making Resume central to the taskbar, the company hopes to build a habit that ties users to Windows even when they start tasks on their phones. However, the feature’s reliability hinges on Link to Windows performance across hundreds of Android models and OEM skins—a challenge Apple simply doesn’t face.

Benefits for everyday users

The immediate win is sheer convenience. Moving a podcast or playlist from a phone to PC speakers with a single click eliminates the friction of manually opening the app, searching for content, and skipping to the right spot. For less technical users, the auto-install path means they don’t need to know whether the Spotify desktop app is already installed—it just works.

Beyond media, the same mechanism could let users resume document editing, reply to messages, or pick up a shopping cart across devices. That would position Windows as the natural hub for all of a user’s digital activity, provided developers buy into the SDK.

Risks, limitations, and enterprise concerns

Privacy watchers and IT admins will rightfully scrutinize what data is transmitted in those AppContext tokens. Microsoft says the tokens are short-lived and only carry session context, but transparent documentation and auditable controls are missing in this early phase. For regulated industries, the ability to disable cross-device resume via Group Policy or CSP will be non-negotiable; a new policy (“DisableCrossDeviceResume”) has already appeared in Insider builds, but its effect must be thoroughly tested.

Fragmentation presents another risk. Without Apple’s control over both the OS and the app ecosystem, Microsoft depends on third-party developers to integrate the SDK—and Android OEMs to not cripple Link to Windows in the background. The initial Spotify-only rollout feels more like a proof of concept than a fully baked feature. Users who own phones from manufacturers known for aggressive battery management (Xiaomi, Oppo, OnePlus) may find the feature unreliable unless they manually whitelist the companion app.

Critically, some observers may misinterpret Resume as a return of Android apps to Windows. It is not. WSA is gone, and this handoff model does not run Android UI or code on the desktop. Instead, it opens native Windows apps—a fundamental distinction that changes the security profile and developer ask entirely.

Strategic calculations: what Microsoft gains

By embedding Resume in the shell, Microsoft keeps Windows at the center of users’ multi-device lives. People increasingly start tasks on mobile; the OS that offers the easiest path to continue on a bigger screen wins more engagement. For Surface and Windows OEMs, a reliable “it just works with your phone” narrative could become a selling point, echoing Apple’s ecosystem lock-in.

Just as importantly, the move offloads the cost of maintaining an Android runtime. Context handoffs deliver much of the convenience that WSA promised at a fraction of the engineering and security overhead. The tradeoff is that Microsoft must now court developers to adopt its continuity SDK—a challenge that will require demonstrable user demand and solid documentation.

What readers and IT admins should do now

For enthusiasts eager to test the feature, the steps are straightforward but require patience due to staged rollout:

  • Join the Dev or Beta Insider channel and install KB5064093.
  • Pair an Android phone via Settings > Bluetooth & devices > Mobile devices.
  • On the phone, open Link to Windows, allow background access, and sign in with the same Microsoft account.
  • Start Spotify playback on the phone and wait for the taskbar prompt. If it doesn’t appear, check that Link to Windows isn’t being battery-optimized.

For IT administrators, the following guardrails apply:

  • Test in a lab first with a non-production device.
  • Identify the new “DisableCrossDeviceResume” CSP and verify it blocks or permits handoff as expected.
  • Consider phased deployment: allow media apps but block productivity apps until data flow and security are fully understood.
  • Update user guidance to explain how to disable the feature in Settings and what the experience looks like.

What to watch for in the coming months

The next few Insider flights will reveal whether Microsoft expands the handoff to more apps. Messaging platforms like Telegram or WhatsApp, document editors such as Word or Google Docs, and reading apps like Kindle are obvious candidates. The speed of third-party adoption will signal whether Resume becomes a platform-defining convenience or a niche curiosity.

Equally important will be the release of formal privacy documentation and admin controls. Without clear answers on what data is transmitted and how long it persists, enterprises will be hesitant to enable the feature on managed devices. Microsoft’s track record with cross-device experiences—from Timeline to “Continue on PC”—has been uneven; execution here must be flawless to build trust.

Finally, real-world reliability across the Android ecosystem will make or break the feature. If users must constantly fiddle with battery settings to get Resume to work, many will simply ignore it. Microsoft’s own guidance to exclude Link to Windows from battery optimization acknowledges the problem, but that’s a hoop most ordinary users won’t jump through without prompting.

A pragmatic step toward true cross-device continuity

“Resume from your phone” is not a radical innovation—it is a pragmatically scaled-down evolution that matches the way people actually use devices. By prioritizing frictionless task handoff over the dream of running Android apps natively, Microsoft is playing to Windows’ strengths while acknowledging its mobile limitations. The single-app, Insider-only preview is modest, but it lays a foundation that could eventually rival Apple’s Handoff in the Windows ecosystem.

The feature’s ultimate success will depend on three factors: developer uptake, transparent privacy guarantees, and consistent performance across Android phones. If Microsoft can deliver on all three, Resume could quietly become one of Windows 11’s most useful additions. If not, it risks being remembered as yet another half-finished cross-device experiment. For now, the message is clear: Microsoft wants Windows to be the natural place you continue what you start on your phone, and it’s beginning that journey one Spotify track at a time.