MustardChef / WSABuilds

Run Windows Subsystem For Android on your Windows 10 and Windows 11 PC using prebuilt binaries with Google Play Store (MindTheGapps) and/or Magisk or KernelSU (root solutions) built in.
GNU Affero General Public License v3.0
6.88k stars 1.19k forks source link

[BUG] ID 709 - "Rejecting a request to register from AppxBundleManifest.xml" #315

Closed RaksitYar closed 2 months ago

RaksitYar commented 4 months ago

Describe the bug

does not work "Run.bat"

Get-AppPackageLog -ActivityID d032e44a-..........

Time ID Message


603 Started deployment Register operation on a package with main parameter AppxManif est.xml and Options DevelopmentModeOption and 0. See http://go.microsoft.com/fwl ink/?LinkId=235160 for help diagnosing app deployment issues. 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com /developer/appx/2015/build is inapplicable, it will be ignored during manifest p rocessing. 709 Rejecting a request to register from AppxBundleManifest.xml because the manifest is not in the package root. 404 AppX Deployment operation failed for package with error 0x80070057. The specifi c error text for this failure is: Registration request from AppxBundleManifest.xm l is rejected because the manifest is not in the root of the package.

Steps to reproduce the issue

Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

Expected behaviour

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor. (Exc eption from HRESULT: 0x80073CF9) The request for registration from AppxBundleManifest.xml is rejected because the manifest is not in the root of the package. NOTE: For additional information, look for [ActivityId] d032e44a-688e-000f-0667-33d08e68da01 in the Event Log or use th e command line Get-AppPackageLog -ActivityID d032e44a-688e-000f-0667-33d08e68da01 At line:1 char:1

Downloaded Build Of WSA

WSA_2311.40000.5.0_x64_Release-Nightly-with-Magisk-26.4-stable-MindTheGapps-13.0

Windows build number

23H2 (22631.3155)

PC Specification

ASUS ROG FLOW 13

Additional context

No response

MustardChef commented 4 months ago

@RaksitYar Update your extraction software (7-Zip/ WinRAR). The delete all your files, redownload the WSA Build and re-extract and try again.

RaksitYar commented 4 months ago

@RaksitYarОновіть програмне забезпечення для видобування (7-Zip/WinRAR). Видаліть усі файли, повторно завантажте збірку WSA, розпакуйте та повторіть спробу.

7zip - 24.01. WinRAR - v6.24. Unzips without errors.

"PS C:\Users...\Documents\WSA> Get-AppxPackage "[I]MicrosoftCorporationII.WindowsSubsystemForAndroid[/I]" | Remove-AppxPackage PS C:\Users...\Documents\WSA>"

I checked all the WSA files. The files are actually deleted.

MustardChef commented 4 months ago

@RaksitYar Could you tell me what files are missing?

RaksitYar commented 4 months ago

All WSA files deleted and the error does not disappear.

MustardChef commented 4 months ago

All WSA files deleted and the error does not disappear.

Could you send me a screen recording of the extraction and installation process and also provide screenshots of the extracted folder.

Thank you!

RaksitYar commented 4 months ago

Run Folder1 Folder2 Folder3

MustardChef commented 4 months ago

Run Folder1 Folder2 Folder3

Could you open the folder in Powershell and run:

Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
RaksitYar commented 4 months ago

PS-run

RaksitYar commented 4 months ago

test

MustardChef commented 4 months ago

test

You ran the command incorrectly.

RaksitYar commented 4 months ago

I didn't even pay attention =). A strange error occurred. Copied from the message.

test2

This error is repeated on two other devices.

MustardChef commented 4 months ago

I was able to download and install the same build successfully. Not sure why this error occurs for you.

RaksitYar commented 4 months ago

Last time I installed WSA PacMan together with WSA. Can it somehow affect now? at this point i have already uninstalled WSA PacMan

akshayrathnavas commented 3 months ago

I can confirm that even I am having the same error with the builds. I have tried the following.

WSA_2311.40000.5.0_x64_Release-Nightly-with-Magisk-26.4-stable-MindTheGapps-13.0.7z WSA_2311.40000.5.0_x64_Release-Nightly-with-Magisk-65207f96-canary-MindTheGapps-13.0-RemovedAmazon.7z WSA_2311.40000.5.0_x64_Release-Nightly-with-Magisk-26.4-stable-NoGApps-RemovedAmazon.7z WSA_2311.40000.5.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon.7z

Windows Specifications: Version: 23H2 OS Build: 22631.2262 Windows Feature Experience Pack 1000.22674.1000.0

Asus Zephryus G15 AMD Ryzen 9 5900HS

image

image

C:\Users\akshay\Documents\WSA> Get-AppPackageLog -ActivityID 1160fcd6-76c4-0008-26e6-6b11c476da01

Time ID Message
15-03-2024 16:31:58 603 Started deployment Register operation on a package with main parameter AppxManifest.xml and Options ForceApplicationShutdownOption,DevelopmentModeOption,ForceUpdateFromAnyVersion and 0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
15-03-2024 16:31:58 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/developer/appx/2015/build is inapplicable, it will be ignored during manifest processing.
15-03-2024 16:31:58 709 Rejecting a request to register from AppxBundleManifest.xml because the manifest is not in the package root.
15-03-2024 16:31:58 404 AppX Deployment operation failed for package with error 0x80070057. The specific error text for this failure is: Rejecting a request to register from AppxBundleManifest.xml because the manifest is not in the package root.

I have tried updating 7zip to the latest, tried latest WinRAR, and also extracting the zips to various locations, like C:\WSA, Documents\WSA, E:\WSA too

akshayrathnavas commented 3 months ago

@MustardChef @RaksitYar I was able to solve this issue using:

https://github.com/WSA-Community/WSAGAScript/issues/28#issuecomment-992113337

MustardChef commented 2 months ago

I will close this issue now. This problem should not occur on the latest LTS builds of WSA.