Digital signing is an important stage of an application packaging cycle and can be achieved by code signing your own software’s certificates. By digitally signing your software, you prove your application’s authenticity and integrity upon installation and guarantee that the software you developed hasn’t been compromised or corrupted.

Microsoft recently came out with an MSIX-related packaging format called the MSIX Bundle, which includes safer and more reliable deployments as well as auto-updates and improved widespread support - which makes our life easier as application packagers.

Advanced Installer 17.5 brings you the most powerful GUI for creating and editing MSIX Optional Packages. Optimize your package downloads and deliver additional features on-demand, using the native MSIX platform.

Managing an infrastructure doesn’t only require updating software, creating OS deployments, or applying GPOs (Group Policy Object).

MSIX packages are installed by default per-user, and the option to provision per-machine MSIX applications is possible through SCCM - which is not yet available in Task Sequences.

In today's article, we're bringing a specific scenario into discussion and proposing the right solution to manage similar situations.

Application Packaging itself is just a small step within the whole process, starting with the application being requested by the business, and resulting in a finished product that is rolled out to production devices.

The latest version of Advanced Installer brings a lot of new powerful improvements that simplify your digital signing process.

If you missed out on our previous blog articles about MSIX, make sure to check out this comprehensive guide to get insights about the technology and the changes it brings to the industry. To continue understanding the different tools and best practices MSIX has, this article will go into the MSIX Packaging Tool. We discuss what it is, how it works, and finally, we will show a side by side comparison using our free Advanced Installer Express edition.

In a previous article , we went over handling the migration from System Center Configuration Manager 2012 to Configuration Manager Current Branch using the 1902 baseline version.

Environment variables are settings or paths that are set outside of a program and can be globally accessed by any software.

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.

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.