WSA Builds are community-maintained software packages that let you install and run Android apps directly on Windows. They modify the original Windows Subsystem for Android architecture to include the Google Play Store, Google Services, and optional root access.
Microsoft officially discontinued its native Android subsystem on March 5, 2025. When that happened, the official Amazon Appstore integration stopped functioning. Open-source developers, most notably projects like MustardChef on GitHub, stepped in to keep the architecture alive. These modified packages provide a direct way to run mobile games, messaging platforms, and smart-home dashboards natively on your desktop.
What Are WSA Builds?
Definition of WSA Builds
A community WSA build is a pre-packaged installer that bundles the core Windows hypervisor files with essential Android frameworks. Developers take the underlying system images and inject open-source Google app scripts before compressing them into a single executable package. This creates a ready-to-use virtual machine that installs via a Windows PowerShell script.
How WSA Builds differ from Microsoft’s official Windows Subsystem for Android
Microsoft’s original version restricted users to the Amazon Appstore. It deliberately excluded Google Play Services, causing apps that relied on Google accounts or location mapping to crash. Community versions bypass these restrictions. They modify the system to embed Google frameworks natively, fake device hardware signatures, and patch the installer to work on older Windows 10 systems.
Why WSA Builds became popular
Once Microsoft closed the official channel, PC users lost the ability to run mobile apps natively. These custom versions gained traction because they filled the immediate void. They provide an open, unrestricted environment that runs faster than standard emulators. Furthermore, native Hyper-V architecture typically consumes 40% to 50% less RAM than traditional software emulators, making it highly attractive for users with average hardware.
Who should use WSA Builds?
This setup suits casual users who want to run mobile-only social apps or smart-home controls directly from their taskbar. It also serves mobile developers who need to test application layouts locally without launching heavy Android Studio virtual devices.
Why People Choose WSA Builds
Access to Google Play Store
The Google Play Store remains the central hub for Android software. Custom packages integrate the store directly into the virtual environment. This gives you instant access to millions of applications that the original Microsoft-Amazon partnership ignored.
Built-in Google Services
Modern applications require Google Play Services to handle push notifications, secure logins, and in-app purchases. Without these background processes, apps fail to launch. Community packages embed frameworks like MindTheGapps, ensuring these background dependencies run quietly behind the scenes.
Magisk Root Support
Power users often require administrative system control. Custom packages offer pre-integrated root access via Magisk or KernelSU. This allows you to install system-level modules, manage file directories, and block ads globally—capabilities Microsoft strictly prohibited in the official release.
Better App Compatibility
Apps that check for standard device signatures run normally on these modified builds. Because the developers continuously update the underlying system images, compatibility rates remain high for streaming services, banking apps, and modern games.
Key Features of WSA Builds
Multiple Android Versions
You can select different Android operating system baselines depending on the repository you use. Developers typically offer Long-Term Support (LTS) releases based on Android 13 or newer, ensuring you meet the API requirements of current applications.
Google Play Integration
The installation scripts do more than just drop a store app on your desktop. They weave the Google service architecture into the core system partition. This means automatic background updates and account synchronization work exactly as they do on a physical phone.
Root and Non-Root Options
Security-conscious apps often refuse to open if they detect a rooted operating system. To solve this, developers release multiple variations. You can download a clean, non-rooted package for stable banking app usage, or a Magisk-enabled version for system modification.
Android Debug Bridge (ADB) Support
Wireless ADB functionality comes standard within the system settings dashboard. You can connect third-party management tools or push standalone app files directly into the virtual machine using simple command-line prompts.
Performance Optimizations
Instead of translating processor instructions purely through software, these packages talk directly to your physical hardware via Windows Hyper-V. This hardware-level integration is why native Hyper-V architecture typically consumes 40% to 50% less RAM than traditional software emulators.
System Requirements Before Installing WSA Builds
Supported Windows Versions
While Microsoft restricted its mobile layer strictly to Windows 11, developers successfully bypassed this limitation.
- Windows 11: Version 22H2 or newer (Build 22621+).
- Windows 10: Version 22H2 or newer (requires specific Windows 10 patched scripts).
Hardware Requirements
Virtualization requires specific hardware minimums to function smoothly.
- Processor: Intel Core i3 8th Gen, AMD Ryzen 3000 series, or equivalent ARM64 processor.
- RAM: 8 GB minimum; 16 GB recommended for multitasking.
- Storage: Solid State Drive (SSD). Traditional hard drives cause severe interface lag.
BIOS Virtualization Settings
Your motherboard must allow hardware virtualization. Restart your computer, enter the BIOS/UEFI screen, and enable the virtualization protocol.
- Intel: Look for Intel Virtualization Technology (VT-x).
- AMD: Look for SVM Mode.
Required Windows Features
The subsystem relies on native Windows modules. You must turn on the Virtual Machine Platform feature in the Windows Control Panel before running any installation scripts.
How to Download WSA Builds Safely
Choosing the Correct Build
Always download installation files from verified open-source repositories on GitHub, such as MustardChef’s releases. Avoid third-party tech blogs offering pre-extracted folders, as these often hide malware or unwanted browser extensions.
Selecting Android Version
Check the repository’s release page and look for the LTS (Long-Term Support) tag. LTS versions offer the most stable experience with the fewest graphical glitches.
Choosing Between Rooted and Non-Rooted Versions
Read the file names carefully before clicking download:
- WithGApps_Magisk: Includes the Play Store and root access.
- WithGApps_NoRoot: Includes the Play Store but leaves the system unrooted.
- NoGApps_NoRoot: A blank Android image with no Google services.
Verifying Download Authenticity
Once your .7z or .zip file finishes downloading, check its SHA-256 hash against the string provided on the GitHub page. This ensures the file did not corrupt during the transfer and remains unmodified.
Security Tips Before Installation
Never disable Windows Defender completely to install these packages. Legitimate community scripts run normally alongside standard security protocols. If a smart-screen prompt appears, verify the file origin before clicking “Run anyway.”
How to Install WSA Builds on Windows (Step-by-Step)
Step 1: Enable Virtualization
Restart your PC and press the BIOS key (usually F2 or Del). Locate your CPU settings and enable VT-x (Intel) or SVM (AMD). Save your changes and boot into Windows.
Step 2: Enable Required Windows Features
Type Windows Features into your Start menu search bar. Scroll down and check the box next to Virtual Machine Platform. Click OK and restart your computer when prompted.
Step 3: Download WSA Builds Package
Navigate to the GitHub repository. Download the package that matches your processor architecture (x64 for most users). Extract this compressed folder directly to the root of your primary drive (e.g., C:\WSA).
Step 4: Install the Package
Open your newly extracted folder. Locate the file named Run.bat. Right-click it and select Run as administrator. A blue terminal window will appear to register the system files.
Step 5: Configure Windows Subsystem for Android
Once the terminal finishes, the Android Settings dashboard will appear on your screen. Verify that the subsystem status indicates it is active.
Step 6: Sign in to Google Play Store
Open your Windows Start menu, find the Google Play Store icon, and open it. Enter your Google account credentials.
Step 7: Install Your First Android App
Search for a lightweight application inside the store. Click install. The system will create a native shortcut icon for that app directly in your Windows Start menu.
Initial Setup After Installation
Configure Developer Mode
Open the subsystem settings dashboard. Navigate to the advanced tab and turn on Developer Mode. This enables local network loopbacks, allowing you to use external debugging tools.
Allocate Resources
Change the memory setting from “As Needed” to a custom fixed amount. Dedicating 4 GB or 6 GB of RAM prevents the system from stuttering when you open a heavy mobile game.
Enable File Sharing
Turn on the file-sharing option in the configuration menu. This action maps your Windows user folders to the Android virtual storage directory, letting you easily share images and documents between the two environments.
Configure Networking
Switch your network connection mode to Advanced Networking. This assigns a dedicated local IP address to the Android layer, which is essential if you want to control local smart-home devices on your Wi-Fi network.
Update Google Play Services
Open the Play Store, click your profile icon, go to Settings, and select “Update Play Store.” This forces the background services to refresh and prevents older API errors.
How to Install Android Apps Using WSA Builds
Install from Google Play Store
The native store acts exactly like it does on a physical phone. Search for the app, click download, and the system handles the entire installation process in the background.
Install APK Files
For apps not hosted on the Play Store, download the APK file from a reputable site like APKMirror. You can install these files by downloading the WSA Sideloader utility from the Microsoft Store, which adds a simple double-click installation feature to your computer.
Install Apps Using ADB
Developers can use the terminal. Open a command prompt and type: adb connect 127.0.0.1:58526 followed by: adb install “C:\path\to\your\app.apk”
Install Third-Party App Stores
You can sideload alternative marketplaces like F-Droid or the Aurora Store. They run parallel to the Google Play Store and manage their own application updates without conflict.
Best Apps to Use with WSA Builds
Productivity Apps
Mobile versions of Microsoft To Do or Google Keep fit perfectly on a desktop screen. They use minimal resources and allow you to pin small, vertical reference windows next to your main browser.
Social Media Apps
Platforms like Instagram and TikTok offer poor desktop web experiences. Installing their native Android versions gives you the proper vertical interface and native push notifications on your Windows taskbar.
Streaming Apps
Certain streaming services cap video quality on web browsers to prevent piracy. The mobile applications often bypass these restrictions, allowing you to download episodes directly to your hard drive for offline viewing.
Educational Apps
Language apps like Duolingo or flashcard systems like AnkiDroid work excellently. You can place them on a secondary monitor and complete quick reviews between tasks.
Android Games
2D puzzle games and continuous base-builders run flawlessly. The subsystem maps mouse clicks to screen taps automatically, allowing you to play casual titles without heavy hardware strain.
Common WSA Builds Installation Errors and Solutions
Installation Failed
If the batch script closes immediately with an error, an old version of the official Microsoft subsystem likely exists on your computer. Navigate to your Windows Apps settings, uninstall any existing Android subsystem entry, and delete its residual files in your AppData folder.
Virtualization Not Enabled
This error means your motherboard is blocking the hypervisor. Double-check your BIOS settings to ensure VT-x or SVM is active, and confirm the Virtual Machine Platform feature is checked in Windows.
Google Play Store Not Working
If the store gets stuck on a loading screen, the Google account sync service has frozen. Open your Windows settings, find the subsystem app, click advanced options, and select Repair. This resets the connection without deleting your data.
Apps Keep Crashing
If apps open and immediately close, your specific Windows update might conflict with an older subsystem release. Download the latest LTS patch from GitHub and overwrite your existing files to apply the fix.
Black Screen Issues
A black application window indicates a graphics rendering failure. Open the subsystem settings and change the graphics preference from your integrated CPU graphics to your dedicated high-performance GPU.
Performance Tips for Better Experience
Allocate More RAM
Fixed memory allocation prevents lag spikes. If your computer has 16 GB of total RAM, restricting the subsystem to a permanent 6 GB block ensures mobile applications always have the space they need to function.
Enable SSD Storage
Virtual machines constantly read and write tiny database files. Running these files on a mechanical hard drive will cause your system to freeze. Always keep the installation folder on an internal SSD.
Keep Windows Updated
Microsoft frequently patches the underlying Virtual Machine Platform. Keeping your host operating system updated ensures the Android layer communicates efficiently with your physical hardware.
Optimize Graphics Settings
Enable direct hardware acceleration within the Android settings panel. Forcing the system to use your dedicated graphics card significantly improves frame rates in mobile games.
Reduce Background Processes
If you have limited hardware resources, close heavy desktop programs before launching demanding Android games. Freeing up CPU threads allows the hypervisor to process mobile code faster.
WSA Builds vs Official Windows Subsystem for Android
Features Comparison
The official version forced users into the Amazon ecosystem. The community version removes those locks, providing full Google Play compatibility, custom networking options, and root access.
Installation Difficulty
Microsoft offered a one-click install from its store. Custom builds require you to extract a folder and run a batch script manually. The trade-off is a few minutes of setup for a vastly superior platform.
Performance
Both versions rely on the same Windows Hyper-V backbone. However, community releases often feel faster because developers remove the heavy telemetry and diagnostic trackers Microsoft originally included.
Google Play Support
The official version permanently lacked Google Play support due to corporate licensing agreements. Community developers inject open-source Google frameworks to solve this problem entirely.
Security
Microsoft code-signed the official release. Custom builds require you to trust independent developers. Sticking to public GitHub repositories ensures thousands of other users regularly audit the open-source code.
Updates
Microsoft stopped updating the platform in 2025. Community developers continue to push updates, security patches, and bug fixes regularly.
WSA Builds vs Android Emulators
WSA Builds vs BlueStacks
BlueStacks runs inside a heavy application window and consumes significant resources. By contrast, the native Hyper-V architecture of WSA builds typically consumes 40% to 50% less RAM than traditional software emulators. Furthermore, subsystem apps sit directly on your taskbar as independent windows.
WSA Builds vs LDPlayer
LDPlayer optimizes heavily for gaming frame rates but includes desktop advertisements and promotional bloatware. Custom subsystem packages remain entirely clean and ad-free.
WSA Builds vs NoxPlayer
NoxPlayer features complex menus and high overhead. Subsystem packages integrate directly into Windows search, letting you open apps instantly without launching a separate interface first.
WSA Builds vs Android Studio Emulator
The official developer emulator accurately simulates phone hardware but runs sluggishly for casual use. Community builds prioritize speed and desktop integration over strict hardware simulation.
Which Option Should You Choose?
Choose custom subsystem builds for lightweight productivity, clean taskbar integration, and low memory usage. Choose traditional emulators only if you require complex multi-touch macro scripts for competitive mobile gaming.
Is WSA Builds Safe to Use?
Security Considerations
The primary GitHub projects do not contain malware. The build scripts simply download official system images, add open-source Google files, and package them together on your local machine.
Privacy
These custom builds respect your privacy better than commercial emulators. They do not inject advertisements or track your desktop usage. You control the telemetry settings directly within the Android dashboard.
Risks of Modified Builds
The only real danger comes from downloading pre-compiled files from random YouTube descriptions or file-sharing forums. Always source your files directly from established GitHub repositories.
Best Practices for Safe Usage
Log into the Play Store using a secondary Google account if you are concerned about data exposure. Run standard Windows Defender scans on your installation folder after applying any new updates.
How to Update WSA Builds
Check for New Releases
Visit the GitHub project page periodically. Look for new release tags under the LTS branch to ensure you get the most stable updates.
Backup Existing Installation
Before applying an update, open your installation folder (e.g., C:\WSA) and copy the userdata.vhdx file to your desktop. This single virtual disk holds all your downloaded apps and saved data.
Update Without Losing Apps
Extract the newly downloaded update folder. Delete all the files in your active installation directory except your original userdata.vhdx file. Move the new files in, and run the Run.bat script as an administrator to apply the patch.
Verify Successful Update
Open the Android settings dashboard and check the version number at the top. If it matches the new release, the update applied correctly.
Troubleshooting Guide
WSA Doesn’t Start
Open the Windows Services menu (services.msc). Locate the HV Host Service. Change its startup type to Automatic. The subsystem cannot boot if this background service is disabled.
Google Play Login Problems
If the store rejects your password or throws a network error, check your Windows system clock. A misaligned clock prevents Google’s authentication servers from verifying your secure connection.
Internet Connection Issues
If apps open but show no network access, open the subsystem settings. Disable Advanced Networking. Reverting to the default NAT connection bypasses strict Windows firewall rules that occasionally block bridged connections.
ADB Not Detecting Device
If your command prompt reads “device offline,” ensure Developer Mode is active in the settings. Run adb kill-server in your terminal, then run the connect command again to refresh the local bridge.
App Compatibility Problems
Apps utilizing strict anti-cheat software often crash on rooted devices. If you rely on these specific apps, you must uninstall the Magisk version and install a clean NoRoot build instead.
Advantages and Limitations of WSA Builds
Pros
- Mobile apps function exactly like native Windows software.
- Extremely low system resource usage compared to emulators.
- Full access to the Google Play Store and Google Services.
- No integrated advertisements or bloatware.
Cons
- Requires manual file extraction and script execution.
- No support for running multiple instances of the same app simultaneously.
- Dependent on community maintenance since Microsoft abandoned the core code.
Best Alternatives to WSA Builds
Official Windows Subsystem for Android
This option no longer exists. Microsoft removed the files from its store and officially terminated the project.
BlueStacks
The standard choice for heavy mobile gamers. It provides excellent keyboard mapping tools but consumes heavy CPU and RAM resources.
LDPlayer
A solid alternative for low-end PCs that struggle with Hyper-V. It runs games well but includes heavy corporate branding.
Android Studio Emulator
The best choice for software developers writing original code, though far too slow and complicated for everyday consumer use.
Waydroid (Linux)
If you operate a Linux machine, Waydroid runs mobile apps directly on the Linux kernel with zero emulation overhead, providing the fastest possible performance.
Frequently Asked Questions (FAQ)
What are WSA Builds?
They are community-maintained installation scripts that configure the Windows Subsystem for Android to run with full Google Play Store support and optional root access.
Are WSA Builds free?
Yes. The projects rely entirely on open-source code and are free to download from GitHub.
Is WSA Builds safe?
Yes, as long as you download the files strictly from verified public GitHub repositories. Avoid third-party mirrors.
Does WSA Builds include Google Play Store?
Yes. Packages labeled with “GApps” include the full Google Play Store and the necessary background services required to run modern apps.
Can I install APK files?
Yes. You can install standalone APK files via the command line or by using a sideloading helper app from the Microsoft Store.
Does WSA Builds support Windows 11?
Yes, it functions correctly on all modern versions of Windows 11 (Build 22621 and higher).
Can Windows 10 run WSA Builds?
Yes. Community developers applied specific patches to the installation scripts, allowing the subsystem to run natively on Windows 10 (Version 22H2 and higher).
Final Thoughts
Key takeaways
Community-driven packages rescued native mobile app support on PC after Microsoft abandoned the project. By injecting Google Play Services and removing arbitrary software locks, these custom files provide a superior desktop mobile experience.
Who should use WSA Builds?
This setup serves users who want a distraction-free way to run mobile tools, messaging platforms, and casual games without the heavy resource tax of standard emulation software.
When WSA Builds is the right choice
It remains the best choice when you value system efficiency. Because the native Hyper-V architecture typically consumes 40% to 50% less RAM than traditional software emulators, it keeps your host PC running smoothly while managing mobile tasks in the background.
Practical next steps for getting started
To begin, verify that hardware Virtualization is active in your BIOS. Enable the Virtual Machine Platform feature in Windows, and visit a trusted GitHub repository to download your chosen installation package.