Hello Elizabeth,
Thanks for the sent project.
After further investigating this, I was indeed able to replicate this behavior. This is caused by the fact that you are using an older version of Advanced Installer (9.0.1).
As you could have noticed, there are three types of launch conditions, these being as it follows:
- System
- Software (also known as predefined)
- Custom
In the previous version of Advanced Installer (15.0.1 and below), the option from the
"Prerequisites" page was called:
Check predefined launch conditions before searching for prerequisites
meaning that only the
predefined launch conditions are checked before launching the prerequisite(s). Furthermore, this means that the custom launch condition that we have created is excluded.
However, starting with version 15.0.1 of Advanced Installer, the option is no longer called like above, it is called:
Check launch conditions before searching for prerequisites
which means that the custom launch conditions are now also checked before launching the prerequisites.
With that being said, this is the reason why your launch condition is checked just after your prerequisite is installed.
In order to make this work, you can update Advanced Installer to our latest version (15.8), which can be downloaded from our "Download" page:
https://www.advancedinstaller.com/download.html
Hope this helps.
All the best,
Catalin
FOLLOW US
Get the latest news in Application Packaging