>>We have been telling our users that ThinApp is not leaving any trace on the system that the package is being ran from. I am assuming now that this is incorrect. Would anyone in ...
See more...
>>We have been telling our users that ThinApp is not leaving any trace on the system that the package is being ran from. I am assuming now that this is incorrect. Would anyone in the community be so kind as to explain what McAfee is actually detecting here Only place which ThinApp change in system is the Sandbox location, which you can simply get rid by deleting the folder. An exception is if the isolation mode for a certain folder is merged (check attribute.ini in any folder at package) . When you capture an application and build a ThinApp project from it; resulting bin folder contains all installation files with the container file as read only data. Now when you copy this to deploment machine and execute it, ThinApp may need to write file in certain cases (For example if application tries to create a log file). Now ThinApp does not allow creation of files into OS system folders (windows, program files etc) and sandbox all creates and writes. You can locate the default sandbox at %AppData%. So when you say no trace, it should mean the application will not write system registry, system folders. Of course if an application creates files, thinApp has to create them as otherwise application will not work, but instead of creating those file at all the places in system, ThinApp restrict them to a single sandbox location. I hope it make better sense now. Aditya
