Publishing an application to the Windows Package Manager (WinGet) requires a manifest file that defines essential metadata, installer information, and localization details.

Registry keys play an important role in the Windows operating systems.They store configuration data and settings for both the system and applications. By adding registry keys, you can properly configure and optimize your app for each user’s system.

It is important to ensure that your Windows operating system is kept up to date in this age of technology. It is a matter that leads us to Microsoft Update Standalone Packages (MSU files), an essential element in the updating process of Windows.

Winget is a command-line package manager created by Microsoft for the Windows operating system. It enables users to search for, install, update, and uninstall software applications using the command line or scripts instead of a graphical user interface (GUI).

Ever faced annoying errors when trying to install something on Windows? You’re not alone.

The confusion of dealing with unsigned drivers can sometimes disrupt your software installation process. Windows typically raises a red flag when such drivers come into play, triggering a warning message that it can't validate the publisher's credibility.

Advanced installer Repackager allows you to repackage your application in multiple environments, such as the host machine, different types of virtual machines like VMware, Hyper-V, and now Windows Sandbox.

Ensuring your application is well-designed is one of the key methods to keep users engaged. They need to have a positive experience while using your app, therefore a poor design can drive them away.

Windows Forms is a UI framework used to create Windows desktop applications. This development platform provides a broad set of features to develop graphically rich and interactive applications, including a visual designer in Visual Studio.

Windows Presentation Foundation (WPF) is a powerful User Interface (UI) framework for building desktop client apps. It's a part of .NET and offers a multitude of helpful features, such as media services, controls, data binding, and security.

Recently, I was assigned to monitor a third-party application to detect when a workstation is unlocked or a user logs in. Additionally, if the monitor goes off, the monitored app should be started.

Throughout their entire history, MSI applications have used Microsoft Windows Installer as an installation and configuration tool provided with Windows since version 2.0 for Windows XP and proceeding to version 5.0 for Windows 7, 10, and 11.

To keep up with the evolution of technology, the architecture of the processors shifted from 32 bit to 64 bit, as did the operating systems.Due to the rapid technological advancements, the logic in the registry and file system changed as well.

Process Monitor is probably one of the most used tools by IT Pros to debug applications and check installations. We mentioned Process Monitor in our MSI Packaging Training free e-book but this time around, we want to explore it further. We will discuss its prerequisites and share how you can get started with it.

Get a quick 5,000 words introduction that will bring you up to speed with the latest packaging and deployment technology for Windows.

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

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.

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.