On March 5, 2025, Microsoft pulled the plug on Windows Subsystem for Android, ending the only native way to run Android apps locally on Windows 11. The move marks the final pivot in a seven-year journey that began with the Your Phone app and now leaves Phone Link streaming as the company’s sole official bridge between Android handsets and the Windows desktop.

Microsoft introduced the Your Phone concept at Build 2018, promising a frictionless link between Windows 10 and Android devices. When the October 2018 Update shipped, the Your Phone app arrived with basic photo and notification syncing, but the real headline was mobile app mirroring. Early demos showed Android apps running in their own windows on a Surface, controlled by keyboard, mouse, or touch. The vision was clear: your phone’s apps, on your PC, with no emulator required.

The company quickly settled on a streaming model rather than building a local Android runtime into Windows. That decision shaped everything that followed. Instead of installing apps on the PC, Your Phone would stream the phone’s display and forward inputs over Wi‑Fi and Bluetooth LE. It avoided app store fragmentation and duplicate sign‑ins, but it tethered performance to network conditions and created immediate compatibility headaches.

The Samsung Years: OEM Partnerships Drive Progress

Most of the real progress between 2019 and 2022 came through a tight partnership with Samsung. Select Galaxy phones gained “Link to Windows” integration baked into the firmware, unlocking features that other Android devices simply didn’t get. By 2020, Samsung and Microsoft were demoing multi‑app support on the Galaxy Note20 — users could pin mobile apps to the Windows taskbar and run several side by side, each in its own window.

Those capabilities remained gated behind specific hardware. Early rollouts required Android 9.0 or higher, Bluetooth LE Peripheral mode on the PC, and phones that ran Samsung’s customized Link to Windows service. The list of supported devices expanded slowly, and many mainstream Android brands never reached feature parity.

In 2022, Microsoft rebranded Your Phone to Phone Link on Windows and Link to Windows on Android. The name change reflected a broader ambition: the tool was no longer a simple companion app but the central cross‑device bridge for notifications, calls, messaging, and app mirroring.

What “Mirroring Android Apps” Actually Means

Phone Link’s app feature does not install anything on the PC. When you launch an Android app from the Phone Link interface, your phone renders the UI, encodes it as a video stream, and sends it to Windows over the local network. Mouse clicks, keystrokes, and touch inputs travel back to the phone in real time. The phone remains the sole runtime — it processes everything, maintains your sign‑in sessions, and handles push notifications.

This streaming architecture explains both the strengths and the sharp limitations. On the plus side, there’s no need to re‑authenticate apps, no duplicate storage, and no compatibility layer to maintain. But audio often plays through the phone’s speaker by default, multitouch gestures require a Windows touchscreen, and many apps intentionally block screen casting. Banking apps frequently show a black screen, while DRM‑protected video content may refuse to stream entirely.

Microsoft’s own documentation confirms these quirks. The feature demands that both devices sit on the same Wi‑Fi network, and even then, latency can creep in. Bluetooth LE assists with device discovery and some input features, but the core streaming pipe is Wi‑Fi — and that means frame drops, compression artifacts, and occasional disconnects are part of the experience.

Technical Requirements and Real‑World Limitations

Before trying app mirroring, users need to check a strict set of prerequisites:

  • Windows: Windows 10 October 2018 Update (1809) or later, fully patched. Phone Link must be updated to the latest version, sometimes including preview builds for new features.
  • Android: Link to Windows companion app installed and current. The phone must run Android 9.0 or higher, but full app mirroring is limited to a supported device list — still dominated by Samsung Galaxy models.
  • Network: Both devices must be on the same Wi‑Fi network. A 5 GHz connection reduces latency, but the stream is never as responsive as a local app.
  • Permissions: On the Android side, you must grant Link to Windows access to notifications, SMS, phone, and storage. Without these, even basic functions break.

Practical pitfalls pile up fast. Games and any app requiring precise timing suffer from input lag. Keyboard shortcuts may not map correctly. Audio routing varies: some apps send sound to the PC, others do not. And app developers can block mirroring at the OS level, making the feature useless for entire categories of content.

Timeline: From Flashy Demos to WSA’s Funeral

The path from promise to current reality unfolded in fits and starts:

  • October 2018: Windows 10 1809 ships with Your Phone. App mirroring is teased but not yet functional.
  • 2019: Insider testing begins. Screen mirroring requires a Samsung phone and a PC with Bluetooth LE Peripheral mode.
  • 2020: Microsoft and Samsung show multi‑app support on Galaxy Note20. Users can pin Android apps to the taskbar.
  • 2022: Your Phone rebrands to Phone Link; Link to Windows becomes the Android counterpart.
  • March 2024: Microsoft announces end‑of‑support for Windows Subsystem for Android (WSA). The Amazon Appstore on Windows is deprecated.
  • March 5, 2025: WSA stops working. All locally installed Android apps vanish from Windows 11. Phone Link streaming becomes the only official Microsoft‑backed method for running Android apps on a PC.

The death of WSA was a strategic atom bomb. For three years, Windows 11 users could sideload APKs or grab titles from the Amazon Appstore and run them natively. That local runtime solved many of the streaming model’s problems — zero network latency, full keyboard and mouse support, no DRM‑related black screens. But maintaining an Android subsystem proved resource‑heavy, and the Amazon store never attracted a critical mass of developers. Microsoft cut its losses and repositioned Phone Link as the future.

