InstallerExplorer: A Step-by-Step Tutorial for Custom Installers

InstallerExplorer — Inspect, Edit, and Extract MSI Files Easily

InstallerExplorer is a tool for inspecting, editing, and extracting contents from Microsoft Installer (MSI) packages. It helps IT professionals, software packagers, and advanced users examine installer structure, troubleshoot installation issues, and customize or repurpose installer components.

Key features

• MSI inspection: View MSI tables (Property, Component, File, Feature, Registry, CustomAction, etc.) and relationships between them.
• File extraction: Extract embedded files and CAB contents without running the installer.
• Table editing: Modify table entries (e.g., change properties, feature names, component paths) and save changes back to the MSI.
• Custom action analysis: Inspect and edit custom actions and their sequencing to diagnose or adjust installer behavior.
• Search & filtering: Quickly find files, components, GUIDs, registry entries, or strings across MSI tables.
• Preview & validation: Validate table integrity and preview how changes affect installation flow before committing edits.
• Batch operations: Apply repetitive edits across multiple MSIs (rename properties, adjust paths, inject/remove files).
• Logging & undo: Maintain change logs and support undo/redo for safer editing.

Common uses

• Troubleshooting failed installations by tracing missing files, broken component GUIDs, or incorrect registry entries.
• Customizing installers to change default install paths, features, or bundled files.
• Extracting resources (binaries, icons, documentation) from legacy MSI packages.
• Preparing MSIs for enterprise deployment (repackaging, removing unwanted bundled apps).
• Security review of custom actions that may execute scripts or elevated processes.

Basic workflow

1. Open the MSI file in InstallerExplorer.
2. Inspect the Property, Feature, Component, and File tables for relevant entries.
3. Extract any embedded CAB or file resources you need.
4. Make targeted edits (update properties, change component paths, edit custom action parameters).
5. Validate changes, review logs, and save the modified MSI.
6. Test installation in an isolated environment.

Tips

• Always back up the original MSI before editing.
• Use validation and a test VM to confirm behavior after changes.
• Watch for component GUID collisions when merging or reusing components.
• For enterprise deployments, complement edits with transform (.mst) files rather than direct MSI edits where possible.

Limitations

• Complex installers that use chained packages or external bootstrapper EXEs may require additional tools.
• Editing some signed MSIs will break signatures; re-signing may be necessary.
• Not a replacement for full repackaging tools when significant rebuilds are required.

If you want, I can draft a short step-by-step tutorial to extract files from an MSI or a checklist for safely editing MSI tables.