Run Android Apps on Windows 11 After WSA Shutdown (2026)

WSA is deprecated and no longer updated. What happens to your installed Android apps, plus 3 supported ways to run Android on Windows 11 in 2026.

Quick answer. Windows Subsystem for Android reached end of support on March 5, 2025. Apps installed before then still open, but they get zero platform updates or security fixes and can no longer be installed fresh. The three supported replacements are Android emulators (BlueStacks, MuMu, LDPlayer), Google Play Games for PC, and phone mirroring via Phone Link.

If you opened an Android app on Windows 11 recently and it either refused to launch or nagged you that Windows Subsystem for Android (WSA) is unsupported, nothing broke on your end. Microsoft deprecated WSA, and the runtime that quietly powered Amazon Appstore titles on Windows 11 is now a dead-end platform. This guide is the migration path: what actually happened to the apps you already installed, and the three sanctioned routes to keep running Android on Windows 11 in 2026 — mapped to what you're actually trying to do.

What actually happened to WSA?

Microsoft announced the deprecation on March 5, 2024, and pulled the Amazon Appstore and Windows Subsystem for Android from the Microsoft Store the next day. Anyone who had installed them before March 6, 2024 kept access through a one-year wind-down. That wind-down ended on March 5, 2025 — the official end-of-support date.

Here's the part that trips people up: end of support does not mean the runtime was force-uninstalled. If WSA is still on your machine, your installed apps generally keep launching. What you lost is everything that makes a platform safe to depend on:

  • No more updates or fixes. The WSA runtime receives no feature, compatibility, or security patches. Any vulnerability found after March 2025 stays unpatched.
  • No new installs. WSA is gone from the Microsoft Store, so a clean Windows install or a new PC cannot get it back through any supported channel.
  • No app source. The Amazon Appstore was WSA's only sanctioned storefront, and it's gone too — so you can't install new apps or update the ones you have.

Practically, treat any surviving WSA install as frozen and temporary. It's fine for a throwaway app you don't sign into, but it's the wrong place for anything touching your bank, your email, or two-factor codes. Migrate those to one of the routes below.

How do I check whether WSA is still installed?

Open PowerShell and query the package directly:

Get-AppxPackage -Name MicrosoftCorporationII.WindowsSubsystemForAndroid

If it returns a package block, WSA is still present and your old apps should still open. If it returns nothing, it's already gone and you're starting clean — skip straight to picking a replacement.

The three sanctioned continuity routes

There is no drop-in replacement that resurrects your exact WSA setup. Instead, Microsoft, Google, and the emulator vendors each cover a different slice of the "Android on Windows" job. Pick by what you're doing, not by which one has the flashiest homepage.

1. Android emulators — the closest replacement for general apps and games

A full emulator (BlueStacks, MuMu Player, or LDPlayer) runs a complete Android OS in a window with the Google Play Store built in, so you get a real app catalog rather than a curated subset. This is the nearest thing to what WSA promised, and then some.

  • BlueStacks ships the most recent Android base of the mainstream three and is the safe default for non-technical users — broadly compatible and polished.
  • MuMu Player targets high-frame-rate gaming and a more modern Android base; a good pick if smooth rendering matters.
  • LDPlayer is the performance-first, lighter-weight option that tends to do best on weaker hardware.

The old blocker — emulators fighting with Windows virtualization — is largely solved. Modern builds use the Windows Hypervisor Platform API to coexist with Hyper-V, WSL2, and Docker, so you no longer have to disable virtualization to run them (BlueStacks fixed this conflict back in version 5.20). The trade-off: gaming performance can run roughly 10–15% lower with Hyper-V active versus fully disabled, so competitive players may still turn it off. If your machine can't do virtualization at all, see our guide to running an Android emulator without virtualization.

For a full breakdown of the options — including cloud and browser-based ones — see the Android emulators complete guide and our roundup of the top virtual Android emulators. On older hardware, start with the best Android emulator for a low-end PC.

2. Google Play Games for PC — the official Google route, games only

Google Play Games on PC is Google's own native Windows client. It runs Android games — a catalog well past 200,000 titles including paid ones — with cross-progression to your phone, mouse-and-keyboard mapping, and no third-party emulator involved. It is the most legitimate, lowest-friction option if games are all you need.

The catch is right there in the name: it's games only. You cannot install WhatsApp, a banking app, or a productivity tool through it. Minimum requirements are also stricter than a lightweight emulator:

  • Windows 10 (version 2004 or newer) or Windows 11
  • A solid-state drive with at least 10 GB free
  • Intel UHD Graphics 630 or comparable GPU
  • A CPU with 4 physical cores and 8 GB RAM or more
  • Hardware virtualization enabled in BIOS/UEFI
  • A personal Google account (some work/school accounts are blocked)

3. Phone mirroring — for the apps tied to your phone number and identity

