Advanced Installer Repackager allows you to create projects based on capturing existing installations. For example you can repackage a legacy EXE setup into an industry standard MSI package. For detailed examples on how to repackage an existing installation package, please see the Repackager Tutorial.
The import operations allow you to create standard Windows Installer-based MSI packages by capturing and reproducing the behaviour of the original installers or installer projects.
Please note that the import features in Advanced Installer (Repackager, MSI import, etc.) are intended for obtaining a starting point for your installation package. This package must still be tested and the eventual incorrect or missing parts must be fixed.
The Repackager tool captures only the effects of the installation: the changes made on the system. If the original installation package executes custom code (programs, scripts etc.) then only the effect will be captured (registry entries, files and folders etc.).
After repackaging an installation some adjustments may be necessary in order to obtain a working installation package.
On 64-bit operating systems, the Repackager tool automatically runs its x64 version, in order to accurately capture 64-bit installations. If you wish to override this default behavior and force the use of the 32-bit Repackager on 64-bit systems, you can use the /ForceX86 command line switch (Repackager.exe).
- Repackage vs. Import
Repackage or import MSI packages?
- Repackaging using VMs
Repackage installations using virtual machines directly from your host OS.
- Repackage - local vs VM
Application Repackaging - Local vs VM
- Repackaging using Docker
Repackage installations using Docker containers.
- Repackager CLI
The repackager command line interface.
- UI Automation
Installer UI Automation
- Apply template over a captured installation
How to apply a template over a captured installation.
- Repackager Session
Repackager session commands