ianh
Posts: 2
Joined: Mon Jun 26, 2023 4:27 pm

Invalid Advanced Installer version detected

Hi all,

We've been using AI for a number of years and have integrated it into our Azure build pipelines, but we are stumped by a new error we're getting during the msi build stage.
Something must have changed outside the .aip (no changes there), but we have a complex environment so it's proving difficult to track down. Any advise on what this error means would be most appreciated.


Starting: Build branded Data Studio exe
==============================================================================
Task : Advanced Installer Build
Description : Build setup packages using Advanced Installer.
Version : 2.0.9
Author : Caphyon
Help :
==============================================================================
Downloading: https://www.advancedinstaller.com/downloads/updates.ini
##[error]Invalid Advanced Installer version detected. Minimum required version: 18.3. Detected version: 17.9.
Finishing: Build Data Studio exe
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Invalid Advanced Installer version detected

Hi,

To ensure the best compatibility and support for our customers, starting with the latest release our official extensions are limited to work with Advanced Installer versions released within the last 24 months. This way our team can ensure the we offer best integration capabilities and limit the number of potential issues that might appear when connecting very old versions of Advanced Installer with our latest extensions.

However, this change will be reverted for the moment as discussed in the link below:
https://github.com/Caphyon/advinst-vsts ... 1608978020

I'm sorry for the inconvenience!

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ianh
Posts: 2
Joined: Mon Jun 26, 2023 4:27 pm

Re: Invalid Advanced Installer version detected

Thanks for the quick reply - we now know the cause of the problem. We await the change to the AzDo plugin and will rebuild when it's done - hopefully later today.

It is important to note that we (like many of your customers it seems) developed an installer a while ago which works perfectly for our needs, and which is deeply embedded in our pipelines.
There is no motivation for us to dedicate resources to upgrading it at this point in time, so we would like to continue using it without modification for the foreseeable future.
If you wish to drop support for older AzDo plugins please do so, but do not force us into upgrading something that is not broken.

We are otherwise very happy with Advanced Installer.

Best regards,

Ian
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Invalid Advanced Installer version detected

Hi Ian,

Thank you for your feedback. We will investigate the option to keep multiple versions of the DevOps extension available, but at the moment the Azure DevOps marketplace doesn't provide support for this. We will keep you informed about our further actions!

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
SimLoe
Posts: 69
Joined: Thu Mar 12, 2020 11:37 am

Re: Invalid Advanced Installer version detected

Hello,

We have been using Advanced Installer version 21.4 in our Azure DevOps build pipeline for quite some time. This version has been thoroughly validated in our environment and is part of a stable, production-proven release process.

Since today, the Azure DevOps task reports that version 21.4 is no longer supported. Effectively, this forces us to upgrade to a newer version in order to continue building our installers.

I would like to express serious concern about this situation.

We have purchased a perpetual license, including maintenance. From our perspective, this should allow us to continue using a specific version that has been tested and approved internally — especially in CI/CD environments where reproducibility and stability are critical.

A forced upgrade introduces significant operational risk:

We would need to update the build pipeline immediately.

We would have to revalidate and regression-test our installer.

Historically, we have experienced situations where newer Advanced Installer versions introduced regressions or behavioral changes that affected our setup project.

If this had occurred right before an important production release, we would have been blocked without warning.

In a CI/CD context, deterministic builds are essential. Many teams intentionally pin toolchain versions to avoid exactly this type of disruption.

Could you please clarify:

Is this restriction coming from the Azure DevOps extension itself?

Is there a supported way to continue building with an older installed version (e.g., via CLI)?

Is there a long-term plan to avoid forced version upgrades in build environments?

We fully understand the need to move the product forward, but build infrastructure should remain predictable and controllable by customers.

Thank you for your clarification.

Best regards,

Simon
Liviu
Posts: 1419
Joined: Tue Jul 13, 2021 11:29 am
Contact: Website

Re: Invalid Advanced Installer version detected

Hello Simon,

Thank you for your detailed message and for sharing your concerns regarding version stability and reproducibility.

The restriction you encountered comes from the Azure DevOps task, which now requires a supported version of Advanced Installer to ensure compatibility, security, and reliable integration. Versions older than two years, such as 21.4, will no longer run in the Azure DevOps task, which is why you are unable to continue building with that version. Please note that warnings about outdated versions appear in the build logs before the version is blocked, so teams have advance notice to update.

We strongly recommend keeping your Advanced Installer version updated at least once per year, primarily for security improvements, bug fixes, and compatibility with modern environments. For reference, you can review our security improvements and fix history here:
Advanced Installer Security Fixes Retrospective

If you update to the latest version, the Azure DevOps task will continue to function reliably, and your builds will avoid any unexpected warnings or issues.

The decision to discontinue support for older Advanced Installer versions is primarily driven by security and platform integrity considerations.

Continuing to allow execution of outdated builds could expose users to potential vulnerabilities or inconsistent behavior when interacting with newer environments and APIs.

Let us know if you have any questions.

Best regards,
Liviu
________________________________________
Liviu Sandu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
SimLoe
Posts: 69
Joined: Thu Mar 12, 2020 11:37 am

Re: Invalid Advanced Installer version detected

Hello Liviu,

Thank you for your response and for clarifying that the restriction originates from the Azure DevOps task.

However, I would like to reiterate that this policy is problematic for us from an operational and contractual standpoint.

We understand and appreciate the importance of security improvements and platform integrity. At the same time, we deliberately pin toolchain versions in our CI/CD environments to guarantee deterministic and reproducible builds. This is standard practice in professional software delivery.

What concerns us is not the recommendation to upgrade — that is entirely reasonable.

What concerns us is the enforcement.

If version 21.4 is still available for download and we hold a valid perpetual license (including maintenance), it should remain our decision whether and when to upgrade, especially in a controlled build environment.

Not every security fix is relevant to every use case. In our scenario, the build runs in an isolated CI environment and produces signed installers. We evaluate risk in context. A blanket two-year cutoff enforced via the DevOps task removes that evaluation from the customer and effectively introduces an upgrade requirement by technical restriction.

The two-year policy also feels arbitrary from the outside. If this is a firm policy moving forward, it would be helpful to understand:

Is this two-year window guaranteed and documented as an official support lifecycle?

Will all future versions be blocked exactly two years after release?

Is there a way to opt out of this enforcement and explicitly accept the risk of using an older version?

We fully support progress and security improvements. What we do not support is a mechanism that can potentially block a production release with limited flexibility — especially when stability of the installer toolchain is business-critical.

In our experience, some upgrades have introduced regressions affecting existing projects. This is precisely why we control the timing of updates and revalidation internally.

We would strongly prefer:

Either a non-blocking warning mechanism (instead of hard enforcement),

Or an officially supported way to run a pinned version in CI (e.g., via CLI without task-level restrictions).

We are not asking to avoid updates indefinitely. We are asking for control over when they occur.

I would appreciate further clarification on whether such an option exists or could be considered.

Best regards,
Simon
Liviu
Posts: 1419
Joined: Tue Jul 13, 2021 11:29 am
Contact: Website

Re: Invalid Advanced Installer version detected

Hello Simon,

If you want to use an older version of Advanced Installer in your pipelines, then you would need to use the previous version of our plugin, 2.*.
v2.png
v2.png (108.55 KiB) Viewed 8628 times

However, please note that this version is no longer maintained.

Best regards,
Liviu
________________________________________
Liviu Sandu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”