Let's consider that the other application's installer cannot be fixed and this should be handled in the installer of the current application. The UX of the other installer is even worse, since if it is ran in a normal mode with user interaction enabled there is no option - a checkbox, to allow/disallow the automatic run of the installed other application. The best solution for sure is to fix the other application's installer, so that not to start the other application automatically. Closing the started other application manually makes the installer of the target application to continue the installation progress. I am running a licensed professional version of BitRock InstallBuilder 17.4.0 ().Īny suggestions why the other BitRock InstallBuilder made installer could be stalling?Īn important fact that I've noticed is, which is probably an incorrect behavior of the other application's installer, is that it is automatically started after being installed and probably the element considers the automatic start of the other application as a prolongation of its installer. Tried dumping the $ but it was surprisingly empty - it should contain some number. WAIT other-app-installer.exe -mode unattended -unattendedmodeui minimalWithDialogsīut this time the installer of the target application throws an unspecified error. Installing another BitRock InstallBuilder made installer . Runs the application provided as an argument in blocked mode and one can proceed working with the console as soon as the other application's installer exits/finishes. Start /WAIT other-app-installer.exe -mode unattended -unattendedmodeui minimalWithDialogs The other application's installer exits correctly when being ran from the command-line with the command: The main application's installer still stalls - the installer is repsponding but does not proceed ahead with the rest of the installation steps.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |