Windows Subsystem For Android May 2026
As of April 2026, the Windows Subsystem for Android (WSA) has been officially retired by Microsoft. Support for the feature ended on March 5, 2025
, and the Amazon Appstore was removed from the Microsoft Store.
While the official path is closed, you can still use Android apps on Windows 11 through community-driven methods or official alternatives. 1. The Community "Fix": WSA Builds
Although Microsoft no longer offers WSA, independent developers maintain WSA Builds on GitHub. These custom packages often include the Google Play Store , which was never officially supported by Microsoft. How to Install in 2026: Enable Virtualization : Search for "Turn Windows features on or off" and enable Virtual Machine Platform . Restart your PC. Turn on Developer Mode Settings > System > For developers and toggle "Developer Mode" to ON. Download a Build
: Find a reputable repository (like "WSA Builds") on GitHub and download the latest stable release. Run the Installer : Extract the ZIP file, right-click install.bat ), and select Run as Administrator windows subsystem for android
: Once the process finishes, the Play Store will appear in your Start menu. Log in with your Google account to download apps.
Newer Windows 11 updates have occasionally broken these custom builds. If your apps start crashing after a system update, you may need to download a newer community patch.
The Windows Subsystem for Android (WSA) was a major feature of Windows 11 that allowed users to run Android applications natively on their PCs. However, Microsoft officially ended support for the service on March 5, 2025. Current Status and Deprecation
Support Status: Microsoft and Amazon have removed the Amazon Appstore and the WSA from the Microsoft Store. As of April 2026, the Windows Subsystem for
Existing Installations: If you had WSA installed before March 5, 2025, it may still function, but it no longer receives technical support, security patches, or feature updates from Microsoft.
Performance Issues: Recent Windows updates (such as KB5064081) have been reported to break compatibility for remaining WSA installations. Key Features (Pre-Deprecation)
The Architecture Breakdown
To understand WSA, you must understand its three main pillars:
- The Hypervisor Foundation: WSA ran inside a lightweight virtual machine (VM) using Windows’ native Hyper-V platform. Unlike VirtualBox or VMware, this VM was optimized for graphics and input latency.
- The AOSP Environment: Microsoft took the Android 13 (initially Android 11) open-source code and modified it heavily. They stripped out Google Mobile Services (GMS)—meaning no native Play Store, Google Maps APIs, or Firebase Cloud Messaging.
- The Integration Layer: This was the magic. WSA mapped Android intents to Windows protocols. Click a link in an Android app? It opens in your default Windows browser. Receive a notification on your phone? WSA piped it directly into the Windows Action Center.
Part 2: The Rise of WSA (2021–2023)
When Microsoft first announced WSA at the June 2021 Windows event, the reaction was electric. The demo showing a TikTok video pinned to the Windows taskbar alongside Excel and Teams felt like the future of productivity. The Architecture Breakdown To understand WSA, you must
3. The Amazon Partnership (The "Why Not Google Play")
Out of the box, WSA comes with Amazon Appstore. Why? Licensing and legal safe harbor. Google Play Services (GMS) are proprietary, and Microsoft would technically have to license GMS per PC. Amazon’s store is the simpler, legal foot in the door.
Interesting note: Users quickly found ways to sideload Google Play Services (see the "Advanced" section below), turning WSA into a near-full Android tablet experience.
The "Google Play" Hack (For the brave)
- GitHub projects like WSA Magisk or WSAGAScript automate patching WSA to include:
- Google Play Services
- Magisk (root)
- Full Google Play Store
- Risk: Breaks on WSA updates, potential account ban (Google doesn't love this).
Part 5: Why You Should Care – The Legacy of WSA
Even though WSA is gone, its influence remains. Microsoft learned three valuable lessons that will shape Windows 12 (codenamed "Hudson Valley," expected 2027):
B. Binary Translation & App Virtualization
The concept of running apps compiled for one OS on another is a mature field of study.
- Paper: DAIKON: A System for Dynamically Translating Android Applications (Not a Microsoft paper, but relevant to the field).
- Context: This explores how Android apps can be translated or virtualized on different architectures.
- Paper: BlueDroid: Running Android Apps on Windows Phone (Research Project).
- Context: Before WSA, researchers attempted to run Android apps on Windows Phone. The challenges outlined in these papers (graphical driver translation, binder IPC) are exactly what Microsoft solved in WSA using DX12 translation layers.
What Was Windows Subsystem for Android?
Announced in 2021 and released with Windows 11, WSA was a compatibility layer that enabled the Windows kernel to run Android’s operating system environment. Think of it as the Android counterpart to the Windows Subsystem for Linux (WSL).
Key features included:
- Native integration – Android apps could be pinned to the Start menu, appear in search, and run in resizable windows.
- Hardware acceleration – Used your PC’s GPU for smooth graphics.
- File system sharing – Android apps could access Windows documents, pictures, and downloads (with permission).
- Camera & microphone pass-through – Zoom, Snapchat, or Instagram could use your PC’s hardware.
- Amazon Appstore integration – Microsoft partnered with Amazon rather than Google.