Why EMCO MSI Package Builder
Use a single tool for all application packaging tasks. Repackage and customize software applications to prepare them for non-interactive automated deployment.
Repackage Any Application
Do you need to repackage a small utility or a huge software package? EMCO MSI Package Builder is able to repackage all types of Windows applications, including complex installations deploying services and drivers. Repackaging example
Intuitive and Automated Process
No more guesses, no more mistakes. The program guides you through entire repackaging process. Follow the instructions of the wizard to select the source package and output format. Then install the source package and customize it, so the program can capture it and generate an output package for you. More about repackaging
Fast and Accurate Results
EMCO MSI Package Builder uses a kernel-mode driver to capture system changes on-fly when repackaging is activated. It produces accurate capturing results and allows generating an output package immediately when repackaging installation is finished. How repackaging works
Application Packaging Scenarios
EMCO MSI Package Builder allows you to use different packaging approaches and output formats to create packages according with your needs and ready for automatic deployment.
Repackage EXE to MSI
Do you need to deploy an application across entire organization? EMCO MSI Package Builder allows you to convert interactive EXE installation into a silent MSI package ready for automated deployment through any of software distribution tools.
Repackage EXE to MSI easily by following the EXE installer steps manually and let the repackager to capture changes and create an MSI package.
Capture Changes and Create an Installation
You can create a new custom installation easily. Use the monitoring feature of EMCO MSI Package Builder to capture system changes and then apply the required customizations in the system manually. The program captures all changes and generate an MSI/MSIX package reproducing these changes.
Customize an Existing Installation
Does your installation require post-deployment configuration? Repackage it by capturing system changes so that both installation and customization actions are included in the output package. Everything is handled automatically.
You can also configure the generated package to run custom actions before/after deployment, so it can run executables if you need.
Convert an Installation to MSIX
Want to use a new deployment format? EMCO MSI Package Builder supports creating MSIX packages. You can select MSIX as the output format in any packaging scenario — whether converting an existing EXE installation to MSIX, or automatically generating a new MSIX package using installation monitoring.
You can switch the output package format and generate an MSIX package for the projects generating MSIs.
Wrap Installations into MSI or IntuneWin
Repackage existing EXE installations by wrapping them into MSI or IntuneWin packages. The original installer remains unchanged and is executed during the deployment of the wrapper package. This approach works when the EXE installation supports silent mode, allowing the generated package to be installed without end-user interaction.
Installations wrapping helps to repackage all types of executable installations with no modifications of the original installation files.
Publish Packages to Intune
EMCO MSI Package Builder integrates with Microsoft Intune, allowing you to publish MSI, MSIX, and IntuneWin packages directly to Intune. Corresponding applications are created in Intune automatically during publishing. Deployment is performed in Intune by assigning the applications to users or devices.
The program also supports application updates. You can configure how existing installations are handled when a new package version is deployed.
How Application Repackaging Works
Follow a few steps of the repackaging wizard to convert an existing non-silent EXE installation into a silent installation package
Prepare Repackaging Environment
It is recommended to use a clean environment for repackaging, so create a new virtual machine specifically for this purpose. After installing Windows on the VM, create a snapshot of its clean state to use for repackaging. The repackaging environment only needs to be set up once and can then be reused for all future repackaging tasks.
Select an Installation to Repackage
You can repackage a non-silent EXE installation into a silent MSI or MSIX package. Select the installer you want to convert, and the process generates a silent package. You can also create an output package by monitoring changes made manually or by a script, then generate a package that reproduces those changes during deployment.
Specify Repackaging Options
Select the output package format (MSI/MSIX), specify the package version, upgrade options, and other properties. Repackaging can be performed on a local machine or a remote virtual machine, so choose the environment where repackaging should take place and let the program verify that it is properly configured.
Follow the Installation Steps
Installations are repackaged using Live Monitoring technology. The program automatically tracks file system and registry changes to generate an output package that reproduces those changes. Simply follow the original installation steps and select the required options. The resulting package will include both the installation and any customizations applied during monitoring.
Get an Output Package
The program automatically detects the end of monitored installation and generate an output package using the settings you specified, so at the end of repackaging you get an package file in the required format. If you need, you can review the captured data used to generate a package and apply the required changes to create an new customized package.
Test the Package and Deploy It
To ensure that the generated package works as required, you can test it before deployment. Testing can be performed safely on a virtual machine or in Windows Sandbox. For deployment, you can use external tools or take advantage of built-in Intune integration to publish the package directly to Intune. Once published, the application can be assigned to users or devices for deployment.
Repackaging to MSI and MSIX
The program allows repackaging applications into MSI and MSIX/AppX formats. The same repackaging process is used regardless of the selected output format. For existing projects you can create output packages in different formats if required.
Easy Repackaging
It's easy to repackage an installation using the automatic repackaging process. You start repackaging, so that all system changes are captured, and follow the installation steps manually. An output package is generated automatically when the monitored installation is finished.
Live Monitoring Technology
The program uses Windows kernel-mode driver to capture changes on the system level. It helps tracking all changes in real-time and generating an output package immediately at the end of monitoring.
Accurate Repackaging
The Live Monitoring technology allows to capture and repackage different types of installations, including complex installations deploying Windows services, drivers, assemblies, etc. The program has built-in and custom filters to guarantee accurate repackaging.
Application Customizations
If the repackaged installations require customizations, you can use a special repackaging option that allows capturing customizations and including them into the generated package.
Packages Ready for Automatic Deployment
The program generates silent output packages that can be deployed with no end-user interaction, so you can use the program to repackage non-silent installations into silent packages. The generated packages can be deployed using SCCM, GPO and other software distribution tools.
Integration with Hyper-V, VMware and VirtualBox
Application repackaging can be simplified using a VM for monitoring. The program integrates with VMware, Hyper-V and VirtualBox to allow repackaging on remote VMs. The program loads a VM snapshot, copy data and performs other steps automatically.
Wrapping to MSI and IntuneWin
If a repackaged installation supports silent deployment, you can wrap it into an MSI or IntuneWin package. In this case, the original installer is included in the package without any modifications. It is executed with predefined command-line parameters when the wrapper package is deployed.
Integration with Intune
The program provides integration with Microsoft Intune, allowing you to publish packages directly to Intune. Packages can be published to deploy new applications or to update existing ones already installed on target devices.
Application Updates Support
You can generate an update package for existing installations. When an upgrade package is installed the old version is uninstalled automatically and then the new version is deployed. To enable update features you need to configure update options in the package.
Pre/Post-Install Custom Actions
You can configure a package to run custom actions on package installation/uninstallation. It is possible to set pre/post install and uninstall actions. You can add custom scripts or executables and configure a package to run them as custom actions.
Package Editor
All captured changes are available in the installation project, so you can review the changes and modify, if required. The program provides specialized editors for registry, file system, driver, services and other captured changes. Using the editors you can add additional resources into the project, if required.
Package Signing
Generated packages can be digitally signed. By default the program uses auto-generated digital certificate, but if you have your own certificate, you can specify it in the program, so all generated packages will be signed using this certificate.
x86/x64 Packages Generation
The program allows generating packages for x86 and x64 platforms. Target platform is selected automatically depending on the platform used for installation repackaging, but you can switch the project to use a specific platform, if required.
Select the Program Edition
The program is available in multiple editions with the different set of the features.
Compare Editions
- Creation of MSI packages using repackaging or manual editing
- Packaging of basic installations deploying file system and registry changes only
- Installations monitoring on a local machine or in Windows Sandbox
- Packages testing on a local machine or in Windows Sandbox
- Creation of MSI and MSIX/AppX packages using repackaging or manual editing
- Packaging of basic and advanced installations deploying drivers, services, env. variables, etc.
- Installations monitoring on a local machine, in Windows Sandbox, and on connected VMs
- Packages testing on a local machine or in Windows Sandbox, and on connected VMs
- Wrapping installations into MSI packages
- Repackaging of Windows Store applications
- Creation of MSI and MSIX/AppX packages using repackaging or manual editing
- Packaging of basic and advanced installations deploying drivers, services, env. variables, etc.
- Installations monitoring on a local machine, in Windows Sandbox, and on connected VMs
- Packages testing on a local machine or in Windows Sandbox, and on connected VMs
- Wrapping installations into MSI packages
- Repackaging of Windows Store applications
- Creation of IntuneWin packages
- MSI, MSIX, and IntuneWin packages publishing to Microsoft Intune
What happens after my 30-days trial end?
The program can be evaluated free of charge during 30 days. After the end of the trial period you have to enter a license code and register the program to keep using it.
All MSI packages generated during the trial period have built-in 30 days expiration. These packages can be used for testing purposes only and cannot be deployed in production because they expire in 30 days.
How to create an update package?
To create a package that updates an existing package you need to specify correct package properties, such as the version number and upgrade identifier. An upgrade package have to include entire installation, so it's recommended to perform repackaging on a clean machine.
When this package is deployed the previous package is uninstalled first and then the package content is applied. An upgrade package creation procedure is explained in the article.
What is the difference between the program editions?
What are trial package limitations?
Packages created using the trial version of the program have a few limitations:
- The trial packages are valid during 30 days. After 30 days, they stop working and should be uninstalled.
- Packages generated using the trial version of the program show the trial mark (their installation name starts with the 'EMCO EVALUATION' prefix) in Windows Programs and Features after installation.
Is it possible to create a package with custom settings?
What type of support do you provide?
Ready to get started?
Install a free, full-featured 30-days trial version and see how it works in your network environment.