In this article, we will learn what “Log on as a Service" is, when and where to use it, and how to enable it.

Do you want to transfer CustomActionData to a CustomAction in WiX? We'll show you how in this article.

In this article, we'll talk about how Windows Installer defines the directory location of an installation, what the INSTALLDIR and TARGETDIR properties are, and what is the difference between them.

Uninstalling a package is as important as installing it, so it's crucial to handle it with care.

Command-line switches should be present in every setup installer. When it comes to MSI installers, they support command line switches by default.

Process Monitor is probably one of the most used tools by IT Pros to debug applications and check installations. We mentioned Process Monitor in our MSI Packaging Training free e-book but this time around, we want to explore it further. We will discuss its prerequisites and share how you can get started with it.

Deploying major upgrades for an MSI package created with WiX Toolset is simple. However, there are a few boxes you need to check to make sure you're doing it properly. We'll share them with you in this article!

When uninstalling an application, Windows Installer removes by default only the files that were created during the installation process. But, how about the files that are created after the installation?

When you create an installer using the WiX Toolset, there are instances where you may want to set a custom action to run under specific conditions, such as uninstalling an application, installing an application, or running a custom script.

When you define shortcuts in WiX Toolset, their default installation is non-advertised (Standard Shortcuts).

Software packaging is the process of building an installer that includes all your applications' resources and can be used to distribute them on the end-user devices.

A ProductCode is made up of string GUIDs containing numbers and uppercase letters.

Depending on whether we're installing or updating an application, we need to use different types of files. For instance, we use MSI files when installing Windows applications, but if we want to make a small update, we can use an MSP file.

Silent installs are the preferred delivery method within an enterprise environment given that end-users don't have to worry about installing or having technical knowledge and just focus on using the software products.

In some instances, when uninstalling an MSI, you may notice that some files and folders stay in the system and are not removed.

We use MSI or EXE files whenever we install a Windows application, so we're pretty used to them. But, what is an MSI file, and what makes it different from an EXE file? What’s the easiest way to open and edit an MSI installer?

If you are a System Administrator, IT Pro, or Developer, and want to find out how to perform a silent MSI or EXE installation – this article is for you!

We extremely recommend you to validate an MSI before attempting to install it for the first time.

In our previous article titled "How to automate the MSI building using GitHub Actions", we saw how you can use Advanced Installer's own GitHub Action to automate the build of your MSI packages.

In this article, we will take a look at how MSIX technology handles log files whenever an installation issue occurs.