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.

What's the most efficient way to perform quick edits to an MSI package?

With Intune, Microsoft made it easier to deploy MSIX/APPX packages in your infrastructure.

In 2018, MSIX was announced by Microsoft as the new universal package format for Windows 10 apps with the later support on desktop, mobile, and other Windows 10 devices.

We've received inquiries from users that encounter issues with the SCCM cache folder.

Digitally signing your application is not only mandatory, it is an essential step to making your software secure and trustworthy.

We are so proud to announce Alex Marin’s brand new work: the MSI Packaging ebook - visit the link to get your free copy.

Sometimes we need to perform quick edits to our MSI packages without having to create a new project or going through the whole repackaging process.

During the installation process of WebApps, there are cases where users are asked to select an SSL certificate. This is because this certificate is used by the IIS elements.

We got a question in the Advanced Installer forum about the possibility of passing arguments to a service when the parameters are received from a configuration file, such as an .INI file.

Sometimes we need to have a single distribution package as an MSIX, which includes MSIX supported features along with MSI features that are no longer available (such as old drivers).

There are scenarios where you need to change a file version programmatically with each launch. To achieve that, we will set an installer property that changes with each release and then uses its value within your installer.