Run Windows Subsystem For Android on your Windows 10 and Windows 11 PC using prebuilt binaries with Google Play Store (MindTheGapps) and/or Magisk or KernelSU (root solutions) built in.
[!WARNING]
READ BEFORE DOWNLOADING!!!!
DIFFERENCE BETWEEN LTS RELEASES AND LAST NON-LTS RELEASES
Switches to upstream MagiskOnWSALocal Repo:
Magisk module and GApps Issues fixed
Pixel Devices Props no longer applied (except KernelSU Builds) (May cause unexpected behavour)
All Builds with Google Apps/GApps will now include Magisk by default in order for them to function
KernelSU Builds will be built using the old non-upstream script, to avoid the Magisk+Gapps limitation
LTS Builds aim to keep Magisk, KernelSU and Gapps up to date via regular releases.
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.2311.40000.5.0
20240213
81658d45
27.0
0.9.2
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!WARNING]
READ BEFORE DOWNLOADING!!!!
DIFFERENCE BETWEEN LTS RELEASES AND LAST NON-LTS RELEASES
Switches to upstream MagiskOnWSALocal Repo:
Magisk module and GApps Issues fixed
Pixel Devices Props no longer applied (except KernelSU Builds) (May cause unexpected behavour)
All Builds with Google Apps/GApps will now include Magisk by default in order for them to function
KernelSU Builds will be built using the old non-upstream script, to avoid the Magisk+Gapps limitation
LTS Builds aim to keep Magisk, KernelSU and Gapps up to date via regular releases.
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.2311.40000.5.0
20240213
81658d45
27.0
0.9.2
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!WARNING]
READ BEFORE DOWNLOADING!!!!
DIFFERENCE BETWEEN LTS RELEASES AND LAST NON-LTS RELEASES
Switches to upstream MagiskOnWSALocal Repo:
Magisk module and GApps Issues fixed
Pixel Devices Props no longer applied (except KernelSU Builds) (May cause unexpected behavour)
All Builds with Google Apps/GApps will now include Magisk by default in order for them to function
KernelSU Builds will be built using the old non-upstream script, to avoid the Magisk+Gapps limitation
LTS Builds aim to keep Magisk, KernelSU and Gapps up to date via regular releases.
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.2311.40000.5.0
20240213
81658d45
27.0
0.9.2
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2310.40000.2.0
to v2311.40000.5.0
20231109
65207f96
26.4
0.7.5
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2310.40000.2.0
to v2311.40000.5.0
20231109
65207f96
26.4
0.7.5
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2310.40000.2.0
to v2311.40000.5.0
20231109
65207f96
26.4
0.7.5
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2308.40000.3.0
to v2310.40000.2.0
20231109
d7750b72
26.4
0.7.1
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2308.40000.3.0
to v2310.40000.2.0
20231109
d7750b72
26.4
0.7.1
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2308.40000.3.0
to v2310.40000.2.0
20231109
d7750b72
26.4
0.7.1
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it
[!CAUTION]
For anyone updating from a previous WSA Build:
Please backup your Userdata VHDX using this guide, in the case that the builds in this release do not work as intended (crashes, bugs or not working), so that you can revert to the old version if needs be.
Ensure that 7-zip/WinRAR is up-to-date, before extracting, to avoid extraction errors.
[!NOTE]
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
If you're updating WSA, merge the folders and replace the files for all items when asked
[!IMPORTANT] If you have the official WSA installed or WSA installed that has not been downloaded from this repo, you must completely uninstall it to use these builds
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.Run.bat
in the extracted dir.
If the script fails, you can take the following steps for diagnosis (admin privilege required):
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
in PowerShell.
This should fail with an ActivityID, which is a UUID required for the next step.Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation.v2309.40000.2.0
to v2311.40000.4.0
20231109
d7750b72
26.4
0.7.1
If the Magisk App does not appear after the installation of the WSA build with Magisk, download it from here and sideload it into WSA
For Builds with KernelSU, you will need to sideload the KernelSU Manager in order to use it. You can get this by going to the releases here, and scrolling down the list of assets, until you find it