Specific issue: I use the tool to capture an installer for an application that has a dependency on vc140 runtime. Because of the requirement to install the SDK on the capture box in order to perform the capture, this runtime is installed (along with a ton of other crap) onto the machine. Therefore the app installer to be captured determines that the requirements are met and does not install the requirement and it is not captured in the package. This package cannot be used on a machine without the pre-requisite. The app will just fail and the handling of the error is completely dependent on the app vendor, which may not help anyone understand that there is a missing dependency.
More general issue: In package capturing, our experience has been that:
The pre-capture environment should contain, as close as is possible, nothing other than the base OS and well known common components that will always be available on the target systems.
The OS image on which the capture is being done needs to have very few moving parts. Turning off search and updates are a good start, but there are many more things going on that should be addressed somehow.
On the first item, our experiences in App-V capturing were to solve #1 using a minimal OS with nothing added except for the capture tool (the sequencer). Microsoft made sure that the sequencer did not add any additional components that would not also be present at the client. This tool needs to do the same.
While there are things I'd like to see the tool do pre-install (like flush the ngen queues and turn off Windows store app updating), we ultimately probably deal with this via conditioning of a "clean VM snapshot" to do the packaging on. We will need more documentation on how that capture works to be successful. So documenting things like exclusions implemented by default (files/folders, registry, and processes) and maybe giving us control over them would be good.