Another Exclusion issue explained
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: But it looks like a file written to during monitoring is captured using a different variablization [{System}], and is NOT excluded: Leading to a problem later on when saving the package, as shown here: 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.
