Releases: MustardChef/WSABuilds
WSABuilds LTS Build #5 (05/12/24 - 2407.40000.0.0) for Windows 10 x64
-
THIS RELEASE SHOULD BE USED IF YOU HAVE BEEN RECENTLY HAVING ISSUES WITH SOME APPS BREAKING OR NOT STARTING OR APPS GETTING SUCK AT LOADING SCREEN OR APPS STUCK ON SPLASHSCREEN ( STUCK ON THE APP ICON SCREEN) OR ANY OTHER SIMILAR CASES.
-
LET ME KNOW VIA GITHUB ISSUES, THE WSA COMMUNITY DISCORD OR THE r/WSA SUBREDDIT IF THIS RELEASE SOLVED HAS YOUR ISSUE. THANK YOU.
Builds Last Updated:
- 05/12/2024 15:46:30 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- Latest Windows 10 Patch Applied (Credit: Cinit/WSAPatch)
- WSA Android Version: Android 13
- WSA Build Version:
2407.40000.0.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
895b5f6c
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.2
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps_Windows_10.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X_Windows_10.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
Windows Subsystem For Android 2407.40000.0.0 for Windows 10 x64
-
THIS RELEASE SHOULD BE USED IF YOU HAVE BEEN RECENTLY HAVING ISSUES WITH SOME APPS BREAKING OR NOT STARTING OR APPS GETTING SUCK AT LOADING SCREEN OR APPS STUCK ON SPLASHSCREEN ( STUCK ON THE APP ICON SCREEN) OR ANY OTHER SIMILAR CASES.
-
LET ME KNOW VIA GITHUB ISSUES, THE WSA COMMUNITY DISCORD OR THE r/WSA SUBREDDIT IF THIS RELEASE SOLVED HAS YOUR ISSUE. THANK YOU.
-
THIS NON-LTS RELEASE HAS NO MAGISK BUILDS. USE THE LTS_5 RELEASE, IF YOU REQUIRE MAGISK BUILDS.
Builds Last Updated:
- 05/12/2024 16:07:55 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- Latest Windows 10 Patch Applied (Credit: Cinit/WSAPatch)
- WSA Android Version: Android 13
- WSA Build Version:
2407.40000.0.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
895b5f6c
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.2
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps_Windows_10.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X_Windows_10.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #4 (15/07/24 - 2407.40000.0.0) for Windows 11 arm64
Builds Last Updated:
- 15/07/2024 09:03:42 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 11.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2407.40000.0.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
b38ab2a7
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #4 (15/07/24 - 2407.40000.0.0) for Windows 11 x64
Builds Last Updated:
- 15/07/2024 09:03:42 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2407.40000.0.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
b38ab2a7
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #4 (15/07/24 - 2407.40000.0.0) for Windows 10 x64
Builds Last Updated:
- 15/07/2024 09:03:42 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- Latest Windows 10 Patch Applied (Credit: Cinit/WSAPatch)
- WSA Build Version:
2407.40000.0.0
- WSA Android Version: Android 13
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
b38ab2a7
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps_Windows_10.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X_Windows_10.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #3 (03/06/24) for Windows 11 arm64
Builds Last Updated:
- 03/06/2024 09:58:19 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2311.40000.5.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
81658d45
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #3 (03/06/24) for Windows 11 x64
Builds Last Updated:
- 03/06/2024 09:58:19 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2311.40000.5.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
81658d45
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #3 (03/06/24) for Windows 10 x64
Builds Last Updated:
- 03/06/2024 09:58:19 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- Latest Windows 10 Patch Applied (Credit: Cinit/WSAPatch)
- WSA Build Version:
2311.40000.5.0
- WSA Android Version: Android 13
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
81658d45
- Magisk Stable Version:
27.0
- KernelSU Version:
1.0.0
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps_Windows_10.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X_Windows_10.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon_Windows_10.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #2 (03/05/24) for Windows 11 arm64
Builds Last Updated:
- 03/05/2024 10:46:40 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 11.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2311.40000.5.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
81658d45
- Magisk Stable Version:
27.0
- KernelSU Version:
0.9.3
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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
WSABuilds LTS Build #2 (03/05/24) for Windows 11 x64
Builds Last Updated:
- 03/05/2024 10:46:40 GMT (Reason: Initial Release)
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
Follow these steps to install on Windows 10.
- Extract the .7z archive using 7-zip (recommended) and rename the extracted folder to WSA
- Delete the .7z archive (It is recommended to keep the .7z archive until WSA has been installed and is working properly)
- 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
- Open the WSA folder and double-click on Run.bat
Notice:
- As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
- You can NOT delete the WSA installation folder.
WhatAdd-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. - You need to register your WSA appx package before you can run WSA.
For WSABuilds and MagiskOnWSALocal users, you need to runRun.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 WSA directory.
- 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. - Run
Get-AppPackageLog -ActivityID <UUID>
in PowerShell.
This should print the log of the failed operation. - Check the log for the reason of failure and fix it.
- If unable to fix, seek assistance via Issues or the WSA Community Discord
Changelog
- WSA Android Version: Android 13
- WSA Build Version:
2311.40000.5.0
- MindTheGapps Package Version:
20240213
- Magisk Canary Version:
81658d45
- Magisk Stable Version:
27.0
- KernelSU Version:
0.9.3
- Amazon Appstore Removed
Difference Between Versions In This Release:
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X-RemovedAmazon.7z
- Contains Google Play Store and Services
- No Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-MindTheGapps-XX.X.7z
- Contains Google Play Store and Services
- Contains Amazon App Store
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-NoGApps.7z
- Amazon App Store Included
- No Google Play Store and Services
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-kernelsu-vX.X.X-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains KernelSU (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-MindTheGapps-XX.X.7z
- Amazon App Store Included
- Contains Google Play Store and Services
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-with-magisk-XX.X.XXXX.-stable-NoGApps-RemovedAmazon.7z
- No Amazon App Store
- Contains Magisk Stable (for Root Access)
- WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.XXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.7z
- No Amazon App Store
- Contains Google Play Store and Services
- Contains Magisk Canary (for Root Access)
Additional Information
-
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