

These differences are then put into the Thinapp package. The Post-Scan checks for any changes made to the clean machine since the information gathered by the Pre-Scan phase. The Post-Scan is run after the software you are trying to Thinapp has been installed. Files, Software, Services, Registry keys etc. It scans the clean machine and makes a note of everything on it. The Pre-Scan phase is run before installation of the software you are Thinapping. If you are a Thinapp user you'll probably understand that during the capture process you have two main phases. This also includes updates Microsoft updates. So what exactly is a clean machine? A clean machine is a “vanilla” Windows OS and its essential drivers with no other software installed. I've been working a lot with Thinapp lately and one thing I keep noticing when users are creating their Thinapp's is they are neglecting to use a clean capture machine.
