Integrate Magisk root and Google Apps into WSA (Windows Subsystem for Android) and make it run on Win10 with GitHub Actions
AGPL-3.0 License
Download latest release here, and find all builds here
Note : If you have the official Windows Subsystem For Android™ 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. For a more comprehensive and detailed guide, take a look at the Backup and Restore section
Note : If you want to build your custom build, please open an Issue,and then download the Artifact from Github Actions. Please visit Custom Build for more information.
Check integrity of downloaded file
cd "{X:\path\to\your\downloaded\archive\package}"
WSA_2XXX.XXXXX.X.X_XXXX_Release-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X
with the name of the archive packagecertutil -hashfile "WSA_2XXX.XXXXX.X.X_XXXX_Release-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X" SHA256
Note : If package don't have the same SHA-256 Hash, please download then check again. DO NOT INSTALL!!!
Extract the zip file
Delete the zip file
Move the newly extracted folder to a suitable location and rename it (Recommended), as you will need to keep the folder on your PC to use WSAOnWin10
Note : If you're updating WSA, merge the folders and replace the files for all items when asked. Please visit Updating instructions for more information.
Open the Windows Subsystem For Android™ 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 Windows Subsystem For Android™ is not installed successfully, you should manually run Install.ps1 as administrator:
Press Win+X
and select Windows™ Terminal (Admin)
Input the command below and press enter, replacing {X:\path\to\your\extracted\folder} including the {} with the path of the extracted folder
cd "{X:\path\to\your\extracted\folder}"
Input the command below and press enter
PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1
The script will run and Windows Subsystem For Android™ will be installed
If this workaround does not work, your PC is not supported for WSA
Once the installation process completes, Windows Subsystem For Android™ 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)
Click on the PowerShell window, then press any key on the keyboard, the PowerShell window should close
Close File Explorer
Enjoy
You can NOT delete the Windows Subsystem For Android™ 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 Windows Subsystem For Android™.
Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
You need to register your Windows Subsystem For Android™ appx package before you can run Windows Subsystem For Android™.
For WSAOnWin10 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):
Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.
Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
Run the command below in PowerShell. This should print the log of the failed operation.
Get-AppPackageLog -ActivityID <UUID>
Check the log for the reason of failure and fix it.
Run.bat
fileAbout
tab using the sidebarNote:
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%\Package\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache
folder. For a more comprehensive and detailed guide, take a look at the Backup and Restore section in this README markdown
To remove WSA installed:
1.) Make sure that Windows Subsystem For Android™ is not running
2.) Search for Windows Subsystem For Android™ Settings
using the built-in Windows Search, or through Add and Remove Programs and press uninstall
3.) Delete the WSA folder that extracted you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)
4.) Go to %LOCALAPPDATA%/Packages/
and delete the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe
To remove WSA installed from the Microsoft Store:
Windows Subsystem For Android™ Settings
using the built-in Windows Search, or through Add and Remove Programs and press uninstallIn order to make a backup of your WSA data you must copy the Userdata.vhdx (which includes, but is not limited Android Apps and their data, settings etc.), located at %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx
, to a safe location
Before attempting to restore your backup, you must remove WSA if installed. Then before you run the "Run.bat" script (to reinstall WSA after removing it), you need to remove these lines from Install.ps1:
Start-Process "wsa://com.topjohnwu.magisk"
Start-Process "wsa://com.android.vending"
Start-Process "wsa://com.amazon.venezia"
Start-Process "wsa://com.android.settings"
After running the script, DO NOT RUN WSA at all, and go to %localappdata%\Packages
and (if the folders do not exist, create them) in MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\
paste the userdata.vhdx
Now run WSA and your serdata should hopefully be restored
❗ 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. |
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. |
If you want to create your Custom Build, please follow the instructions set out clearly, to avoid the repo from being taken down as a result of a misuse of Github Actions due to the large number of forks. AND ALSO if you want to build with Latest Insider version, please skip the first 7 steps |
DO NOT download it via multithread downloaders like IDM
icu.dll
and winhttp.dll
from Windows 11 images
icu.dll
andwinhttp.dll
in Windows 11 images are the key to WSA running on Windows 10, because some functions do not exist the above dll files in Windows 10 images. All builds provided by this repository already contain the dll files mentioned above, as well as' WSAPatch.dll ', so you can ignore this section if you are just using the builds provided by this repository
This repository uses Issues and Github Actions to automatically fetch dll files in Windows 11 images and inject 'WSAPatch.dll'. Visit this link to see the dll files already in the repository. If you wish to submit an updated dll file, follow these steps
Note Please do not upload the dll file arbitrarily, and fill in the information correctly
If you cannot provide the link of Windows 11 images, please fetch
icu.dll
andwinhttp.dll
manually, and then open a pull request.
Help me, I am having problems with the MagiskOnWSA Builds
Help me, I am having problems with installing Windows Subsystem For Android™ on Windows™ 10
How do I get a logcat?
There are two ways:
adb logcat
or
Location in Windows ---> %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat
Can I delete the installed folder?
How can I update Windows Subsystem For Android™ to a new version?
Install.ps1
. Don't worry, your data will be preservedHow do I update Magisk?
Can I pass SafetyNet/Play Integrity?
What is virtualization?
Run.bat
helps you enable it. After rebooting, re-run Run.bat
to install Windows Subsystem For Android™. If it's still not working, you have to enable virtualization in your BIOS/UEFI. Instructions vary by PC vendor, look for help onlineCan I remount system partition as read-write?
system.img
fileI cannot adb connect localhost:58526
Make sure developer mode is enabled. If the issue persists, check the IP address of Windows Subsystem For Android™ 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
Step 1
adb push module.zip /data/local/tmp
Step 2
adb shell su -c magisk --install-module /data/local/tmp/module.zip
How do I uninstall Magisk?
How to install KernelSU Manager?
Connect to WSA with ADB.
Run the following command:
adb shell ksuinstall
If the installation completes successfully, the KernelSU Manager will launching.
The repository is provided as a utility.
Android is a trademark of Google LLC. Windows™ is a trademark of Microsoft LLC.