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.

Modern-day application packaging often relies on free, open-source scripting methods, and one of the most widely adopted is the PowerShell App Deployment Toolkit (PSADT). However, there are cases where PSADT alone is not sufficient. In such cases, the Advanced Installer Architect steps in to complement the workflow of an application packager.

Software updates are an important part of keeping applications secure, stable, and competitive. But they also serve as a valuable business tool, as each new release is an opportunity to remind customers of your product and encourage them to maintain or renew their subscription.

Customizing the App Installer UI used to require manually editing an XML file and adding it to your MSIX application. With Advanced Installer, however, you can do the customization directly from its graphical user interface, no XML editing is required.

Windows fonts are a set of digital files that define how text appears on the screen or in print.

The Windows services are apps that run in the background of the Windows operating system without direct user interaction. But how do you build and install a .NET-based service?

Advanced Installer 23.1 introduces AppInstaller UI customization, allowing you to design a unique installation experience directly from our graphical interface. No more manual XML editing — you can now configure the installer window title, checkbox positions, accent colors, logos, button text, and alignment options with just a few clicks.

In a previous article, we covered the software packaging and testing checklist, along with best practices for follow up.

The operating system manages Windows Services, the background processes that can run continuously without user interaction.

Environmental variables, as their name implies, are variables that specify the environment in which a program runs.

How did I end up here? Well, I wanted to build a Windows service that would create an SSH reverse tunnel with a PEM-formatted private key, PowerShell, and the Non-Sucking Service Manager (NSSM). I never expected the biggest hurdle would be invisible line endings and encoding quirks.

So, you’re wondering how to run custom code during the installation of an EXE generated with Python.

Back in March 2018, Microsoft announced the MSIX packaging format and introduced Advanced Installer as the first recommended tool for creating MSIX packages.

In a previous blog article, we explored Suite Installer, a new feature in Advanced Installer available starting with version 23.0. We discussed how to create Suite Installer applications, discovered the wide range of visual customization options for each bundled application, and presented some practical use cases.

Launching your application is such an exciting milestone, but soon you realize that distributing an executable means more than simply sharing it. I cannot stress enough how important it is to make sure your users have a smooth experience from installation to updates, even more so if your users are redeploying your software within a complex IT environment.

Software deployment is the process of managing software within organizations. It generally refers to the activities and procedures involved in making applications available for installation to users or performing mass rollouts of a specific application.

The Windows Registry acts, or can be conceived as a structured database of the operating system where Windows and many programs store configuration settings.