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

Starting with Advanced Installer version 23.0, you can bundle multiple applications into an installer that acts as an application store, allowing your users to choose which app to install.

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.

In a previous blog article, we discussed what an EXE setup file is, how it differs from an MSI installer, and other general EXE file particulars related to Windows setup.exe.

In this release, Advanced Installer introduces WinGet manifest generation, allowing you to create WinGet manifests directly inside the application, without the hassle of managing YAML files or external scripts. We’ve also expanded support for MSIX App Attach, enabling you to generate VHD, VHDX, and CIMFS images for modern deployment scenarios.

The message is clear: PowerShell is taking over the scripting world within the Windows OS. Until now, many different scripting languages have been used, with batch scripting being the most popular, and later replaced by VBScript.

AI is one of the best inventions of the past decades, as well as one of the most talked about topics across all industries.

If you’re an IT administrator managing multiple Windows servers, you may have heard of Remote Server Administration Tools (RSAT). RSAT is a collection of Microsoft utilities that let you manage Windows Server roles and features remotely from a Windows client machine — meaning you don’t need to log in to the server itself to perform administrative tasks.

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.

PowerShell is a flexible tool created to help in automating your tasks in any environment. The same scenario applies to Intune, where users can use PowerShell extensively to accomplish this.

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.

In the digital era, the capacity to remotely install software on computers is essential for any kind of infrastructure, regardless of its size.

In some cases, you may have to continue the execution of a certain PowerShell script after a device reboot. This applies to both local and remote execution environments.

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.

PSADT 4.1.X finally brings direct user interaction to Intune deployments, so no more ServiceUI.exe. The new Invoke-AppDeployToolkit.exe automatically detects active sessions, displaying messages and prompts right from Intune. But the new Defer feature doesn’t work on an exact timer; it depends on Intune’s own unpredictable recheck cycle.

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.

Automatically converting your App-V application to MSIX spares you from rebuilding it from the ground up.

Advanced Installer 23.2 delivers key enhancements across PowerShell automation, UI performance, and compatibility with the latest Windows and .NET versions.

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.

Converting PowerShell scripts into standalone executables with PS2EXE has always carried one persistent inconvenience: the external files.