From 05f33010fda9ffa8f10a738769ba6eff62ef990c Mon Sep 17 00:00:00 2001 From: MCDeltaT <68516357+MustardChef@users.noreply.github.com> Date: Thu, 19 Jan 2023 20:19:36 +0000 Subject: [PATCH] Update README.md --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 14f5fe7..d9f32ac 100644 --- a/README.md +++ b/README.md @@ -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 ` 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.