WSABuilds      

MagiskOnWSA (For Windows™ 10 and 11)

Windows Subsystem For Android™ (WSA) with Google Play Services and (or) Magisk

 

Downloads

Note

To request a newer WSA build or a WSA build with a different version of GApps or Magisk (root) or a build without them (root or Google Play), feel free to open an issue in the Issues page.
Requested (Custom) Builds can be found by pressing the "Custom Build" button below.

Operating System	Download Page

 

❗ Important:   ⚠️DO NOT FORK⚠️
This repository is designed specifically not to be forked. MagiskOnWSA and some of the various forks and clones that have sprung up on the platform (potentially) violate GitHub's Terms of Service due to abuse of GitHub Actions and have been ultimately warned, disabled or banned.
We would like to say one thing: We respect the Terms and Conditions set out by Github to its users. MagiskOnWSA Builds are built using the MagiskOnWSALocal script, patched in the case of Windows 10 Builds and uploaded onto Github and hence do not rely on the use of Github Actions.
Therefore, don't fork this repository unless you're a developer and want to modify the code itself and/or want to contribute to this Github repository.

 

Before Continuing:

Warning

❗ Important:

Prebuilt WSA Builds for Windows™ 11 in Releases HAVE NOT been modified in anyway prior and subsequent to running the MagiskOnWSA script and upload to Github.

Prebuilt WSA Builds for Windows™ 10 in Releases ONLY have had AppxManifest.xml, icu.dll and WsaPatch.dll patched according to the WSAPatch guide before upload to Github.

The same level of scrutiny should be applied with the WSA builds as with any other program that you download from the internet

 

Requirements

- RAM: 6 GB (not recommended), 8 GB (minimum) and 16 GB (recommended).	- RAM: 6 GB (not recommended), 8 GB (minimum) and 16 GB (recommended).
- Processor: Your PC should meet the basic Windows™ 11 requirements i.e Core i3 8th Gen, Ryzen 3000, Snapdragon 8c, or above.	- Processor: N/A (This is a bit of a hit or miss)
- Processor type: x64 or ARM64.	- Processor type: x64 or ARM64.
- Virtual Machine Platform Enabled: This optional setting is for virtualization and you can enable the setting from Control Panel/ Optional Features.	- Virtual Machine Platform Enabled: This optional setting is for virtualization and you can enable the setting from Control Panel/ Optional Features.
- Storage: Solid-state drive (SSD) - Hard Disk Drive (HDD) (NOT RECOMMENDED).	- Storage: Solid-state drive (SSD) - Hard Disk Drive (HDD) (NOT RECOMMENDED).
- Partition: NTFS WSA can only be installed on a NTFS partition, not on an exFAT partition	- Partition: NTFS WSA can only be installed on a NTFS partition, not on an exFAT partition
- Windows™ 11: Build 22000.526 or higher.	- Windows™ 10: 22H2 10.0.19045.2311 or higher. - May work on Windows™ 10 21H2 10.0.19044.2311 However, MinVersion ---> TargetDeviceFamily node in AppxManifest.xml must be modified before trying
- The Computer must support virtualization and be enabled in BIOS/UEFI and Optional Features. Guide	- The Computer must support virtualization and be enabled in BIOS/UEFI and Optional Features. Guide

Installation

Note

: If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA.

In case you want to preserve your data from the previous installation (official or MagiskOnWSA), you can backup %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx before uninstallation and restore it after installation.

1. Go to the Releases page
2. In the latest release, go to the Assets section and download the WSA version of your choosing (do not download "Source code")
3. Extract the zip file
4. Delete the zip file
5. Move the newly extracted folder to a suitable location (Documents folder is a good choice), as you will need to keep the folder on your PC to use MagiskOnWSA

Note

:
If you're updating WSA, merge the folders and replace the files for all items when asked

6. Open the WSA folder: Search for and double-click Run.bat

   • If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous one while preserving all user data and install the new one, so don't worry about your data.
   • If the popup windows disappear without asking administrative permission and WSA is not installed successfully, you should manually run Install.ps1 as administrator:
     • Press Win+x and select Windows™ Terminal (Admin)
     • Input cd "{X:\path\to\your\extracted\folder}" and press enter, and remember to replace {X:\path\to\your\extracted\folder} including the {}, for example cd "D:\wsa"
     • Input PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1 and press enter
     • The script will run and WSA will be installed
     • If this workaround does not work, your PC is not supported for WSA

7. Once the installation process completes, WSA will launch (if this is a first-time install, a window asking for consent to diagnositic information will be shown instead. Sometimes two identical windows will show, this is fine and nothing bad happens if you click OK in both windows)

8. Click on the PowerShell window, then press any key on the keyboard, the PowerShell window should close

9. Close File Explorer

10. Enjoy

Notice (Applicable for both Windows 10 and 11):

