THIS RELEASE FIXES THE ARM TRANSLATION LAYER ISSUE. UPDATE TO THESE BUILDS IF YOU FACE THE FOLLOWING:
APPS NOT OPENING OR CRASHING OR GETTING STUCK ON THE SPLASHSCREEN OR ANY OTHER SIMILAR ISSUES OCCURRING ON AND AFTER THE 2ND OF JUNE 2025
-
-
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.
-
Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 11.
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
- 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
- As stated in theRequirements, 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.xmldoes 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.batin 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.xmlin 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