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   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


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.
Answered 10/05/2005 by: akhlaque
Orange Senior Belt

Please log in to comment
^^ 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...

Answered 10/05/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
I bet you ALWAYS do ICE validate your new MSI files "religiously" eh?[;)]
Answered 10/07/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
Seems like you include temporary files set as keypath in you package which get deleted every time you open your app.
Answered 10/07/2005 by: sini
Orange Senior Belt

Please log in to comment
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.
Answered 10/07/2005 by: TomB
Orange Belt

Please log in to comment
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.
Answered 10/07/2005 by: VeyTakon
Senior Yellow Belt

Please log in to comment