MSI Package Runs Configuration Every Time After Install

We are making .msi packages with Admin Studio 6. We are having an issue with some of the created .msi packages. The install always works in our test area.

When the .msi is deployed via active direcotry it does install correctly. But every time the application is opened we get a box saying Windows is configuring the application. Then the application always opens normally.

Has anyone else seen this?


Eric Kaufmann
St.Louis University

0 Comments   [ + ] Show comments

Answers (6)

Posted by: akhlaque 15 years ago
Orange Senior Belt
Hi Eric:

Try making the value of this registry key to blank


where XXXXXXXXXXX is the product ID and make the value of the key complete to blank.
Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
^^ Not sure about this reg fix akhlaque - can you explain?

Sounds to me like the application is repairing itself - did you validate and fix ICE errors / warnings?

Look in the eventlog (under application) to find out which component has a broken keypath - that should point you in the right direction...

Posted by: WiseUser 15 years ago
Fourth Degree Brown Belt
I bet you ALWAYS do ICE validate your new MSI files "religiously" eh?[;)]
Posted by: sini 15 years ago
Orange Senior Belt
Seems like you include temporary files set as keypath in you package which get deleted every time you open your app.
Posted by: TomB 15 years ago
Orange Belt
Along the same lines as sini, i have seen this multiple times with registry keys. some applications will write a setup complete or first launch value to the registry the first time it is opened. If you forget to open the application before and after snap shot and this registry key becomes a key path then when you open the app it will set reg key. Then the next time you open the app the MSI will set it back to the origional value and when the app runs it will change the key again. An endless loop if you will.

However, the best thing to do is to look in the event viewer and find the component in question.
Posted by: VeyTakon 15 years ago
Senior Yellow Belt
I agree. I used to run into this frequently with older version of Wise Package Studio before I got my exclusion list refined. I’m not sure if Admin Studio 6 has a similar feature. I’ve never used it before. I’d guess it does though.

For me the files in the C:\windows\prefetch directory (commonly known as “F&^#ing Prefetch”) were the biggest culprits. This directory is used by Windows to pre-cache commonly used components, and the files are updated and replaced continuously. These should always be removed from a package.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