What causes an MSI package to launch following application install
- by Damo
We have an application we have developed, it gets deployed via an MSI I built.
The MSI has been used in many locations, on many different builds. On one customers site, on occasion we are seeing some odd occurrences of data from the registry going missing. The 'data' from some select registry keys disappears and we have little idea why.
One interesting point is that the MSI installer for our application has been seen in passive mode during OS load / load of our application on stat-up.
The MSI loads a progress bar then disappears, following this our application loads up. It has been noted that following this the data disappears from our registry. However I can't say these two events are absolutely linked, it could have been missing before this event.
What causes the MSI for an application to launch way after initial installation.
How can it be prevented (correctly)