1. You can NOT delete the WSA installation folder. What Add-AppxPackage -Register .\AppxManifest.xml does is to register an appx package with some existing unpackaged files, so you need to keep them as long as you want to use WSA. Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
2. You need to register your WSA appx package before you can run WSA. For WSABuilds and MagiskOnWSALocal users, you need to run Run.bat in the extracted dir. If the script fails, you can take the following steps for diagnosis (admin privilege required):
   1. Open a PowerShell window and change working directory to your WSA directory.
   2. Run Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.
   3. Run Get-AppPackageLog -ActivityID <UUID> in PowerShell. This should print the log of the failed operation.
   4. Check the log for the reason of failure and fix it.

Uninstallation

New CLI and GUI Uninstall Tool Coming Soon! Join the Discord for announcements and updates.

Note: If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder.

1. Go to the Start Menu
2. Type Windows Subsystem for Android
3. Once the WSA app shows, click App settings in the right pane
4. In the Settings window that opens, scroll down and click Terminate
5. Click Repair
6. Click Reset
7. Close the Settings app
8. Go to the Start Menu
9. Type Windows Subsystem for Android
10. Once the WSA app shows, click Uninstall in the right pane

FAQ

Help me, I am having problems with the MagiskOnWSA Builds

• Open an issue in Github or join the Discord and describe the issue with sufficent detail

Help me, I am having problems with installing WSA on Windows™ 10

• I am not working on the patch, and nor claim to. Open an issue in the Discord or Github, and I will try to assist you with the problem if possible. For full support visit the project homepage and open an issue there: https://github.com/cinit/WSAPatch/issues/

How do I get a logcat?

• adb logcat

or

• %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

Can I delete the installed folder?

• No.

How can I update WSA to a new version?

• As Explained Installation instructions. Download the latest WSA Version and replace the content of your previous installation and rerun Install.ps1. Don't worry, your data will be preserved

How do I update Magisk?

• Do the same as updating WSA. Wait for a new MagiskOnWSA release that includes the newer Magisk version, then follow the Installation instructions to update

Can I pass SafetyNet/Play Integrity?

• No. Virtual machines like WSA cannot pass these mechanisms on their own due to the lack of signing by Google. Passing requires more exotic (and untested) solutions like: https://github.com/kdrag0n/safetynet-fix/discussions/145#discussioncomment-2170917

What is virtualization?

• Virtualization is required to run virtual machines like WSA. Run.bat helps you enable it. After rebooting, re-run Run.bat to install WSA. If it's still not working, you have to enable virtualization in your BIOS/UEFI. Instructions vary by PC vendor, look for help online

Can I remount system partition as read-write?

• No. WSA is mounted as read-only by Hyper-V. You can, however, modify the system partition by creating a Magisk module, or by directly modifying the system.img file

I cannot adb connect localhost:58526

• Make sure developer mode is enabled. If the issue persists, check the IP address of WSA on the Settings ---> Developer page and try adb connect ip:5555

Magisk online module list is empty?

• Magisk actively removes the online module repository. You can install the module locally or by adb push module.zip /data/local/tmp and adb shell su -c magisk --install-module /data/local/tmp/module.zip

How do I uninstall Magisk?

• Request, using Issues, a WSA version that doesn't include Magisk from the Releases page. Then follow the Installation instructions

Can I switch between OpenGApps and MindTheGapps?

• No. GApps will no longer function. Do a complete uninstallation before switching

How do I install custom Magisk or GApps?

• You can achieve this by using the MagiskOnWSALocal Script and following the provided instructions located in the repo.

Credits

• Microsoft: For providing Windows Subsystem For Android™ and related files. Windows Subsystem For Android™, Windows Subsystem For Android™ Logo, Windows™ 10 and Windows™ 11 Logos are trademarks of Microsoft Corporation. Microsoft Corporation reserves all rights to these trademarks. By downloading and installing Windows Subsystem For Android™, you agree to the Terms and Conditions and Privacy Policy

• Cinit and the WSAPatch Guide: Many thanks for the comprehensive guide, files and support provided by Cinit and the contributers at the WSAPatch repository. Windows™ 10 Builds in this repo rely on the hard work of this project and hence credit is given where due
• StoreLib: API for downloading WSA
• Magisk: The Magic Mask for Android
• The Open Google Apps Project: Script the automatic generation of up-to-date Google Apps packages
• WSA-Kernel-SU: A kernel module to provide /system/xbin/su to Android Kernel
• Kernel Assisted Superuser: Kernel assisted means of gaining a root shell for Android
• WSAGAScript: The first GApps integration script for WSA
• MagiskOnWSA: Deprecated Integrate Magisk root and Google Apps into WSA
• MagiskOnWSALocal: Integrate Magisk root and Google Apps into WSA

The repository is provided as a utility.

Android is a trademark of Google LLC. Windows™ is a trademark of Microsoft LLC.