Many applications rely on INI files for configurations. In some scenarios, you may want to allow users to define specific configuration values during the installation process and automatically write them inside the INI file.

I remember when Microsoft released the MSIX technology in 2018, and Advanced Installer was the first application packaging tool to support it.

Every application needs a way to store its settings, which exist outside of the application’s code.

Although rarely considered, a cfg file is an essential component that keeps software running as expected by users.

Group Policy is a powerful tool for managing Windows Environments, and we’ve previously discussed how you can deploy an MSI using GPOs.

Digital signatures have grown in popularity and acceptance in the industry and are now required in some cases, such as with MSIX packages. This ensures that the software delivered is secure and trustworthy.

In 2018, Microsoft announced MSIX as the next big thing: a single installer that will replace MSI, EXE, and APP-V.

Digital Signing should be a formality for professionals. It’s been almost 30 years since the first software was digitally signed but we still have many users who don’t know how or why they should use a code signing certificate. We need it to protect their intellectual property and enhance the cybersecurity of their end-users.

Have you recently noticed unexpected User Account Control (UAC) prompts when launching MSI-installed applications, especially when using advertised shortcuts or opening associated files?

In a previous blog article, we discussed what an EXE setup file is, the difference between EXE and MSI installers, and other general details related to Windows’ setup.exe.

In April 2025, version 6.0.0 of WiX Toolset introduced the Open Source Maintenance Fee (OSMF), and since then, IT professionals have been reviewing and reassessing how they build and maintain their installers, as well as how they budget for their infrastructure.

Understanding how actions are sequenced when building or customizing Windows Installer (MSI) packages is essential.

What version of Windows do I have? This is a far more common question than we’d think. Checking the OS version is important in software packaging and deployment, especially in the modern world. Each new OS version may include new functionality that third-party software developers can use. In cases like this, it is recommended to first check the actual OS version before installing or updating the software.

Visual Studio is a complete development environment for writing, testing, and deploying applications across different platforms. Beyond coding, it also supports creating MSI installers directly within the IDE.

One of the greatest things about software packaging is the variety of choices available to you to achieve your objectives. However, having too many alternatives to choose from can make it challenging to pick the best one for your requirements.

Creating installer packages sometimes requires presenting item lists in custom dialogs, where data must line up cleanly rather than drift into uneven text blocks. Advanced Installer offers controls such as ComboBox, ListBox, and CheckListView. However, to correctly align columns in these controls, there are some steps you should be aware of.

Java applications are compiled into JAR files, which need the Java Runtime Environment (JRE) to run. However, JAR files cannot be executed as standalone files.

The Windows Installer service is a standard in the industry when it comes to software packages, but it doesn’t mean it’s not prone to errors.

Customizing the App Installer UI used to require manually editing an XML file and adding it to your MSIX application. With Advanced Installer, however, you can do the customization directly from its graphical user interface, no XML editing is required.

The Windows services are apps that run in the background of the Windows operating system without direct user interaction. But how do you build and install a .NET-based service?