Menu
▾
▴
#1076 Command line silent flag (/S) is not always honored
In specific cases where the installer can't read itself in loadHeaders(), a message box will be displayed ("Error launching installer" or "Installer integrity check has failed ...") even if the user specified /S on the command line. This is because g_exec_flags.silent is only updated after the first header, containing script flags, is read. Presumably, this is done so the user can't skip fatal errors with /NCRC. It would not make sense to let the user skip a failure to read the data, only checksum failures.
To easily reproduce this, copy an installer into C:\windows\system32 on Windows x64 and run it with /S. See bug [#1075] for details.
Even after fixing this, a message box may still pop-up if the script has
SilentInstall silentbut the user doesn't pass/S. The same use-case applies. If the installer can't itself, it can't read the flag set by the script.