Microsoft shipped a new Insider Preview build this week that transforms how Windows users – and Spotify listeners – move between their phone and PC. Build 26200.5761, delivered as KB5064093 to the Dev and Beta channels, introduces a cross-device Resume feature that lets you pick up an Android app’s activity directly on your desktop, starting with Spotify. The flight also packs Copilot+ gesture tweaks, quality-of-life improvements from battery icons to dash-shortcuts, and a critical .NET fix for Arm64 developers – alongside a handful of vexing bugs that remind testers this is still early code.

Controlled Feature Rollouts (CFR) govern the most interesting additions, so not every Insider will see them immediately. Microsoft’s staged model reduces risk but means the exact feature set varies from machine to machine. What’s here, however, is a pragmatic snapshot of where Windows 11 is heading: tighter cross-device continuity, hardware-gated AI experiences, and quiet polish that should make daily computing smoother.

Cross-device Resume: picking up Android app activity on your PC

The marquee experiment is a new “Resume” taskbar alert. When a supported Android app is active on a paired phone, a prompt can surface on the Windows 11 desktop. Click it, and the PC launches the corresponding Windows app – or installs it from the Microsoft Store with a single click and signs you in – so playback, or eventually other tasks, continues seamlessly. The initial partner is Spotify: play a track on your Android device, and if the feature is flagged on for your machine, a Resume toast appears on the taskbar. Tapping it opens the desktop Spotify client and resumes the same song.

Microsoft is building this on the existing Phone Link stack, not a separate cloud service. That means users need a linked Android phone with Link to Windows running in the background, plus the same Spotify account on both devices. The PC must be running Build 26200.5761 with the “Get the latest updates as soon as they’re available” toggle enabled in Windows Update, and even then, exposure is telemetry-gated. Early adopters should navigate to Settings > Bluetooth & devices > Mobile devices, enable “Allow this PC to access your mobile devices,” and ensure the phone is linked before starting playback on the Spotify mobile app.

Why start with media? Playback state is simple to synchronise and doesn’t risk data loss if the handoff fails. It’s a low-risk, high-visibility use case that demonstrates the flow’s potential. If Microsoft publishes a Resume API and app developers embrace it, the feature could extend to drafts, messaging threads, and document states, cutting the friction of switching between screens – a direct shot at Apple’s Handoff, but for the Android–Windows world.

Productivity and UX polish: small changes with outsized impact

Build 26200.5761 is packed with tiny, immediately useful refinements.

Lock screen battery icons get a refresh. Laptop and tablet users will see redesigned battery iconography with clearer percentage visuals, making it easier to gauge charge state without unlocking. It’s a modest tweak, but for anyone who obsessively checks battery life, it’s a welcome one.

Snipping Tool gains window-mode screen recording. The screen recorder now lets you select a single application window as the capture region. The recording area snaps to that window’s bounds at start and stays fixed – it won’t follow the window if you drag it mid-capture. This is an inbox app update, not part of the OS build directly, and rolls out gradually. To use it, open Snipping Tool, switch to Record, pick “New,” then choose “Window Mode” from the recording area dropdown. Select the target window and start recording. The feature is ideal for tutorials or bug reports where you want a clean, predictable capture of one app.

En and em dash hotkeys finally arrive for Windows writers. Press Win + Minus (–) for an en dash (–) and Win + Shift + Minus for an em dash (—). Note the conflict with Magnifier: Win + Minus traditionally zooms out when Magnifier is active, so the dash shortcut won’t work in that accessibility context.

Windows Share pinning lets you pin favorite apps, contacts, or services to the top of the Share dialog. For anyone who repeatedly sends screenshots to the same messaging app or cloud folder, this eliminates a few clicks every time.

Copilot+ devices, Automatic Super Resolution, and Click to Do

Several Copilot-adjacent features are gated to Copilot+ hardware – machines with a dedicated NPU, including Snapdragon X-powered laptops. On those devices, Click to Do now supports a two-finger press gesture on touchscreens, allowing quick content selection and contextual actions without keyboard shortcuts. Agent results in Settings also deep-link to the exact pages they reference.

Automatic Super Resolution (Auto SR) gets simplified controls and toast-driven configuration on Snapdragon Copilot+ laptops. Gamers and creators can tweak upscaling behavior per title directly from pop-up toasts, rather than digging through submenus. It’s a clear nod that upscaling needs quick, visible adjustments, not buried settings.

This hardware-gated strategy is a double-edged sword. On one hand, NPU-accelerated AI can deliver low-latency, privacy-preserving features that turn demos into daily tools. On the other, splintering the user base by silicon risks confusion: non-Copilot owners get incomplete experiences, and IT admins managing mixed fleets face inconsistent behavior. How Microsoft balances innovation with inclusivity will define the Copilot+ narrative.

Fixes and developer notes: .NET, Windows Hello, and more

The build includes several targeted reliability fixes. Settings’ Installed apps list loads faster, Windows Hello face authentication is more reliable, and Game Bar stability improves on multi-monitor setups with mixed refresh rates.

