Hopefully someone has experienced this and can point me in the right direction.
We have a pretty simple installation requirement, a main program, a few DLLs, OCXs and a Help PDF.
I have made the installation, changed what I need to change and compiled to a single setup.exe.
This works perfectly well for installation and uninstallation, but...
Under Vista 64bit (2 unrelated PCs) we have witnessed horrendous start up times, from double clicking setup.exe to the splash screen appearing has taken 45 minutes. :eek:
I can't say for sure if this is a 64bit problem, because I have also seen it wait a couple of minutes on XP, but I would really like some advice on whether it is a problem with this OS or a PC dependent problem, or even if anyone has experienced this.
I really need an explanation because we can't put this installation out to our customers without a work round.
We see a similar startup delay on Windows 7 64 bit when we use InstallShield Pro 2009.
Everything is chugging along merrily until InstallationInfo() is hit in our event-based InstallScript.
Using ProcessMonitor, it seems like the registy is getting a lot to do on a RegCloseKey(). It took about 19 seconds for a RegCloseKey() to finish. Meanwhile, a large white/blank area is left on the screen leaving our users to wonder if the app crashed. The UI (wizard) has not even been displayed yet!
