I am using Wise Package Studio 7 SP3 and I have a program that keeps going through the set up before a program launches. The program launches fine each time but goes through the set up. On the box I used to package it it does not do this. Has anyone seen this and point me in the right direction to resolve.

Thank you.
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


Sounds like you are launching the application via an advertised shortcut.

When you launch software via an advertised shortcut it will look at all of the components within the feature that the shortcut is in. If one of the keypaths is incorrect/missing, it will repair that feature and then work it's way up the feature tree.

Most likely when you launch the application, or use it in some way, it is changing a component on your PC that is set as a keypath or you have another application that's changing something.

Either way......your best bet is to look in the event viewer for more details and also enable Windows Installer Logging on your test PC to view the logs.

If you need to know more about self healing/advertised shortcuts, there are several great posts on this website/forum, just search for them.
Answered 03/18/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
im guessing your the lucky winner of 2 applications sharing a component code with different keypaths

chances of this are supposedly very slim although I have seen it a lot. (go buy a lotto just in case your lucky).

as the previous poster mentioned check the application event log to find the path to fixing this .
Answered 03/18/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Thank you for the help. I was able to resolve the issue. There was a MSI Installer error in the event log about microsoft search each time the program was launched. Removed it from the package, re-compiled it and it worked.
Answered 03/19/2009 by: bgpau96
Senior Yellow Belt

Please log in to comment