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).

One of the main things we need to consider when performing a Major Upgrade is how we will backup and restore our previous files and folders.

One of the most asked questions in the industry is related to CAB files and what embedding options these have within the WiX Toolset.

In this post, we will address installer updates with a focus on the most common scenarios you may encounter when performing a small, minor, or major upgrade.

We have a list of Wix-related articles meant to help developers navigate through the tool in a seamless way. From implementing upgrades with WiX to embedding CAB options in MSI - you can find a lot of helpful materials on our main WiX page.

Do you need your installer to keep its current build version? In this article, will go through all the steps you need to set your WiX installer version to the current build version.

An important characteristic that we've highlighted in our series of posts about Windows Installer XML Toolset (WiX) is that it doesn't have a GUI. It builds the Windows Installer package with the information defined in the WiX source file (XML based).

Over the years, we've received many questions regarding how Custom Actions work with PowerShell scripts in MSI.

Many of us are aware of the importance of securing our applications and how digital signatures are a solid way to avoid security breaches. For those looking into MSIX, you must know that Microsoft enforces digital signature for all packages within this technology. There is no exception.

Your application's installer is the very first direct interaction of users with your product. And, a positive first impression is essential for the success of any software.

Many applications keep settings or configurations in files that later get stored in per-user based locations, such as %appdata% or %localappdata% folders.

In this article, we will explore what happens during a Windows Installer registration and what are the repercussions that appear if you don't register your MSI during installation.

Applications often require different types of permissions to operate smoothly - so adding permissions to files, folders, and registry keys is a standard practice in MSI.

In my experience, CustomActions can be difficult to add and set up, especially in MSI, often requiring reviewing lengthy documentation or dealing with unexpected failures or bugs. If you started your career prior to the App-V and MSIX era, you have probably come across various applications installers that required reverse engineering work.

Up until 2020, Windows Services were not supported in MSIX -- which represented a blocker for organizations looking to transition their applications (that used Windows Services) to MSIX technology.

TL;DR: Let's put it bluntly, you should never set a CustomAction to “Immediate” when you intend to change the system state.

A firewall is a network security system that can be found on any modern operating system. It's purpose is to act as a barrier against network-based intrusions, to monitor and control incoming and outgoing traffic following an organization's predetermined security rules.

Release management and version control go hand in hand when delivering quality software, whether you are a solo developer or part of a development team.

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.