WSAGAScript icon indicating copy to clipboard operation
WSAGAScript copied to clipboard

Issue installing

Open swatwithmk3 opened this issue 3 years ago • 6 comments

When I get to the step for the AppxManifest.xml I get an error that I need to a Windows Developer license or sideload enabled system. When I run the command with "-DisableDevelopmentMode" I get an error that the install failed.

image

swatwithmk3 avatar Oct 24 '21 03:10 swatwithmk3

Same issue here. In Dev ring, had previously used the Msixbundle method to install latest Windows Store and WSA, then uninstalled WSA, then followed the guide ~~to the letter~~ and everything was fine up to this point. I do notice the folders: C:\ProgramData\Microsoft\Windows\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForAndroid_1.7.32815.0_x64__8wekyb3d8bbwe and C:\Windows\System32\config\systemprofile\AppData\Local\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe still remain after uninstalling WSA.

EDIT: Nevermind, missed the part in the "Delete the files appxblockmap, appxsignature and [content_types] along with the folder appxmetadata." bit under "Extract msixbundle". Perhaps give that a bolded heading of its own? It's easy to skip when thinking that step is done after extracting the file. After doing so it installs and runs just fine.

Jaitsu avatar Oct 24 '21 04:10 Jaitsu

Screenshot 2021-10-23 234713

Make sure you enable developer mode, as shown in the screenshot above.

shahmirn avatar Oct 24 '21 04:10 shahmirn

@shahmirn It was already on but it seems I made the same mistake as @Jaitsu, after deleting the files from msix bundle and redoing everything the installation was completed successfully

P.S.

I had some trouble with Appx package installation but that was because I had installed Powershell 7 and it seems that it currently only works with Powershell core and the default Powershell app that is bundled with Windows in case someone else is using powershell 7

swatwithmk3 avatar Oct 24 '21 09:10 swatwithmk3

Faced with the same issue on beta. Do I need to remove preinstalled WSA first?

hooddy avatar Oct 25 '21 07:10 hooddy

I've been able to resolve the issue of "manifest is not in the package root" by running this command Get-AppPackage -Name "*WindowsSubsystemForAndroid*" -AllUsers | ForEach-Object {Remove-AppPackage $_.PackageFullName -AllUsers}

marcellus00 avatar Dec 13 '21 05:12 marcellus00

this works thanks😊

qwertryyyu avatar Jun 21 '23 15:06 qwertryyyu