Crucially for developers: a Visual Studio WPF crash on Arm64 after a recent .NET update is resolved by an accompanying patch – KB5064402. Anyone building or debugging WPF applications on Arm64 hardware must install that .NET update after applying the OS flight. The fix is a tidy example of OS and runtime teams coordinating to keep developer workflows intact. The recommended checklist: update to Build 26200.5761 on a test machine, immediately pull KB5064402 from Windows Update, and test WPF scenarios. Collect performance traces if you rely on Game Bar overlays and send them via Feedback Hub.

Known issues: regional quirks, scanning stalls, and a nasty Xbox controller bug

No Insider build is without gremlins, and 26200.5761 has a few that demand caution.

Recall behavior in the European Economic Area may malfunction due to regional regulatory requirements. The workaround is a quick reset: Settings > Privacy & security > Recall & snapshots > Reset Recall. But if you’re testing on an EEA-configured device, expect flakiness until Microsoft addresses the policy code.

File Explorer’s Shared section sometimes appears on the Home page even when empty, and the Temporary files scanner under Settings > System > Storage can hang during scanning. Power users may need to restart File Explorer, clear recent files/folders from Folder Options, or reboot to unstick the scanner. These are nuisance-level bugs, but they can disrupt workflows.

The most severe known issue: Xbox controllers connected via Bluetooth can trigger a bugcheck (blue screen). Microsoft has documented a manual Device Manager workaround, but it’s tedious. Start by unpairing the controller, toggling Bluetooth off/on, and re-pairing. If crashes continue, open Device Manager, switch to “Devices by driver” view under the View menu, expand Bluetooth and Human Interface Devices, and uninstall any greyed-out or suspicious Xbox or Bluetooth LE Xinput entries – checking “Delete the driver software for this device” if prompted. Reboot, then re-pair the controller and let Windows re-provision the driver. This is a clear signal: don’t run this build on a gaming rig that depends on Bluetooth controllers. Microsoft says a proper fix is in development.

Strategic analysis: where Windows is heading

Build 26200.5761 is a focused, pragmatic flight that illustrates Microsoft’s current modus operandi: small, synchronised wins delivered via controlled rollouts and hardware-targeted differentiation.

Strengths: The cross-device Resume experiment with Spotify is clever – a highly visible, low-risk demo that doesn’t depend on cross-platform document syncing. If Microsoft exposes a clean API, Windows could finally offer a practical Android‑to‑PC handoff story. The quality-of-life tweaks (dash hotkeys, share pinning, lock screen icons) are incremental but collectively reduce daily friction. Copilot+ and Auto SR show how NPU power can deliver fast, private, on‑device AI experiences that give OEMs something to sell beyond raw performance numbers.

Risks: Hardware gating fragments the user base. Features tied to Copilot+ or specific NPUs may never reach the majority of Windows users, creating a two-tier experience that confuses consumers and complicates enterprise deployment. Regional policy friction, like the Recall EEA bug, hints at a future where Windows feature sets diverge by geography. And the Xbox controller Bluetooth crash is a reminder that peripheral stability remains fragile – a single blue‑screen class issue can erode trust in the Insider program.

What Microsoft should do next: Publish developer documentation and an API reference for Resume so app vendors can build handoff support early. Provide transparent gating signals in Settings (a toggle status and estimated rollout window) to reduce confusion when features don’t appear. Prioritise the Bluetooth‑controller fixes before widening the rollout; gamers and streamers are loud and influential.

Practical guidance for Insiders, IT admins, and developers

For Insiders: Enable the “Get the latest updates” toggle in Windows Update, link your phone, and keep inbox apps like Snipping Tool updated from the Microsoft Store. Test Resume by starting Spotify playback on your Android device – noting that the feature is still rolling out, so patience is required.

For IT admins and lab managers: Image test machines or snapshot VMs before deploying. Pilot the build on a small ring that matches real workloads: developer workstations, gaming rigs with controllers, and Copilot+ hardware. Hold production fleets on known‑good builds until the Xbox controller crashes and Recall EEA behaviour are resolved.

For developers: Install the KB5064402 .NET patch immediately after the OS update if you work with WPF on Arm64. Evaluate whether your mobile app could expose a lightweight session token to the Phone Link/Resume pipeline – even if the API isn’t public yet, planning for such continuity will pay off if Microsoft opens it up.

Conclusion

Windows 11 Build 26200.5761 is a telling milestone. It nudges the platform toward more fluent device transitions with the cross‑device Resume experiment, squeezes extra polish into everyday workflows, and pushes on‑device AI with Copilot+ and Auto SR – all while revealing the unavoidable friction of preview software. For Insiders on non‑critical machines, it’s a worthwhile glimpse at what’s coming. For everyone else, the conservative play is to wait: let Microsoft squash the Xbox Bluetooth bug, clarify regional policies, and deliver the Resume API developers will need to make handoff truly useful. In the meantime, the build succeeds as a laboratory for ideas that could soon reshape how Windows and Android work together.