Check our other helpful areas that might answer your question

Hello Zapp and welcome to Advanced Installer forums, I have tested this scenario, but I was unable to reproduce the described behavior. Upon further investigation, I could indeed notice that we deliver two signtool.exe executables. Their location is: WinDir:\Program Files (x86)\Caphyon\Advanced Inst...

Hello and welcome to Advanced Installer forums, 1. This can be achieved by going to "Licensing" page and checking the "Use Serial Validation Option" from under the "Package Serial Validation" section. 2. By doing the above, a dialog will be added in the "Dialogs" page --> "UserRegistrationDlg" . Thi...

Hello Alexander, The ProgramFIlesFolder property resolves based on Operating System bitness. It resolves to: C:\Program Files C:\Program Files (x86) -- on a 64-bit machine If you want to set it to "C:\Program Files (x86)" on x86 machine and to "C:\Program Files", you can condition it in your script,...

Hello and welcome to Advanced Installer forum, As you may know, the installation consists of two processes - client and server . Client represents the process where the UI is spawned and the server represents the process where the installation happens (after you press the "Install" button) The ID (i...

Hello Alexander, Could you please try to retrieve the "ProgramFilesFolder" property instead? The AI_ProgramFiles is a custom made property and I am not quite sure if you can retrieve its value. With that being said, your script could look like this: $programFiles = AI_GetMsiProperty ProgramFilesFold...

Hello, Thank you for your followup on this. In the article you have given me, it states that: The other problem is that an MSI has a master table including a ‘platform’ field, and initially, I couldn’t work out what to put in there. If I set it to ‘Arm’ or ‘Arm64’, then msiexec.exe reported that the...

Hello Smruti and welcome to Advanced Installer forum, Unfortunately, we do not have predefined support for your task. You can, however, display all the features available using the predefined "OptionalFeatsDlg" dialog (go to "Dialogs" page --> select "WelcomeDlg" --> "Add Dialog" button from the too...

Hello, I figured out how to pass all the values of each user inputted parameter to the .msi. I needed to specify each parameter in the install command lines. I am glad you figured out how to pass the parameters to your prerequisites. In what regards your second question, please allow me to explain t...

Hello and welcome to Advanced Installer forums, Unfortunately, I am not very familiar with the ARM architecture. First of all, just to make sure, in order to repackage your application, are you using our Repackager.exe tool or the "EXE to MSI" project template? As I am not familiar with the ARM arch...

You are always welcome!

I'm glad that helped.

Best regards,
Catalin

Hello Joe and welcome to Advanced Installer forums,

Unfortunately, I am not quite sure I understand your scenario here.

Could you please give me a step by step test-case which I can follow in order to reproduce this?

Looking forward to hearing from you.

Best regards,
Catalin

Hello, Since you have mentioned that you have a suite installation, I imagine that the features you are talking about are actually feature-based prerequisites (please correct me if I'm wrong). If that is the case, the order is actually dictated by the prerequisite's order. For instance, let's say yo...

Hello,

i can't see ExtractFilesFirst property in install parameter page

The property is not there, by default. You have to add it and set its value.

Hope this helps.

Best regards,
Catalin

You are always welcome, Robert.

Always my pleasure to help.

Best regards,
Catalin

Hello Jürgen, The mentioned error means: UPDATE_INSTALLATION_FAILED Most probably, the installation condition of the update is wrong. After the update is installed, the condition is checked and, if false, this error is returned. There are two ways in which this can be avoided: 1. create a condition ...