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.
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.1.0
arm64 ----> v2308.40000.3.0
arm640fe46c5a (26301)
---> d4e552d0 (26301)
v26.3
v0.6.7
---> v0.6.8
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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.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
https://github.com/LSPosed/MagiskOnWSALocal https://github.com/cinit/WSAPatch
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.VPNDialogs
back into the releasesIf 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
https://github.com/LSPosed/MagiskOnWSALocal https://github.com/cinit/WSAPatch
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.VPNDialogs
back into the releasesIf 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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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.VPNDialogs
back into the releasesIf 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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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..zip
releases to .7z
for releasesIf 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
https://github.com/LSPosed/MagiskOnWSALocal https://github.com/cinit/WSAPatch
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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..zip
releases to .7z
for releasesIf 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
WSA
. This will help you avoid the potential issues that may occur during installation and after install.Warning
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
Note
If you're updating WSA, merge the folders and replace the files for all items when asked
Note : If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
WSA
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..zip
releases to .7z
for releasesIf 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