Let’s be honest: the idea of running Android apps on your Windows PC is fantastic. But the execution? Historically, it’s been a bit messy. The official Windows Subsystem for Android (WSA) from the Microsoft Store had potential, but it lacked the Google Play Store, didn’t support root, and—crucially—Microsoft has officially discontinued it.

But don’t worry. If you are sitting there wishing you could play mobile games on your big monitor or develop apps with root access, I have the perfect solution for you: WSABuilds.

Maintained by the open-source hero MustardChef, this project is the “unshackled” version of WSA. It’s powerful, customizable, and yes, it runs on both Windows 10 and 11. Grab a coffee, and let me walk you through exactly how to set this up.

What is WSABuilds and why should you care?

Think of WSABuilds as the “Pro” version of the standard Android subsystem. Instead of a locked-down container, you get a fully functional Android environment with the features enthusiasts actually want.

Unlike the official release, WSABuilds offers optimized prebuilt binaries that solve the biggest pain points of emulation. Here is why it is superior:

1. The Google Play Store is built-in

This is the game-changer. You don’t need to sideload APKs manually or mess around with complex scripts to get GApps.

  • Seamless: Install apps directly from the Play Store just like on your phone.
  • Services: Full support for Google Play Services ensures apps like YouTube, Maps, and Gmail work correctly.

2. Root access via Magisk

For the power users reading this, yes, you get full root access.

  • Control: Safely manage root permissions.
  • Modules: Install Magisk modules to change fonts, block ads, or tweak system performance.
  • Compatibility: Essential for apps that require admin-level privileges.

3. KernelSU integration

If you prefer a stealthier approach to rooting, WSABuilds offers KernelSU.

  • Kernel-level: Root access is managed at the kernel level, not the userspace.
  • Stealth: It offers significantly better detection evasion compared to traditional root methods, which is great for apps that try to block rooted devices.

4. Flexible versions

You are not stuck with one update channel. You can choose:

  • LTS (Long Term Support): If you want stability and don’t want things to break.
  • Non-LTS: If you want the bleeding edge features (updated frequently).
  • NoGApps: A lightweight version if you just want pure Android without Google’s bloatware.

System requirements check

Before we dive into the installation, let’s make sure your rig can handle this. It’s not too demanding, but specific requirements must be met.

Operating system

  • Windows 11: Build 22000.526 or higher (This is the recommended path).
  • Windows 10: Version 22H2 (Build 10.0.19045.2311 or higher). Yes, Windows 10 users, you are invited to the party too.

Hardware specs

  • Processor: x86_64 or ARM64. Basically, any Intel Core i3 8th Gen (or newer) or AMD Ryzen 3000 series (or newer).
  • RAM: 8GB is the absolute minimum, but believe me, you want 16GB for a smooth experience.
  • Storage: You need an SSD. Do not try this on an HDD. You need at least 10GB free on your C:\ drive (NTFS format).
  • GPU: Any modern GPU works. Just avoid very old integrated graphics like Intel HD 530.

Essential Windows features

You need to enable virtualization at the OS level. Here is the quick way to do it:

  1. Press Windows + R on your keyboard.
  2. Type OptionalFeatures.exe and hit Enter.
  3. Look for Virtual Machine Platform and Windows Hypervisor Platform.
  4. Check both boxes and click Apply. You will likely need to restart your PC.

Pro Tip: Make sure “Virtualization” is also enabled in your motherboard’s BIOS/UEFI settings.

Installation guide: Step-by-step

We are going to do this manually to ensure it is done right. It is actually quite simple if you follow these steps precisely.

Step 1: Download your preferred version

Head over to the WSABuilds Releases page. You will see a lot of assets, so here is how to pick:

  • Want the Play Store? Look for files with “GApps” in the name.
  • Want Root? Most GApps builds now include Magisk or KernelSU automatically.
  • Win 10 vs 11: Download the .7z file that matches your Windows version.

Step 2: Extract and prepare the folder

This step is critical. Many users fail here because of long file paths.

  1. Use 7-Zip or WinRAR to extract the downloaded file.
  2. Crucial: Once extracted, rename the resulting folder to simply WSA.
    • Why? Windows has a path length limit. A folder name like WSA_2307.40000.5.0_x64_Release-Nightly... is too long and will cause the installation to fail.
  3. Move this WSA folder to a root directory or somewhere simple, like C:\WSA or your Documents folder.
  4. You can now delete the original .7z file to save space.

Step 3: Run the installation script

Now, let’s fire it up.

Method 1: The easy way (File Explorer)

  1. Open your WSA folder.
  2. Find the file named Run.bat.
  3. Double-click it.
  4. If Windows asks for permission (UAC), click Yes to grant Administrator privileges.
  5. A blue command window will pop up. Let it do its thing.

Method 2: The reliable way (PowerShell)
If Run.bat closes immediately or doesn’t work, do this:

  1. Press Windows + X and select Terminal (Admin) or PowerShell (Admin).
  2. Type the following commands (replace “path_to_WSA_folder” with your actual folder location):
    powershell cd "path_to_WSA_folder" PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1
  3. Press Enter.

