Mirrors/WSABuilds
2
0
Fork 0
mirror of https://github.com/MustardChef/WSABuilds.git synced 2024-11-13 07:05:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
MCDeltaT 2023-01-19 20:19:36 +00:00 committed by GitHub
parent 0924e5e9dc
commit 05f33010fd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -78,6 +78,23 @@
9. Close File Explorer
10. **Enjoy**
### Notice: For the Windows 10 Builds
1. 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 (the 8th step in the instructions).
For [MagiskOnWSALocal](https://github.com/LSPosed/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.
## Uninstallation
### New CLI and GUI Uninstall Tool Coming Soon! Join the Discord for announcements and updates.