This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Simon_Dand
Level 4
‎Sep 14, 2009 10:02 PM

Windows Installer initialization dialog question

All,

Does anyone know a way of hiding the Windows Installer initialization dialog that appears briefly when starting an MSI installation? I know the /qn switch will hide it, but I need my silent installation to still run the InstallUISequence; I have conditions on all the visible dialogs in the InstallUISequence to hide them.

My install now basically runs silently, but I am now being told the Windows Installer initialization dialog that pops up for a few seconds at the start is violating the silent installation requirement.

I'm guessing this is a MSI issue that is probably out of my control, but being a diligent software engineer I'm trying to find a solution.

Thanks
Simon
Labels (1)
Labels
0 Kudos
(4) Replies
Reureu
Level 10
‎Sep 15, 2009 02:42 AM

I'm not sure I understand why you still want to show the UI sequence in a silent installation.
A silent installation actually does not run the UI sequence. It only runs the execute sequence.

Anyway, that might help:

If you are launching the installation by calling msiexec, the command line should be:
msiexec /qn /i "YourMsiPackage.msi"

You should not see any user interface when calling it in that way.

Now if you are calling setup.exe, you need to hide the setup.exe UI too.
setup.exe /s /v"/qn"

the /s tells setup.exe not to display any UI.

Tell me if that does the job.
0 Kudos
cbragg
Level 7
‎Sep 15, 2009 03:43 AM

initializing dialog doesn't come from the package it comes from Windows installer itself. The only way, you can silence it and only have some of your own select dialogs (and it's beyond me why you'd want to do this) is to silence the installation using /qn and then having your own developed dialogs (using C++ or whatever) pop up as installexecute custom actions but this breaks sooooo many best practices not to mention you wont be able to support remote deployment easily
0 Kudos
Simon_Dand
Level 4
‎Sep 15, 2009 07:33 AM

Thanks for the replies but using the /qn switch is out of the question, as I want the InstallUISequence to run, I just don't want any dialog displayed. I have some other custom actions running the UI sequence that wont run correctly in the InstallExecuteSequence and so I run them in the InstallUISequence.

Regards
Simon
0 Kudos
Reureu
Level 10
‎Sep 15, 2009 10:19 AM

I reckon you should try to understand why your custom actions work fine in the UI sequence and not in the execute sequence, but that's only my opinion.
Regards
0 Kudos