Track Program Installer Modifications - A Comprehensive Guide

Understanding Application Installation Processes

Have you ever wondered what actions are being performed during an application's installation, as the progress bar advances? Maintaining detailed insight into these processes requires utilizing appropriate monitoring tools.

The Source of Today’s Inquiry

This particular question and its subsequent answer originate from SuperUser. It’s a segment of Stack Exchange, a collaborative network of question-and-answer websites.

Stack Exchange functions as a community-driven resource for knowledge sharing. Users contribute by posing questions and providing answers across a wide range of topics.

SuperUser specifically focuses on questions related to advanced computer usage and troubleshooting. It’s a valuable platform for both novice and experienced users seeking technical assistance.

Therefore, the following information is derived from the collective expertise found within the SuperUser community. It provides a deeper understanding of what happens behind the scenes during software installations.

Monitoring tools are essential for observing the changes made to your system during installation. These tools can reveal file creations, registry modifications, and other critical operations.

By utilizing these resources, users can gain a comprehensive view of the installation process. This knowledge empowers them to troubleshoot issues and ensure system stability.

Identifying Changes Made by Installers

A SuperUser user, Gregory Moussat, has posed a question regarding the ability to monitor the actions of software installers.

Specifically, he is interested in understanding which files, folders, and registry entries are created, deleted, or altered during the installation process.

The Problem of Poor Documentation

Moussat highlights a common issue: many professionally developed applications lack sufficient documentation.

This deficiency makes it challenging to properly configure, update, and manage these programs effectively.

InstallRite: A Previous Solution

The program InstallRite previously offered a solution by capturing a system “snapshot” before and after software installation.

By comparing these snapshots, users could determine exactly what changes the installer had made.

Furthermore, InstallRite facilitated the creation of customized uninstallers.

The Need for a Replacement

Unfortunately, InstallRite is no longer actively maintained and hasn't received updates since 2008.

This has led to a search for a suitable alternative tool that can provide similar functionality.

Seeking Current Alternatives

The core of the inquiry centers around identifying a modern tool capable of replicating InstallRite’s capabilities.

Users require a method to effectively track and understand the modifications made to their systems by software installers.

Finding Hidden Software Changes

Synetech, a valued contributor, suggests ZSoft Uninstaller as a preferred tool for identifying software modifications. It’s a free utility that excels at pinpointing changes without the excessive clutter often found in other programs, even those that are commercially available.

Alternative Uninstallers

Another recommended option is PC Magazine’s InCtrl 5, recognized for its effectiveness – enough to earn Microsoft’s approval. However, distribution of InCtrl 5 as a free download was discontinued several years ago, though existing copies remain accessible.

The newer version, InCtrl X, is a paid product costing $8. Further details about InCtrl X can be found on its official website.

Manual Investigation Techniques

Prahlad Yeri offers several methods for manually investigating the actions of an application during installation. Determining the complete extent of an installer’s changes can be challenging, potentially requiring reverse-engineering of its code.

Key Areas to Examine

• Check the Program Files directory for application-specific folders, typically located at C:\Program Files\AppXYZ.
• Inspect system folders, such as C:\Windows\System32, for any libraries (DLL, OCX, or TLB files) placed by the application.
• Utilize CCleaner to identify newly created registry entries and other system modifications, including MIME type registrations.
• Examine the .NET Global Assembly Cache (GAC), found in C:\windows\assembly, for registered .NET assemblies.
• Don't overlook common locations:
  • Start Menu and desktop shortcuts.
  • Files within the C:\users\USER-NAME\Application Data folder (visible through CCleaner).
  • Startup menu entries and modifications to boot.ini (accessible via msconfig).

Combining the use of snapshot comparison tools with these manual checks provides comprehensive coverage. The complete discussion on this topic is available on SuperUser. Share your own tools or techniques in the comments below.