Step 4: Finalization

  1. Once the script finishes, you will see a message saying “Press any key to quit”. Go ahead and press a key.
  2. Close any popup windows that appeared.
  3. Windows Subsystem for Android should launch automatically.
  4. Open your Start menu, look for Play Store, sign in, and you are good to go!

Updating WSA without data loss

This is one of the best features of WSABuilds. You don’t need to wipe your data to get the latest Android updates.

  1. Shutdown WSA: Open the WSA Settings app and click “Turn off”. Wait until it’s completely stopped.
  2. Download: Get the new version .7z file from GitHub.
  3. Extract: Open the archive.
  4. Copy: Go into the inner folder of the new download, select all files, and drag them into your existing installed WSA folder.
  5. Overwrite: When Windows asks, choose “Replace the files in the destination”.
  6. Re-run: Double-click Run.bat again to register the updated components.
  7. Verify: Open WSA Settings → About to check the version number.

Your apps, logins, and game saves will be exactly where you left them.

Backup and restore data

Paranoid about losing your game progress? You should be. Here is how to manually back up your entire Android instance.

How to backup

The entire Android “disk” is stored in a single virtual hard drive file.

  1. Navigate to this folder path (you can paste this into the Run dialog or File Explorer address bar):
%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\
  1. Look for a file named userdata.vhdx.
    • Note: It might be named userdata.2.vhdx or userdata.3.vhdx depending on previous installs. Just look for the file that is several GBs in size.
  2. Copy this file to a USB drive or cloud storage. That is your backup.

How to restore

  1. Uninstall your current WSA if needed.
  2. Perform a fresh installation (Steps 1-3 from the Installation Guide).
  3. Before you launch the Play Store for the first time, copy your backup userdata.vhdx back into the folder path mentioned above.
  4. Run Run.bat again just to be safe.
  5. Launch WSA. It will load your old data perfectly.

Troubleshooting common issues

Even the best software has hiccups. Here are the fixes for the most common problems I have seen.

“The folder name is too long”

If the installation crashes instantly, it is almost always because you didn’t rename the folder.
Fix: Rename your extracted folder to WSA and move it to C:\.

WSA won’t start after a Windows Update

Recent Windows updates (especially post-July 2025) have tweaked virtualization protocols which can break older WSA builds.
Fix: Upgrade to the latest LTS version of WSABuilds. If that fails, try the NoGApps version to rule out Google compatibility issues.

Magisk modules disappear after reboot

This is a known quirk with unstable builds.
Fix: Switch to an LTS (Long Term Support) build. They are tested more thoroughly for root stability.

GPU or graphics glitches

If apps are flickering or WSA refuses to launch while you have an NVIDIA card:
Fix:

  1. Go to Windows Graphics Settings.
  2. Force WSA to use your Intel iGPU or AMD GPU instead of the NVIDIA one.
  3. Alternatively, inside WSA Settings, change the graphics driver to Microsoft Basic Renderer (it’s slower, but stable).

What works and what doesn’t?

Let’s manage expectations. This is virtualization, not a native phone.

✅ Working well

  • Social Media: Facebook, TikTok, Instagram, and Zalo run smoothly.
  • Streaming: Spotify, YouTube, and Netflix work great (though Netflix typically won’t play in 4K due to DRM).
  • Productivity: Microsoft Office Android apps and Duolingo.
  • Integration: Features like Virtual Wi-Fi, Multi-touch, and shared Clipboard (Copy/Paste between Windows and Android) are flawless.

⚠️ May require workarounds

  • Banking Apps: Because the device is rooted and virtualized, many banking apps will block access. You will need to use Magisk Hide or Zygisk to try and bypass this, but it’s not guaranteed.
  • Heavy Gaming: While OpenGL ES 3.0 and Vulkan are supported, very heavy 3D games might have texture glitches.

❌ Not supported

  • Bluetooth: WSA cannot access your PC’s Bluetooth adapter directly. You cannot connect a smartwatch or fitness tracker to an app inside WSA.
  • Physical Hardware: No fingerprint sensors or NFC.
  • SafetyNet: While KernelSU helps, passing strict SafetyNet/Play Integrity checks is extremely difficult on a virtual machine.

LTS vs Non-LTS: Which should you pick?

AspectLTS (Recommended)Non-LTS
StabilityHigh (Field tested)Moderate (Experimental)
UpdatesMonthlyWeekly
Android BaseOlder, proven stableLatest AOSP features
Root StabilityHigh reliabilityVariable
Best for…Daily usersDevelopers & Tinkerers

My advice: Start with LTS. Only switch to Non-LTS if there is a specific new feature you desperately need.

Final thoughts

WSABuilds is practically a miracle for Windows users. Even though Microsoft officially pulled the plug on WSA on March 5, 2025, the open-source community has kept the dream alive—and improved it.

Whether you are a developer needing a test bench, a gamer wanting to grind mobile MMORPGs on a PC, or just someone who wants TikTok on a second monitor, this is the way to do it.

Ready to get started? Download the latest build and give your PC a serious upgrade.

You may also like

Subscribe
Notify of
guest

0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments