Skip to content

Windows Subsystem For Android: Windows 11 for ARM Processors (Windows_11_WSA_2304.40000.7.0_arm64)
Compare
Choose a tag to compare
@MustardChef MustardChef released this 25 May 16:26
· 35 commits to main since this release
Windows_11_2304.40000.7.0_arm64
be37296
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Builds Last Updated:

- 25/05/2023 17:00 GMT (Reason: Initial Reason)

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.



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

  1. Extract the zip file
  2. Delete the zip file (It is recommended to keep the .zip file until WSA has been installed and is working properly)
  3. 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
  4. Open the WSA folder and double-click Run.bat

Notice:

  1. As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
  2. You can NOT delete the WSA 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 WSA.
    Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
  3. You need to register your WSA appx package before you can run WSA.
    For WSABuilds 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):
    1. Open a PowerShell window and change working directory to your WSA directory.
    2. 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.
    3. Run Get-AppPackageLog -ActivityID <UUID> in PowerShell.
      This should print the log of the failed operation.
    4. Check the log for the reason of failure and fix it.

Changelog

  • Microsoft's Official Changelog: There is no official changelog as of the time of publishing this release. I will update this release description if one is made avaliable
  • WSA v2304.40000.6.0 arm64 ----> WSA v2304.40000.7.0 arm64
  • WSA Android Version: Android 13
  • MindTheGapps 13.0 arm64
  • Magisk Delta fdac22ba (25210)
  • Amazon Appstore Removed

Difference Between Versions In This Release:

  • WSA_XXXX.X0000.X.0_XXXX_Release-Nightly-magisk-XXXXX.-delta.XXXXX.-canary-MindTheGapps-XX.X-RemovedAmazon.zip
    - Contains Google Play Store and Services
    and
    - Contains Magisk Delta (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

Credits:

https://github.com/LSPosed/MagiskOnWSALocal

Assets 3
Loading