In an enterprise environment, applications are often deployed via configuration management tools like Intune, SCCM (MECM), or similar. These installations typically occur in the system context because end users lack administrative privileges. As a result, user-specific registry keys under the HKEY_CURRENT_USER (HKCU) hive are not applied during the installation process.

VBScript (Visual Basic Script) is a scripting language introduced by Microsoft in the mid-1990s. It was designed to offer a lightweight scripting capability for web development and Windows administration. In October 2023, Microsoft announced the VBScript deprecation in upcoming Windows releases, making it available only as a feature on demand.

Navigating the Windows Registry can seem like wandering through a digital jungle. Fear not! Advanced Installer offers a user-friendly way to tweak registry keys and values.But what if you have a Custom Action in PowerShell or are a fan of the PowerShell App Deployment Toolkit (PSADT)? You might want to set registry key values using these tools.

Understanding custom actions can be challenging, and most beginner IT Professionals tend to “leave the chat” when custom actions are brought to the table. Without a doubt, MSI technology is complex, and best practices have evolved over the years, adding to the difficulty.

To enhance the security of your machines, it is crucial to properly define and configure the firewall rules, ensuring a safer environment.

Object Linking and Embedding (OLE) is a proprietary technology developed by Microsoft that enables developers to embed and link to other objects.

Do you need to execute your application (exe file) as an administrator or apply compatibility options to it?

MSI is a Windows Installer package format that uses Microsoft’s Windows Installer service to manage the installation (and uninstallation) of applications.

Often throughout the repackaging process, it's frequent to come across files featuring straightforward paths such as: C:\Program Files.

Custom Actions are user-defined actions that enhance the installation process by adding functionalities beyond what is offered by the standard Windows Installer actions. They are necessary when built-in options fail to meet specific installation requirements.

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

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.

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.

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.

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

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.

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

Although it’s a rare scenario - you might run into the situation where you need to continue the installation of a certain application after reboot. We are talking about a silent installation that doesn't require admin rights or any input from the user.