MSIX Packaging Tool Failures: File not found issues (A workaround)


In packaging a lot of apps, I find that the Packaging tool fails quite often when saving the package.  In looking into the Log file, these errors are usually background system created files.  Like C:\Windows\System32\config\SYSTEM.LOG1 or LOG2.  Or those stupid wbem files.


Adding exclusions doesn't seem to help.  I even add them in the form shown, or in \\?\C:\Windows... form (as the log file hints at).  Still doesn't help.  Even though the files are in the exclusion list, they don't get excluded.  


One possible cause of this is hinted at by the workaround that I am using.  Rather than save the package off and have it fail, I find I must continue into the package editor.  From there I can manually look for potentially offending files and right-click delete them.  Then I can save the package off cleanly.


So what's the hint about the possible cause?  Well when you add an exclusion (on an x64 OS) to C:\Windows\System32\config\SYSTEM.LOG1, this exclusion is mapped to and saved as "[{AppVPackageRoot}]\config\SYSTEM.LOG1"  (where the default [{AppVPackageRoot}] points to the system32 folder).  I previously commented that this is a horrible mapping, as one might set the package root manually in which case this points to a different place.  And that does need to be addressed, but I wasn't doing that here - I was not specifying the installation folder.  No, the possible cause is seen inside the editor where the captured file is actually mapped differently, as "[{System}]\config\SYSTEM.LOG1".  Which of course is a different folder (but also in the exclusion list).


So it seems that the exclusion filtering is horribly confused by these variables and needs to be fixed. But at least with a work-around I can start packaging again!






5 Replies

Thanks for the feedback.  I filed an item for the team to look into this for the MSIX Packaging Tool.



Hi Tim,


I assume you started seeing this issues on the November Insider flight?  I fixed some issues in this area early December that should address missing file or file in use errors while saving the package.  The December flight should have those fixes.


If you are still seeing such problems on the latest build of the tool, please let me know.





I am using build 1115. I'll go back and see if that isn't the latest.



I see this isn't the latest. 


It isn't easy to know when updates to the tool are available because we keep Windows Update disabled don't login with the MSA account on machines  we use for captures.  A notification to those getting access to the private builds would go a long way ;) 

The public release of the tool is 2018.1005.2324.0, which is the only update to date.  We will update the docs when a new version is released (and provide notes on some key changes).


Longer term we have an item in the backlog, lower priority at this time, to offer an in app notification if a newer version is available.  This would obviously require some connectivity to the internet to poll and let the IT Pro know a newer version is available.