Forum Discussion

Charles_Y9495's avatar
Charles_Y9495
Copper Contributor
Jan 25, 2023

Add-AppxPackage -Register, 0x80073CF9, The manifest is not located in the package root directory.

  As shown, I tried to install a package (loose files) using the command "Add-AppxPackage -Register", but it did not install successfully. HRESULT: 0x80073CF9, telling me that "The manif...
0x80073CF9
MISX
TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
Jan 25, 2023
I would suggest looking at (or showing) the contents of the AppXManifest file. Possibly it sees the file but can't recognize the contents. If so, the event log in "Applications and Services Logs/Microsoft/Windows/AppXPackagingOM" should contain a more detailed error about what it didn't like.
  • Charles_Y9495's avatar
    Charles_Y9495
    Copper Contributor
    Jan 26, 2023
    Thanks for your suggestions. I have updated the information in the post to include the contents of AppxManifest.xml and an event log.
    • TIMOTHY_MANGAN's avatar
      TIMOTHY_MANGAN
      MVP
      Jan 26, 2023

      Charles_Y9495 

      I'm not sure what you are trying to accomplish, and suspect that what I see is a mashup up different things.
      1) The -Register option of the Add-AppxPackage command is for use with AppAttach, used for non-persistent VDI scenarios. General use of Add-AppxPackage does not use this option and the command line would reference a .appx or .msix package that was previously created using the MakeAppX or MakeMsix command.
      2) The AppxManifest file appears to be UWP from the contents. That's fine, but I am unsure if AppAttach deals with UWP apps (as in I just don't know, I have never tried it myself). But anyway, there are clearly incorrect fields in the file. The value for DisplayName (in several places) looks like a placeholder for the validation type. You should just have a normal looking name in that field rather than "ms-resource:xxx".

       

      Hopefully this will get you more into the right direction.

Resources