Problem:
When packaging large applications and/or applications with a high volume of files using the high-compatibility capture mode, files that would otherwise be present after performing a native installation of the application are not present when compared to file contents of the package itself.
**This issue is fixed in ProfileUnity 6.8.6**
Resolution:
Step 1 - Increase Journal Size
High-compatibility mode leverages the NTFS Change/USN (Update Sequence Number) Journal of the OS when capturing applications, comparing files that are present prior to installation of application against those that are present upon completion of installation, saving the recorded changes into the FlexApp package. Using Windows 10 as an example, the default size of the journal is 32MB. Per the chart displayed below, it's recommended to increase the journal size by 128MB for every 100,000 files.
In the event where files are missing, this is due to the size limit of the journal being exceeded and unable to completely record all of the files created during installation. To address this issue, increase the size of the journal on the FPC image by defining higher values for both 'Maximum Size' and 'Allocation Delta' using the native Windows 'fsutil' utility. In the example command below, we'll set the values to be half of the maximum allowed, per the chart referenced above.
fsutil usn createjournal m=2147483648 a=268435456 C:
Step 2 - Increase Capture Timeout
Larger applications can take longer to install, so to avoid possible timeout issues during the capture process, modify 'C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Console\FlexApp Packaging Console.exe.config.xml', changing the value of 'CaptureTimeout' setting shown below.
In this example, double it from:
<CaptureTimeout>600</CaptureTimeout>
To:
<CaptureTimeout>1200</CaptureTimeout>
References:
https://faq.scomis.org/kb4174/
https://binaryguru.wordpress.com/2017/01/05/increasing-the-size-of-the-ntfs-change-journal/
Product: ProfileUnity
Product Version: 6.8.5