mirror of
https://github.com/MustardChef/WSABuilds.git
synced 2024-11-27 13:44:16 +01:00
Update README.md
This commit is contained in:
parent
05f33010fd
commit
dd3946d409
@ -85,8 +85,8 @@
|
|||||||
What `Add-AppxPackage -Register .\AppxManifest.xml` does is to register an appx package with some existing unpackaged files,
|
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.
|
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.
|
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).
|
3. You need to register your WSA appx package before you can run WSA.
|
||||||
For [MagiskOnWSALocal](https://github.com/LSPosed/MagiskOnWSALocal) users, you need to run `Run.bat` in the extracted dir.
|
For [WSABuilds](https://github.com/MustardChef/WSABuilds) and [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):
|
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.
|
1. Open a PowerShell window and change working directory to your WSA directory.
|
||||||
2. Run `Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml` in PowerShell.
|
2. Run `Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml` in PowerShell.
|
||||||
|
Loading…
Reference in New Issue
Block a user