Microsoft pulled the plug. On March 5, 2025, Windows Subsystem for Android (WSA) and the Amazon Appstore disappeared from the Microsoft Store. No new downloads. No official support. The feature that let Windows 11 users run Android apps natively is dead — in its official form.

But for a determined subset of users, this isn't the end. Community-driven WSA builds, complete with Google Play Services and root access, have stepped into the void. And they just became the only practical way to keep Android apps alive on Windows.

The Official Timeline: How Microsoft Buried WSA

Microsoft's retreat started quietly. In March 2024, buried in a support document, the company announced it would deprecate WSA. No fanfare, no explainer — just a note that the subsystem would lose support on March 5, 2025, exactly one year later. The date arrived, and the Microsoft Store listings for WSA and the Amazon Appstore were delisted.

What does this mean for users who already had WSA installed? Existing installations continue to work. But no updates, no security patches, and no access to the Amazon Appstore for new app downloads. If you uninstall WSA after March 5, you can't get it back. The official channel is closed.

The deprecation blindsided many. WSA launched with Windows 11 in 2021 as a headline feature, built on Intel Bridge technology and a full Android 12 (later 13) environment. It integrated with Windows notifications, taskbar, and file system. But adoption never soared. The Amazon Appstore's limited selection — no Google Play — hamstrung the experience. Power users who wanted the full Android app ecosystem turned to sideloading APKs and, eventually, community mods.

Why Did Microsoft Kill WSA?

Microsoft never gave an explicit reason. The support doc simply states that "Microsoft is ending support for the Windows Subsystem for Android." But the writing was on the wall. Android app streaming via Phone Link already offered a tighter integration for Samsung users. Windows 11's AI features and Copilot integration have become the focus. And maintaining a whole Android subsystem — with kernel updates, security patches, and app compatibility — is expensive for a niche audience.

Amazon, too, seemed to lose interest. The Amazon Appstore on Windows remained a barren desert. Most major Android developers didn't bother. Why would they? Google Play dominates Android distribution. Without that, WSA was a curiosity, not a platform.

The Community Strikes Back: WSA Builds with Google Play and Root

Enter the enthusiasts. Long before the official deprecation, community developers had been modifying WSA to include Google Play Services, the Google Play Store, and root access. Projects like LSPosed's MagiskOnWSA (later renamed WSA-Script) and MustardChef's WSABuilds turned the official WSA package into a custom installer. These projects let users run almost any Android app, including those requiring Google services, with full superuser abilities.

After March 5, 2025, these community builds are no longer just a power-user tweak — they are the primary way to get Android apps on Windows. The equation shifted: you can no longer rely on Microsoft's store; you must use a third-party installer packaged by an unknown developer. That carries risk, but also possibility.

What Do These Builds Offer?

Community WSA builds typically deliver:
- Google Play Store: Full access to millions of Android apps, including those that depend on Google Play Services (Maps, Gmail, Drive, etc.)
- Root access: Magisk (or KernelSU) integration, allowing deep system modifications, ad-blocking, and advanced customization.
- OpenGApps or MindTheGapps: Bundled Google apps package to ensure compatibility.
- Automatic updates (unofficial): Some projects provide update scripts that fetch the latest WSA version from Microsoft's servers before the cutoff, but post-March 5 builds are frozen unless Microsoft releases a final image. However, community maintainers can still redistribute the last official build with modifications.

The most popular project, WSABuilds, offers a graphical installer and presets for different configurations (with/without root, different Android versions). It sources the official WSA image and applies modifications. Since the official download is no longer available, the project now relies on archived packages — a snapshot of the final build (2309.40000.8.0, based on Android 13).

Another notable project is WSA-Magisk, which focuses purely on root access and Magisk modules. Both require users to enable Developer Mode in Windows and sideload the modified package.

Should You Trust Community Builds? The Security Trade-Off

Let's be blunt: installing a modified system image from a stranger on the internet is a security risk. These projects are open-source, but that doesn't guarantee audit safety. A malicious actor could inject spyware into the image. Even well-intentioned maintainers may inadvertently bundle outdated binaries with known vulnerabilities.

Microsoft's official WSA ran in a Hyper-V sandbox, isolating it from the host OS. Community builds generally preserve that sandboxing, but root access and Google Services necessarily expand the attack surface. A malicious Android app could, in theory, exploit the subsystem to attack the Windows host if the Hyper-V boundaries are breached. Such exploits are rare but not unheard of.

For most users, the risk is acceptable. The community has rallied around these projects, with thousands of users and active GitHub issue trackers. The code is visible. But you're still placing trust in maintainers who could, at any moment, go rogue or get compromised.

