With almost all packages I have created (Installshield AdminStudio 5.5), I get the nearly the same message/behavior when I run a program that was installed via .msi package that I created:

Windows Installer, preparing to install
Gathering required information
Please wait while Windows configures [package name]

It acts like it's copying files or something. I could understand if this occured the first time I attempted to run a program that was installed via package on a machine, but it happens all subsequent times as well. I was thinking that it looks like it's looking for files from the distribution point, in this case a network resource installed via Active Directory. (Which would be bad because what if the network resource was not available) But I unassigned the package, and even renamed the folder of the distribution point as a test, and the program still runs properly, but after the 5-10 second message as mentioned above. After the message, (and what looks like a file copy) the program runs just fine, no problems at all.

However, I think it's kind of sloppy and annoying for some applications to always show this. Has anyone heard of this? Is there something I need to be doing when creating a package to eliminate this? Is there something I can clean up in a package to eliminate this? Like I said, this usually happens on most packages I have created, so it must be my method? Thanks in advance for your help.
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


That's a problem in your package, not Windows Installer.

The end result is that you package is attempting to self-repair on every launch. Check your Event Log and find out exactly what component triggered the self repair. My guess is that you have a Windows Protected File included in your package. Look for WPF errors in your Event Log, indicating the OS had a file overwritten and needed to correct it. If you included a Windows OS file in your package, this sort of thing can happen. Each tries to "fix" the other.
Answered 06/07/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment