When it comes to MSI technology, users might encounter a blocking point with the "Updating component registration" message during the installation process. This can be frustrating, but there are several solutions you can try to fix this issue. Let's explore them in this article.

At Advanced Installer, we’ve been hosting weekly Tech Talks for over a year, where our developers share key insights, lessons learned, and in-depth explorations of topics that help us grow as a team. These sessions have been invaluable for us, and we’re excited to share some of the best takeaways with the wider developer community.

SAP GUI is the graphical user interface client used to access SAP systems. It’s an essential tool for organizations that rely on SAP applications. Automating and customizing the installation process not only saves time but also ensures consistency across multiple systems.

One common question packagers often ask themself is what type of installer to use when patching an application.

A continuous activity when it comes to any software application is providing security, improvements, and functional upgrades. But what happens if the end-user has made his personal application configurations and a new update arrives? How can we make sure these user preferences are preserved after an update installation?

ASP.NET applications are not something new in the world. However, having a powerful tool that streamlines and deploys your ASP.NET applications is a must these days.

MSIX packaging is a modern solution for deploying applications on Windows devices. However, if you want MSIX-deployed apps to support auto-updates via .appinstaller file on Windows Server, you have to manually install the App Installer Tool.

Let’s start with the basics: Microsoft Endpoint Configuration Manager, or MECM (formerly SCCM), is one of the tools that IT admins in larger organizations rely on heavily. It helps you manage devices, deploy applications, enforce security policies, and keep everything running smoothly across the entire IT environment.

As an IT professional, I noticed throughout the years how software packaging has evolved from mostly repackaging applications to making them enterprise-ready, to customizing and integrating them into configuration management tools directly. All by applying the repackaging technique only on those exceptional occasions when silent installation is impossible.

PowerShell commands play a key role in software packaging and deployment by automating and managing deployment tasks.

At Advanced Installer, we’ve been hosting weekly Tech Talks for over a year, where our developers share key insights, lessons learned, and in-depth explorations of topics that help us grow as a team. These sessions have been invaluable for us, and we’re excited to share some of the best takeaways with the wider developer community.

Microsoft Deployment Toolkit, commonly known as MDT, is a robust solution for IT professionals needing to deploy Windows operating systems and applications across multiple devices efficiently. Its primary goal is to simplify and streamline the deployment process, ensuring consistency and reducing the likelihood of errors.

As we head into 2025, the application packaging world feels familiar—like a well-worn tool that still gets the job done. While there’s always talk of “the next big thing,” much of what worked in 2024 will keep working. Let’s break down what to expect.

When creating an installer for your application, it's often necessary to read configuration values during the setup process.

Updates are crucial in software development, enabling developers to add new features, fix bugs, and enhance security. Regular updates are essential to maintaining the performance and reliability of applications.

Group Policy Objects (GPOs) are a powerful feature of Windows environments that enable administrators to control and configure operating systems, programs, and user settings across a network.

Those of you already familiar with Intune might have noticed that, by default, Intune runs the application installer process in a 32-bit context. Unlike SCCM, Intune doesn’t offer an option to start app installation in a 64-bit context with a simple checkbox.

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.

PowerShell scripts are an effective tool for automating tasks, but with great power comes a need for security.

Software applications often require certain components, like runtime environments, databases, or other software to run properly. It’s important to make sure the right versions of these components are installed before the main application runs.