Forum Discussion

TIMOTHY_MANGAN's avatar
Feb 24, 2022

Incorrect VFS references in AppXManifest due to MSIX Packaging Tool 2022.110

There appears to be an issue in how the packaging tool translates paths into relative VFS paths in the AppXManifest.

 

Although I suspect the issue is likely more general than this specific case, I'll provide the specific case.  The application being packaged includes a new shortcut that has a target application which is placed under the System32 folder. 

 

When captured on an x64 system, this results in the package ingredients being stored under relative paths starting with VFS\SystemX64.  Inside the AppXManifest, meanwhile, the reference in the application lists the executable as VFS\System.  This results in a file not found when the shortcut is run.

 

I do not know if this is new behavior in 2022.110, but suspect it has been there all along.

  • TIMOTHY_MANGAN 

    We would like to get more information on the app that you are trying to convert. Is it possible to share the name of the app or submit an issue through the feedback hub?

    • TIMOTHY_MANGAN's avatar
      TIMOTHY_MANGAN
      MVP
      The application includes a shortcut to run powershell.exe against a PS1 file that is inside the package. To repackage this, because the normal target exe is not in the package, it requires adding the PSF and replace the shortcut with one pointing to a copy of PsfLauncher. PsfTooling traditionally would place the launcher (and PsfRuntime.dll) in the folder of the original target exe, which is under a subfolder of the Windows\System32 folder. So these are files that are then captured as VFS\System. There are likely numerous other examples out there, but this is a simple one to reproduce.

      NOTE: I have since put special handling of this example in PsfTooling 5.0, but it only solves the issue (for this app) by avoiding this folder for files it adds. Other applications using this folder that require manifest reference, such as a shell extension component dropped in the System32 folder, will also have this problem.

      This mapping is clearly wrong, but I also recognize the pain it might cause to change it at this point.
      • kalyaniverma's avatar
        kalyaniverma
        Icon for Microsoft rankMicrosoft

        TIMOTHY_MANGAN 

        Thank you for your feedback. If you are able to share the app or log an issue through feedback hub, we will be able to do more research on this.

Resources