With App-V packages closing to end-of-life (2026), the reality of a transition to MSIX is much closer and many are starting to research the ins and outs of what it entails. Although we now know that MSIX is not an update to MSI, but a completely new technology, there are still some correlations that we'd like to address.

Starting with version 17.3, Advanced Installer natively supports Device Guard Signing. This feature is of most use for the vendors to prepare their software product installers to be used in enterprise environments.

The latest version of Advanced Installer brings more than 25 features and improvements across all editions. Modernize and increase the security of your release process with our Device Guard Signing integration.

When building a new version of an installation package, you should pay attention not only to adding improvements but also ensuring a seamless upgrade to the old version.

If you have ever wondered how fonts are installed in an MSIX package or if you want to master all MSIX concepts, you landed on the perfect page. In the following article, we’ll see how to add and register fonts so your package will be more impactful.

On a recent post, we explored how MSIX deployments are done via SCCM, covering the scenario when a per-user installation is needed.

For the past 10+ years, I have worked with various projects and types of organizations as an Application Packager. During that time, I have witnessed some "elementary" mistakes that could have been easily avoided by having a clear understanding of the end-to-end application packaging process.

Recently, in one of our previous articles, we covered how MSIX redirects user data to specific locations.

Recently, one of our users has asked us if it is possible to install, through Advanced Installer, a service under a Managed Service Account (MSA).

Version 17.2 of Advanced Installer brings you more than 20 features and enhancements ready to be discovered.

To help with the MSIX transition, Microsoft has released the Package Support Framework (PSF) - an open-source framework that enables you to apply runtime fixups for issues that might appear when migrating legacy applications that you don’t have the source code for.

You've finished building your MSIX application, and it's time to share it with the rest of the world.

Although not necessarily common practice, there are some instances where you would want to prevent users from uninstalling specific MSIX packages such as monitoring software that is required to gather data from all employees.

MSIX Modification Package is a type of MSIX package format introduced by Microsoft with the goal of decoupling customizations from the main application. Launched with the release of their MSIX packaging format, the MSIX Modification Package is an MSIX package meant to store the customizations of the application.

Building an MSIX package for your app? Use the table below to check what Windows version you can target, depending on the features you are using.

We have good news! Advanced Installer 17.1 comes with Digital Signature support for PowerShell scripts - you can now digitally sign PowerShell scripts to enhance your enterprise security policies.

Automation. A word heavily used around industries, especially the software one. A word that arouses great interest for every manager, service, or business owner.

Every new MSIX package we build allows us to learn more and improve the tools we build. The whole Advanced Installer team got involved.

Although it’s a rare scenario - you might run into the situation where you need to continue the installation of a certain application after reboot. We are talking about a silent installation that doesn't require admin rights or any input from the user.

As a standard, Advanced Installer automatically creates the components when generating the product package. The automatic process respects a strict set of Windows Installer rules, together with a series of best practices we have gathered from our customers during the years.