SOLVED

Another Exclusion issue explained

%3CLINGO-SUB%20id%3D%22lingo-sub-292989%22%20slang%3D%22en-US%22%3EAnother%20Exclusion%20issue%20explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292989%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20another%20case%20of%20exclusion%20issues%2C%20this%20time%20without%20specifying%20the%20installation%20folder.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Exclusion%20for%20%22C%3A%5CWindows%5CSystem32%5Cwbem%5CPerformance%22%20gets%20mapped%20to%20%5B%7BAppVPackageRoot%7D%5D%26nbsp%3B%20when%20you%20enter%20it%20in%20the%20exclusion%20list%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F61015i8849CF691D084AE5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture1.PNG%22%20title%3D%22Capture1.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBut%20it%20looks%20like%20a%20file%20written%20to%20during%20monitoring%20is%20captured%20using%20a%20different%20variablization%20%5B%7BSystem%7D%5D%2C%20and%20is%20NOT%20excluded%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F61016i129523F09BA5D8B3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture2.PNG%22%20title%3D%22Capture2.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELeading%20to%20a%20problem%20later%20on%20when%20saving%20the%20package%2C%20as%20shown%20here%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F61017i70470DF1F263322F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture3.PNG%22%20title%3D%22Capture3.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAs%20with%20the%20previous%20exclusion%20issue%2C%20there%20are%20two%20problems%20here%3A%3C%2FP%3E%0A%3CP%3E1)%20The%20way%20the%20exclusion%20is%20stored%20does%20not%20match%20how%20the%20filtering%20is%20done.%3C%2FP%3E%0A%3CP%3E2)%20The%20save%20shouldn't%20fail.%20I%20don't%20know%20why%20this%20file%20caused%20an%20error%2C%20although%20003%20error%20code%20sounds%20like%20file%20not%20found.%20Except%20that%20in%20this%20case%20the%20file%20is%20indeed%20there%20when%20I%20look%20for%20it%20after%20the%20problem%20occurred.%26nbsp%3B%20Perhaps%20it%20was%20unable%20to%20open%20the%20file%20to%20look%20at%20the%20attributes%20because%20someone%20had%20a%20lock%20on%20it%3F%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20attaching%20the%20full%20log%20file%20from%20the%20save.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-292989%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Etim%40tmurgent.onmicrosoft.com%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-326379%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20Exclusion%20issue%20explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326379%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20update!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-326305%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20Exclusion%20issue%20explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326305%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20note%20to%20confirm%20that%20it%20looks%20like%20this%20no%20longer%20causes%20the%20package%20to%20fail%20creation%20in%20the%201.2019.110%20version%20of%20the%20MSIX%20Packaging%20Tool.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324966%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20Exclusion%20issue%20explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324966%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20remember%20the%20specific%20app%2C%20but%20it%20wasn't%20the%20app%20touching%20the%20WMI%20stuff%20you%20see.%26nbsp%3B%20This%20was%20just%20general%20back-end%20Windows%20noise.%26nbsp%3B%20The%20issue%20is%20when%20the%20noise%20creates%20a%20file%20while%20monitoring%2C%20but%20then%20deletes%2Flocks%20it%20during%20package%20creation%20phase.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20think%20the%20team%20has%20a%20handle%20on%20the%20saving%20issue%2C%20but%20ultimately%20I%20would%20like%20a%20way%20to%20deploy%20preconfigured%20settings%20for%20the%20tool.%26nbsp%3B%20These%20are%20stored%20in%20a%20file.%20You%20can%20pre-deploy%20the%20tool%20in%20an%20image%2C%20but%20until%20the%20user%20is%20logged%20on%20and%20starts%20the%20tool%20once%2C%20the%20redirection%20folder%20for%20the%20app%20does%20not%20exist.%26nbsp%3B%20So%20I%20can%20copy%20it%20over%20then%2C%20but%20I%20would%20like%20to%20be%20able%20to%20automate%20that.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324734%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20Exclusion%20issue%20explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324734%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20a%20publicly%20available%20app%3F%20it%20looks%20like%20it%20extends%20the%20WMI%20repository.%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

I found another case of exclusion issues, this time without specifying the installation folder.

 

The Exclusion for "C:\Windows\System32\wbem\Performance" gets mapped to [{AppVPackageRoot}]  when you enter it in the exclusion list:

Capture1.PNG

 

But it looks like a file written to during monitoring is captured using a different variablization [{System}], and is NOT excluded:

Capture2.PNG

 

Leading to a problem later on when saving the package, as shown here:

Capture3.PNG

As with the previous exclusion issue, there are two problems here:

1) The way the exclusion is stored does not match how the filtering is done.

2) The save shouldn't fail. I don't know why this file caused an error, although 003 error code sounds like file not found. Except that in this case the file is indeed there when I look for it after the problem occurred.  Perhaps it was unable to open the file to look at the attributes because someone had a lock on it?  

 

I am attaching the full log file from the save.

4 Replies

Is this a publicly available app? it looks like it extends the WMI repository.

I don't remember the specific app, but it wasn't the app touching the WMI stuff you see.  This was just general back-end Windows noise.  The issue is when the noise creates a file while monitoring, but then deletes/locks it during package creation phase.

 

I think the team has a handle on the saving issue, but ultimately I would like a way to deploy preconfigured settings for the tool.  These are stored in a file. You can pre-deploy the tool in an image, but until the user is logged on and starts the tool once, the redirection folder for the app does not exist.  So I can copy it over then, but I would like to be able to automate that.  

best response confirmed by Steve Thomas (GLADIATOR) (Microsoft)
Solution

Just a note to confirm that it looks like this no longer causes the package to fail creation in the 1.2019.110 version of the MSIX Packaging Tool.

Thanks for the update! :)