Microsoft has officially ended support for the Windows Subsystem for Android (WSA) on March 5, 2025. That means the Amazon Appstore is gone from the Microsoft Store, and no new Android apps can be installed on Windows 11 through the official channel. Existing installations may still work, but they're now unsupported and won't receive security updates.

For the millions who dipped into this feature—or built workflows around it—the clock has run out. Here's exactly what changed, who it affects, and what to do next.

The March 5 Shutdown: What's Gone for Good

On March 5, 2025, Microsoft flipped the switch. The Windows Subsystem for Android—the AOSP-based runtime that let Android apps run inside a Hyper-V virtual machine on Windows 11—stopped receiving support. The Amazon Appstore, the only official distribution channel for those apps, was pulled from the Microsoft Store a year earlier (discovery ended March 6, 2024). After that date, new users couldn't install the Appstore at all. Existing users could keep using their apps until the deprecation date, but now that's passed.

The practical implications are stark:

  • You can no longer install the Amazon Appstore from the Store—it simply isn't there.
  • Any Android apps you had pinned to Start or Taskbar might still launch, but they're frozen in time: no app updates, no security patches, no official support.
  • Integration features—clipboard sharing, notifications in Action Center, Snap layouts, Alt+Tab—still work where applicable, but they're running on borrowed time as Windows evolves.
  • The WSA settings entry in Windows remains, but its usefulness is nil without active app management.

Microsoft and Amazon coordinated a "smooth end of support experience," but that phrasing undersells the reality: the feature is dead, and any reliance on it now carries risk.

Who's Affected—and How Much It Hurts

The impact cuts across three groups: home users, IT administrators, and developers.

Home Users and Power Users

If you grabbed a few Android games or productivity apps from the Amazon Appstore, you can likely still use them for now—but you're on your own. The apps won't update, so if a security flaw is discovered, you won't get a fix. Over time, apps may break as Windows changes or as the apps themselves phase out older Android versions.

Power users who sideloaded APKs directly into WSA face the same cliff. Without an officially supported runtime, maintaining a secure Android environment on Windows becomes a manual, fragile chore.

IT Administrators

Any organization that baked Android apps into a workflow—say, a custom line-of-business tool only available via Amazon's store—now faces an urgent migration. The deprecated runtime is an unsupported attack surface; it shouldn't remain on managed devices. Beyond the security risk, there's a compliance problem: running unpatched software can violate internal policies or regulatory requirements.

For admins, the immediate task is to inventory and remediate:

  • Identify all Windows 11 devices with WSA installed (check via PowerShell or endpoint management tools).
  • Remove WSA and the Amazon Appstore from these devices.
  • Redirect users to supported alternatives (native Windows apps, web apps, or sanctioned emulators).

Developers

Developers who published Android apps to the Amazon Appstore for Windows lost a distribution channel. Amazon closed submissions for Windows targets after the deprecation announcement and limited update windows. If you maintained an Android app primarily for Windows users, that audience evaporated.

The path forward isn't to lament but to adopt Microsoft's new cross-device framework: the Continuity SDK. This lets an Android app hand off its activity to a native Windows app, enabling a seamless "resume" experience. It's developer-driven and requires building a companion Windows app—but it's the only official way to keep a mobile-to-desktop bridge alive in the Microsoft ecosystem.

A Brief History: From Launch Hype to Quiet Exit

When Windows 11 was announced in June 2021, the ability to run Android apps was one of its most attention-grabbing features. Microsoft promised Android apps would "feel like part of Windows": they'd appear in the Start menu, integrate with Snap layouts, and support keyboard, mouse, and pen input.

The reality, however, came with more asterisks than a baseball record book.

  • Early Access was a maze. You had to enroll in the Windows Insider Program (Beta Channel), set your PC region to the United States, and hold a U.S. Amazon account. Even then, hardware virtualization support (BIOS/UEFI, Virtual Machine Platform, Hypervisor Platform) was mandatory.
  • The catalog was a fraction of Google Play. Microsoft partnered with Amazon, not Google, so the Appstore's curated selection lacked many popular apps. Power users quickly discovered the gaps.
  • Performance was a mixed bag. Intel Bridge Technology translated Arm-compiled Android binaries to x86 at runtime, and while it was clever, apps with DRM, anti-tamper protections, or architecture-specific libraries often stumbled.

Despite these hurdles, the technical feat of running Android apps in a secure, isolated Hyper-V VM with deep Windows integration was impressive. It just wasn't enough to build a lasting platform on.

Microsoft's March 2024 announcement of the impending deprecation felt abrupt but not surprising. Managing an entire Android runtime in Windows was resource-intensive, and the partnership with Amazon never scaled to meet user expectations. Microsoft pivoted to a lighter-weight, developer-centric model: Cross Device Resume.

Your Action Plan: Next Steps for Homes, Offices, and Developers

The deprecation doesn't mean you can't use Android apps on Windows at all—it means you need a new strategy.

If You're a Home User

  1. Audit what you have. Make a list of Android apps installed via the Amazon Appstore. Back up any app-specific data (saved files, login credentials).
  2. Find native replacements. Search the Microsoft Store or the web for Windows-native equivalents or progressive web apps (PWAs). Many Android apps have web versions that work just as well.
  3. If you must run Android apps, consider a third-party emulator like BlueStacks or Nox. These are consumer-grade and often ad-supported, but they're actively maintained and offer broader app compatibility. Be mindful of security: only install trusted apps.

If You're an IT Administrator

  1. Remove WSA from managed devices. Use Intune or Group Policy to uninstall Windows Subsystem for Android and the Amazon Appstore.
  2. Block sideloading. Prevent users from installing unsupported Android runtimes; enforce application whitelisting.
  3. Communicate the change. Let users know their Android apps are going away and provide a list of approved alternatives.

If You're a Developer

  1. Explore the Continuity SDK. Apply for limited access to the Link to Windows APIs and integrate cross-device resume into your Android and Windows apps. This is the official replacement for the old WSA-based integration.
  2. Build a native Windows companion. Even a lightweight PWA or WinUI app that receives handoff from your mobile app can keep your users in the Microsoft ecosystem.

Where Microsoft Is Going Instead

The shutdown of WSA isn't a retreat from cross-device ambition—it's a redirection. Microsoft is betting on "Resume," formally known as Cross Device Resume (XDR), which lets you start an activity on your phone and continue it seamlessly in a native Windows app. The feature is already visible in Phone Link and is part of a broader vision to make Windows the center of your digital life without hosting foreign runtimes.

This approach is more sustainable. It doesn't require maintaining an entire Android stack, and it puts the onus on developers to create native Windows experiences. The tradeoff is that you won't be able to run just any Android app on your PC; you'll be limited to those with companion Windows apps.

For users, the lesson is clear: platform features built on third-party dependencies can vanish. The convenience of Android on Windows was real, but it was always on shaky ground. Moving forward, build your workflows on tools that have a clear, long-term support horizon—native Windows apps, web apps, and solutions from vendors with a track record of commitment.

The Android-on-Windows experiment was a fascinating technical achievement, but its lifespan was short. March 5, 2025, marks the official end. What comes next depends on how quickly users, IT managers, and developers adapt to a world where the bridge between phone and PC is built differently.