Builds Last Updated:
- 19/09/2023 12:00 GMT (Reason: Initial Release)
Information:
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.
Please rename the folder (after extraction) to a shorter name, for example 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
Follow these steps to install on Windows 11.
Note :
If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA
- 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 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.
Changelog
- Microsoft's Official Changelog
- Update from WSA
v2308.40000.1.0
arm64 ---->v2308.40000.3.0
arm64 - WSA Android Version: Android 13
- MindTheGapps 13.0 arm64
- Magisk Canary
0fe46c5a (26301)
--->d4e552d0 (26301)
- Magisk Stable
v26.3
- KernelSU
v0.6.7
--->v0.6.8
- 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