How to Stay Safe

If you choose to use a community WSA build:
- Download only from the official GitHub repositories. Avoid random download sites.
- Check the latest release for integrity hashes and verify them if possible.
- Run the build in a Windows sandbox or isolated environment first to observe behavior.
- Keep your Windows installation updated and use Windows Security.
- Avoid providing sensitive information to Android apps running in this environment.

Installation: A Step-by-Step Overview

Getting community WSA up and running isn't trivial, but the process has matured. Here's a condensed guide using WSABuilds (as of March 2025):

  1. Enable Windows features: Turn on Virtual Machine Platform and Windows Hypervisor Platform from "Turn Windows features on or off."
  2. Enable Developer Mode: In Windows Settings > Privacy & security > For developers.
  3. Download the WSABuilds package from the project's GitHub releases page. Choose a variant (e.g., with Google Play Store and Magisk root).
  4. Extract the archive and run Run.bat as administrator. The script handles installation, including uninstalling any official WSA remnants.
  5. Wait for installation and launch the WSA Settings app to configure graphics and other options.
  6. Sign into Google Play and start installing apps.

The process often breaks due to Windows updates or missing dependencies. The community forums (Reddit, XDA Developers) are full of troubleshooting threads. Common issues include failed Hyper-V startup, network failures, and Google Play certification errors.

The Amazon Appstore Alternative Is Dead Too

Alongside WSA, the Amazon Appstore for Windows is gone. That storefront, which offered a curated selection of Android games and apps, was the official face of Android on Windows. Its removal means the few apps that were officially available — like TikTok, Kindle, and Subway Surfers — can no longer be installed through official means. Even those who had the Amazon Appstore installed may find it stops working, as its backend services may eventually shut down.

This leaves the community builds as the sole option for any Android app on Windows, regardless of source.

What About Existing Users? The Countdown to Bitrot

If you installed WSA before March 5 and never uninstall it, it will continue to function. But it's a ticking time bomb. Without updates, compatibility will degrade over time. Android apps update through the Play Store (if you sideloaded it), but the subsystem itself is frozen. A future Windows update could break it. Microsoft has not promised to keep it functional beyond the end-of-support date.

Apps that rely on specific Android API levels may eventually refuse to run. Security vulnerabilities will remain unpatched. Over time, the experience will become unstable. Most technically inclined users have already migrated to community builds to keep getting Play Services updates and root-level tweaks.

The Future: Will Android Apps on Windows Survive?

Microsoft's official line is that users should use phone mirroring via Phone Link. The company has invested heavily in making Android phone integration seamless, allowing you to run phone apps on your PC from a Samsung or select other Android devices. But that requires you own a compatible phone and have it nearby. It's not an independent app platform.

Google, for its part, has its own solution: Google Play Games on PC, a native Windows client that runs Android games on a virtual machine. It's limited to games and still in beta, but it shows Google's intent to own the Android-on-PC experience. Meanwhile, third-party emulators like BlueStacks and LDPlayer continue to thrive, though they lack the deep OS integration WSA offered.

The community will likely keep WSA on life support for years. As long as the installer scripts work and the final official image is available, enthusiasts can replicate the setup. Some developers are exploring ways to update the underlying Android framework independently, possibly using AOSP builds. But that's a colossal effort. For now, we're coasting on Microsoft's last release.

What Should Windows Users Do Now?

If Android apps are critical to your workflow, you have three paths:

  1. Embrace community builds: Accept the risks and install a modded WSA with Google Play and root. This gives you the most complete experience today.
  2. Use a third-party emulator: BlueStacks, NoxPlayer, or LDPlayer offer stable, often better-performing Android environments, though they don't feel as native as WSA.
  3. Rely on phone mirroring: Use Phone Link or Samsung DeX to run apps from your phone. This is the official Microsoft path but requires specific hardware.

None of these perfectly replicate the original vision of seamless Android apps on Windows. But the community, as always, fills the void.

Final Thoughts: The End of an Experiment

WSA was a bold experiment in marrying two operating systems. It worked surprisingly well, given the complexity. But the marriage was always uneasy — Android without Google is crippled, and Microsoft's partnership with Amazon couldn't fill the gap. The community picked up the slack, and now, with the official deprecation, it's the only torchbearer.

For tinkerers, this is a golden era. You can run Android apps with more power and flexibility than Microsoft ever allowed. For average users, though, the dream of native Android on Windows is effectively dead. The March 5, 2025, deadline wasn't just a date — it was the end of a promising, if flawed, feature. What rises in its place will be built by the people, not the platform.