Windows 11's Phone Link app can stream Android apps from your actual phone into resizable windows on your PC. As of early 2026 this "Apps" feature is generally available with expanded, almost-full-screen layouts. The app runs on the phone; your PC is just the display and keyboard.

That design is exactly right for messaging and identity-bound apps — the app keeps your real phone number, your logged-in session, and your push notifications, with nothing re-installed on the PC. Limits to know: it works only on select phones from Samsung (S22–S24 series and similar), HONOR, OPPO, ASUS, vivo, Xiaomi, and OnePlus that ship with Link to Windows; you can open up to five phone apps at once; and some apps won't expand their layout. Your phone also has to be powered on and on the network.

Which route fits your use case?

What you're doingBest routeWhy
General apps (banking, utilities, social)Android emulatorFull Play Store; real app catalog, not a curated subset
Mobile gamesGoogle Play Games for PCOfficial, native, cross-progression, no third-party runtime
Messaging / OTP / phone-number appsPhone Link mirroringKeeps your number, session, and notifications on the real device
App / QA testing during developmentAndroid emulator (or Android Studio AVD)ADB access, adjustable Android version, snapshots, root options
One frozen legacy app you can't moveExisting WSA (short term)Still opens, but unpatched — migrate off anything sensitive

Which route fits your hardware?

Hardware tierRecommended routeNotes
Low-end / older laptop (no SSD, weak GPU, virtualization off)LDPlayer, or Phone LinkLDPlayer is lightest; Phone Link offloads all work to the phone
Mainstream PC (SSD, quad-core, 8–16 GB RAM)BlueStacks or Google Play GamesBoth run comfortably; Play Games if you only want games
Gaming rig (modern i5/Ryzen 5+, 16 GB+, dedicated GPU)MuMu Player or Google Play GamesHigh-FPS rendering; disable Hyper-V for the last 10–15%
Dev machine running Docker/WSL2Hyper-V-compatible BlueStacks or Android Studio AVDWindows Hypervisor Platform lets the emulator coexist with your containers

What about developers testing Android apps?

If your reason for running Android on Windows was app testing rather than personal use, WSA was never the right tool anyway — it had no clean ADB story and a fixed Android version. Use Android Studio's emulator (AVD) for API-level control and snapshots, or point ADB at a desktop emulator. Most emulators expose an ADB bridge in their advanced settings; enable it, note the port it prints, then connect:

# Confirm no stale device is attached
adb devices

# Connect to the emulator's local ADB bridge (port varies by emulator)
adb connect 127.0.0.1:5555
adb devices

From there you get adb install, logcat, and the rest of the normal toolchain against a real Android surface. If you're building out a team that needs consistent, reproducible mobile test environments across Windows and macOS, Codersera can help you hire vetted remote developers who set this up as standard practice.

Your migration checklist

  1. List the Android apps you actually used in WSA and sort them into three buckets: games, general apps, and phone-tied apps (messaging, OTP, banking).
  2. Send games to Google Play Games for PC, general apps to an emulator, and phone-tied apps to Phone Link.
  3. Sign out of anything sensitive inside the old WSA install, then stop using it for accounts and 2FA.
  4. Install one emulator first rather than three — most people only need a single general-purpose route plus, optionally, Phone Link.
  5. If you run Docker or WSL2, pick a Hyper-V-compatible emulator build so you don't have to toggle virtualization on and off.

FAQ

Will my WSA apps stop working overnight?

No. Reaching end of support did not trigger a forced uninstall. If WSA is still installed, your apps generally keep opening. But they receive no updates or security fixes, so treat the setup as frozen and migrate anything that matters.

Can I reinstall Windows Subsystem for Android in 2026?

Not through any supported channel. WSA and the Amazon Appstore were removed from the Microsoft Store in March 2024, so a fresh Windows install or a new PC has no sanctioned way to get them back. Use an emulator, Google Play Games, or Phone Link instead.

Is Google Play Games for PC a full WSA replacement?

Only for games. It's Google's official native Windows client with a large game catalog and cross-progression, but it can't run general apps like WhatsApp, banking apps, or productivity tools. For those you need an emulator or phone mirroring.

Do Android emulators still conflict with Hyper-V and WSL2?

Mostly no. Modern BlueStacks, MuMu, and LDPlayer builds use the Windows Hypervisor Platform API to run alongside Hyper-V, WSL2, and Docker. Gaming performance can be about 10–15% lower with Hyper-V active, so competitive players sometimes disable it, but coexistence works out of the box.

Which is the safest option for banking and 2FA apps?

Phone Link mirroring, because the app stays on your real phone with its real session and number — nothing sensitive is re-installed on the PC. An emulator with the official Play Store is the next-best option; a frozen, unpatched WSA install is the one to avoid.

Yes, when you use the official app (BlueStacks, MuMu, LDPlayer) and sign in with your own Google account through the built-in Play Store. Download the emulator from the vendor's own site, avoid "modded" repacks, and keep it updated so you get security patches — the exact thing WSA no longer provides.