2 problems with SETUP.EXE command line - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

jerryz
Posts: 13
Joined: Fri Mar 08, 2013 11:51 am

2 problems with SETUP.EXE command line

Hello,
We are using evaluation version of AI and we created testing installation package - 32bit, EXE bootstrapper. Unfortunately we have 2 following problems when executing installer from command line (console).

1) "setup.exe /exenoui" seems to to have no effect - UI is always displayed.

2) "//" marker seems not to work if no preceding arguments are present.
If we execute command "setup.exe /x // /l*v log.txt" then uinstallation fails and log contains these 2 lines:
MSI (c) (D8:90) [11:31:32:954]: Note: 1: 2203 2: // 3: -2147286788
MSI (c) (D8:90) [11:31:32:954]: MsiOpenPackageEx is returning 123.

BUT if we use any preceding argument like: "setup.exe /exenoui /x // /l*v log.txt" then marker works.

Do you have an idea what could be a culprit of these issues and how to solve them?

Thanks,
J
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 2 problems with SETUP.EXE command line

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.
1) "setup.exe /exenoui" seems to to have no effect - UI is always displayed.
Please keep in mind that the "/exenoui" switch will hide only the EXE bootstrapper dialogs (e.g. the pre-install prerequisites wizard dialogs). If you want to launch the embedded MSI without UI, then you can add the /qn switch in the "MSI Command Line" field from "Media -> Configuration" tab.
2) "//" marker seems not to work if no preceding arguments are present.
If we execute command "setup.exe /x // /l*v log.txt" then uinstallation fails and log contains these 2 lines:
Indeed, this is an Advanced Installer issue. Please take a look on our "Documented Command Line Uninstall Fails With AI Bootstrapper" thread which debates this issue. We are aware of it and a fix will be included in the next version of Advanced Installer (which should be released soon).

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”