Custom Action to be executed on _every_ run (not only first installation) - Advanced Installer Community
Jakob1981
Posts: 46
Joined: Fri Jun 13, 2014 10:52 am

Custom Action to be executed on _every_ run (not only first installation)

Hello everyone,

I have an exe file which executes a custom action (VBS code)

This works fine - on installation, the custom action is executed correctly.

However - when I start the exe file for the second time, this custom action is not executed anymore. I guess it is because the exe itself is already installed?

I tried various scenarios
- I set a combination of Execute on "Install" / Condition "true"
- I tried immediate action, deferred actions, actions on commit....
- I moved the custom action - from to be executed during Install Execution Stage to Finish Dialogs Stage...

Nothing helped - it always executes the custom action only on the first installation

It would be very much appreciated if someone could point me in the right direction. Preferable with a screenshot indicating which settings I need to activate.

Thanks a lot !!

Best regards,
Jakob
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Custom Action to be executed on _every_ run (not only first installation)

Hi Jakob,

I'm not sure why your custom action is executed only on the first install. Normally, when the EXE package is started for the second time, it should start in the maintenance mode, so you can "Change", "Repair" or "Remove" your product. Do you want the custom action to be executed in those cases, too?

It should be executed every time if the "Install", "Uninstall" and "Maintenance" options are checked for it in the "Execution Stage Condition" section.

Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com, so we can investigate them?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jakob1981
Posts: 46
Joined: Fri Jun 13, 2014 10:52 am

Re: Custom Action to be executed on _every_ run (not only first installation)

ah - I don't want the user to see "Repair / Change / Remove" options, so I suppressed the UI as much as possible - I want to be able to start the executable over and over again, with the custom action always being run

I will try again with "Maintenance" enabled and if this does not work, I will forward you the aip file

thank you for your help!!
Jakob1981
Posts: 46
Joined: Fri Jun 13, 2014 10:52 am

Re: Custom Action to be executed on _every_ run (not only first installation)

YES! With maintenance enabled, it works! :) Thank you !!!
Jakob1981
Posts: 46
Joined: Fri Jun 13, 2014 10:52 am

Re: Custom Action to be executed on _every_ run (not only first installation)

Another question...

I want to completely suppress the UI
meaning, I do not want to show the "extracting files...." etc, etc at each and every start of the exe file - I simply want it to run without showing anything

I use Inline Scripting and suppress the console with VBS (which works) - still, the "extracting files...." before remains

is there any way to avoid this? I already enabled "limited ui", but this only removed the dialogues, not the "extracting file..." stuff

any help will be appreciated! thank you !!
Last edited by Jakob1981 on Fri Mar 03, 2017 1:35 pm, edited 1 time in total.
Jakob1981
Posts: 46
Joined: Fri Jun 13, 2014 10:52 am

Re: Custom Action to be executed on _every_ run (not only first installation)

Found Bootstrap UI -> Silent Install

Now the "extracting files..." dialogue is removed, but "Please wait while Windows configures XXX ...." remains...

another hint for that one? :)
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Custom Action to be executed on _every_ run (not only first installation)

Hi Jakob,

I'm glad you solved the first problem.

If you want to suppress all the UI dialogs of your package you need, indeed, to set the Bootstrapper UI level to "silent" and also send the "/qn command line to the MSI package. You can send it in the "Command line" field from the "Builds" page or you can send it directly through the console (e.g. Command Prompt).

You an also launch the package form a console with the "/exenoui /qn" command line. For example: myPackage.exe /exenoui /qn

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”