Despite its constraints, Phone Link delivers real value for specific workflows:

  • No duplicate sign‑ins: Your banking app, authenticator, or messaging client stays signed in on the phone. Phone Link simply mirrors that existing session.
  • Fast task switching: Replying to a WhatsApp message, approving a 2FA prompt, or checking a delivery status takes seconds — no need to unlock your phone.
  • Taskbar integration: Frequently used apps can be pinned to the Windows taskbar, launching with a single click just like a native Windows program.
  • Lower maintenance burden: Microsoft avoids the nightmare of shipping and updating an entire Android runtime across billions of Windows PCs. The phone does all the heavy lifting.
  • OEM polish: On Samsung devices, Link to Windows is deeply integrated, enabling features like app continuity (handoff between phone and PC) and clipboard sync that feel close to Apple’s Continuity.

Risks, Security, and Enterprise Pitfalls

Streaming a phone’s screen over a local network introduces risks that IT departments cannot ignore:

  • Network attack surface: Though Phone Link uses encrypted channels, a compromised router or weak Wi‑Fi password can expose streaming sessions. Microsoft recommends strong WPA3 encryption and isolated guest networks for untrusted devices.
  • DRM and app blocking: Media apps like Netflix or Disney+ may refuse to stream, and many banking apps detect mirroring and shut down, leaving users with a black window.
  • MDM conflicts: Organizations that manage Android devices via Microsoft Intune or other MDM platforms may disable Link to Windows entirely for work profiles. Administrators must review policies to prevent data leakage or compliance violations.
  • OEM dependency: The feature’s reach depends on phone manufacturers embedding and updating Link to Windows. Outside Samsung and a few Honor devices, support is patchy. If your OEM stops updating the companion service, features break.

Setting up the service takes about five minutes — if your hardware is compatible:

  1. On your Windows PC, open Phone Link (preinstalled on Windows 10 and 11) and select Android.
  2. On your Android phone, download Link to Windows from the Play Store. Alternatively, Samsung Galaxy phones have it preinstalled under Settings → Connected devices → Link to Windows.
  3. Scan the QR code displayed in Phone Link with your phone’s camera. Grant all requested permissions: notifications, contacts, SMS, phone, and media.
  4. Ensure both devices connect to the same Wi‑Fi network. Bluetooth must be enabled for discovery and input features.
  5. In Phone Link, click the Apps tab. A list of supported apps appears. Click any to launch it in a separate window on your PC.

If the Apps tab is missing, your phone likely isn’t on Microsoft’s supported list. Check the official compatibility page and update both apps. For gaming or latency‑sensitive work, don’t expect miracles — even a great network adds 30–50 milliseconds of lag.

Strategic Implications: Why Microsoft Chose Streaming Over Local Runtime

The WSA shutdown closes the book on a decade‑long identity crisis. Microsoft has swung between two poles: host Android locally and compete with Google’s ecosystem, or stream from the device users already own. The local approach (WSA) required a full Android‑compatible layer, a separate app store, and constant kernel updates. It never gained traction with developers, and the lack of Google Mobile Services meant many apps refused to run or lost features.

Streaming, by contrast, leans into what Microsoft already does well — cloud and connectivity. Phone Link turns the PC into a thin client for the phone, making the handset the single source of truth for apps, data, and authentication. That model aligns with industry trends: Apple’s iPhone mirroring in macOS Sequoia, Google’s Phone Hub on ChromeOS, and Samsung DeX all treat the phone as the hub. Microsoft is betting that users prefer simplicity over local power.

The risk is obvious. By killing WSA, Microsoft has no answer when streaming fails. Users who need offline Android apps, or who work with DRM‑heavy content, or who simply own a non‑Samsung phone, are left with no first‑party path. That creates an opening for third‑party emulators and remote‑control tools.

For anyone who must run Android apps natively on Windows, a handful of workarounds exist:

  • BlueStacks, NoxPlayer, LDPlayer: These Android emulators install a full virtualized Android environment on your PC. They support Google Play, keyboard mapping, and multiple instances. Performance is solid, but they consume significant RAM and CPU. Critically, they operate entirely independently from your phone — no session sharing, no notifications sync.
  • scrcpy: An open‑source tool that mirrors and controls Android devices over USB or TCP/IP. It’s low‑latency, free, and works with almost any Android phone if you enable Developer Options and USB debugging. scrcpy offers far better input fidelity than Phone Link, but it’s not a consumer‑friendly solution and requires a wired connection for best results.
  • AirDroid and TeamViewer: These remote‑access apps provide wireless mirroring with file transfer and notification sync. Input handling varies, and free tiers often impose resolution or session limits.

None of these alternatives match the seamless integration of Phone Link, but they fill functionality gaps Microsoft abandoned with WSA’s death.

What to Watch Next

Microsoft’s cross‑device strategy now hinges on two pillars: Phone Link for Android continuity, and Windows 365 / Cloud PC for full desktop streaming. Expect incremental Phone Link updates that expand supported devices, improve audio routing, and possibly add a low‑latency mode over USB. But a return to local Android runtimes is unlikely — the engineering cost proved too high for too few users.

For consumers, the calculus is simple: if you own a recent Samsung flagship, Phone Link will cover most quick tasks. For everyone else, test compatibility before relying on it. And if local Android apps are critical, keep an emulator on standby.

The journey that started with a Build 2018 stage demo has reached its endgame. Android apps on Windows aren’t native anymore — they’re streamed, contingent, and entirely dependent on the phone in your pocket. For some, that’s a liberation. For others, it’s a regression. The only certainty is that Microsoft isn’t looking back.