Advanced Installer 24.1 introduces highly requested improvements, including a redesigned Custom Actions view for easier management, more flexible Azure Key Vault signing with new authentication options, and expanded PowerShell automation capabilities across multiple project areas.

Starting with Advanced Installer 24.0, you can add application prerequisites directly from the WinGet repository.

Let’s say you have an application that has multiple features, and you want to give the end user the option to select which one to get installed.

The user interface is a key part of any application, and the same applies to its installer.

We wrote a certain approach that you could use if you don’t want to publish your MSIX package to the Microsoft Store and instead want to use your own website.

Advanced Installer 24.0 in summary:

Advanced Installer 24.0 is the biggest release of 2026. This version brings you major new features and improvements, standing on over 20 years of application packaging experience.

Starting with Advanced Installer version 24.0, you can include prerequisites in your installer directly from the WinGet repository.

Before version 24.0, when you published application updates with Advanced Installer, you had to host the updates configuration file and the corresponding installer package on your own server.

As an application packager, once you are done with your installer, it’s time for deployment, which is usually done via Intune, SCCM, or other configuration management tools.

We are very excited to inform you that, starting with version 24.0, Advanced Installer gets its own integrated AI Assistant!

If you’ve repackaged more than a handful of legacy installers into MSIX, you’ve probably noticed that in order to build an MSIX, you need to have at least one application defined before the package can go through. Even Advanced Installer has a hard stop when it comes to this because it will not let you remove all the applications inside the Application Details Page.

There may be cases when you have an in-house web application or simply a website, and you want to offer your users a true Windows desktop app experience.

It's 2012. I’ve just finished getting my IT bachelor’s degree, and I was eager to hop on an exciting opportunity.

Secure software distribution depends on digital certificates. They validate applications and guarantee that users receive software from trusted publishers.

Version 23.9 is now available and includes new capabilities for certificate validation, expanded virtualization support, improved registry component handling, and additional SBOM customization options.

Packaging a Windows app the “proper” way usually means creating a manifest file, generating assets, doing a test certificate, and signing the application, all before you can confirm that your application behaves correctly with a package identity.

At first glance, signing installers seems easy, and nothing could go wrong.

Advanced Installer 23.9 introduces Expected Identity OID for Updater certificate validation. This new option allows Updater to validate Microsoft Artifact Signing certificates using the certificate policy OID associated with the verified identity. It provides a more reliable alternative to matching certificate subject fields that may change after renewal.

Flutter has rapidly become a popular framework for building cross-platform applications.