如何监控并记录含setup.exe、MSI的产品手动安装过程？

Great plan—documenting manual installs with monitoring is the gold standard for reverse-engineering enterprise app packaging, especially when dealing with multiple setup.exe, MSIs, and dependencies. Here’s how to execute this smoothly:

Pre-Install Preparation #

• Pick your monitoring tool: Process Monitor (ProcMon) is my go-to free option—it tracks every file system, registry, and process change in real time. For more focused install tracking, InstallWatch Pro is also solid. For MSIs specifically, enable verbose logging by running msiexec /i "path\to\installer.msi" /L*V "C:\logs\msi-log.log" to capture every installer action.
• Set up a clean test environment: Use a virtual machine (VMware, Hyper-V, etc.) and take a snapshot before starting. This lets you roll back to a pristine state if you mess up a step, ensuring no leftover files/registry entries skew your data.

Execute Installation & Monitor #

• Start monitoring first: Launch ProcMon, click the "Capture" button (the magnifying glass), and apply filters to narrow down noise—filter for processes named setup.exe, msiexec.exe, and any known dependency installers (like vc_redist.exe).
• Install one component at a time:
  1. Begin with your suspected prerequisites (e.g., .NET Framework, VC++ Redistributables).
  2. After launching each installer, wait fully for it to finish—check Task Manager to ensure all related processes are gone before moving on.
  3. Manually note the start/end time of each step, or rely on ProcMon’s timestamped logs to map the sequence later.
• Watch for hidden processes: Some setup.exe files are just wrappers that extract temporary MSIs or launch silent sub-installers—ProcMon will catch these, so don’t skip analyzing child process activity.

Analyze Logs & Map the Installation Sequence #

• Export and parse logs: In ProcMon, export the captured data to a CSV or XML file. You can use Excel to sort by timestamp, or write a quick PowerShell script to filter out irrelevant changes (like temporary file deletions).
• Document each component’s impact:
  • File system: List all new/modified files, their paths, and versions—this tells you what needs to be included in your package.
  • Registry: Note any new keys/values, especially those related to app registration, file associations, or dependency checks.
  • Dependency order: Cross-reference timestamps and error messages (if any) to confirm which components must be installed first. For example, if an MSI fails without .NET installed, that’s a clear prerequisite.
• Build a standardized sequence: Turn your findings into a step-by-step order, including silent install parameters where possible (e.g., vc_redist.x64.exe /quiet, ProductComponent.msi /qn).

Package the Product #

• Choose a packaging tool: WiX Toolset is free and powerful for MSI-based packages; Advanced Installer or InstallShield offer more GUI-based options for complex setups.
• Integrate components and dependencies: Configure your package to run each installer in the correct sequence, adding checks to verify prerequisites are present (e.g., check for .NET Framework version before installing the main app).
• Test rigorously: Roll back your VM to the clean snapshot, run your packaged installer, and compare the end state (files, registry, app functionality) to your manual install. Fix any gaps or order issues until they match perfectly.

Pro Tips #

• Always use silent install parameters when possible—this ensures consistency between your manual test and the final packaged installer.
• For self-extracting setup.exe files, use their built-in extract command (often /extract or /unpack) to get to the underlying MSIs/scripts—this makes packaging cleaner and avoids redundant extraction steps.
• If you hit a snag with a stubborn installer, check its command-line help (run setup.exe /?) for hidden parameters or logging options.

内容的提问来源于stack exchange，提问作者Eric Feurich