Shrink and Optimize InstallShield Installers Using InstallAware Setup Squeezer
Reducing installer size and improving runtime performance are common goals for software distributors. InstallAware Setup Squeezer for InstallShield helps compress and optimize InstallShield-built installers without altering application logic. This article explains what Setup Squeezer does, when to use it, step-by-step usage, optimization tips, and verification checks to ensure your installers remain reliable.
What Setup Squeezer Does
- Recompresses payloads inside an InstallShield MSI or setup.exe using more efficient compression.
- Removes redundant data and aligns files for better extraction performance.
- Preserves installer logic: custom actions, transforms, and sequences remain intact.
- Reduces download size and potentially lowers disk I/O during installation.
When to Use It
- Shipping large MSI or setup.exe packages where bandwidth is a concern.
- Distributing over slow networks or integrating installers into constrained storage devices.
- Preparing installers for download portals with size limits or for customers with limited connections.
- After finalizing installer contents and behavior (run Setup Squeezer as a last build step).
Prerequisites and Precautions
- Work on a final, tested build—do not compress a package still undergoing functional changes.
- Keep an uncompressed archive of the original installer for debugging and rollback.
- Test compressed installers across all target OS versions and configurations.
- Ensure licensing and signing processes still validate after recompression (re-sign if necessary).
Step-by-Step: Using InstallAware Setup Squeezer
- Prepare the installer
- Build your InstallShield installer (MSI or setup.exe) and verify installer functionality on a clean test machine.
- Create a backup
- Save a copy of the original installer and related build artifacts.
- Launch Setup Squeezer
- Open InstallAware Setup Squeezer and choose the input installer file.
- Choose compression settings
- Select the compression algorithm and level. Higher compression yields smaller files but longer processing times.
- If available, enable options to optimize file alignment and remove redundant metadata.
- Configure exclusions
- Exclude files that must remain untouched (e.g., cryptographically signed files, license containers) if recommended.
- Run the squeezer
- Start the compression process. Monitor for warnings or errors.
- Re-sign the installer
- If code signing is required, re-sign the compressed installer using your signing certificate to maintain trust.
- Test the compressed installer
- Perform functional, upgrade, repair, and uninstall tests on target operating systems.
- Validate custom actions, registry changes, shortcuts, and file permissions.
- Measure results
- Compare installer size, extraction time, and installation duration against the original.
- Deploy
- If tests pass, replace the original installer in distribution channels with the compressed version.
Optimization Tips
- Balance compression vs. CPU time: For large-scale distribution, prioritize smaller downloads; for rapid builds, use moderate compression.
- Segment large payloads: If supported, split nonessential payloads to be downloaded on demand rather than bundled.
- Avoid compressing already-compressed files: Multimedia and archive formats (e.g., .zip, .png, .mp3) gain little from further compression and waste CPU.
- Automate in CI/CD: Add Setup Squeezer as a final pipeline step, then re-sign and publish artifacts automatically.
- Use test automation: Incorporate silent-install tests to verify behavior without manual steps.
Verification Checklist
- Installer launches and finishes successfully.
- Application files installed and differ only in expected ways from original.
- Uninstall removes files and registry entries cleanly.
- Digital signature verifiable (re-sign if signature broken).
- No performance regressions during install or at first-run.
Troubleshooting Common Issues
- Installer fails to launch: Check that compression didn’t corrupt the bootstrap; try a different compression level.
- Signature invalid: Re-sign the installer after compression.
- Custom actions error: Ensure any embedded scripts or binaries were not altered; exclude them if necessary.
- Antivirus flags the installer: Submit samples to AV vendors; consider adjusting compression or signing methods.
Conclusion
InstallAware Setup Squeezer provides a practical way to shrink InstallShield installers while preserving functionality. Use it as a final optimization step, re-sign compressed artifacts, and run comprehensive tests across target environments to ensure a safe, efficient distribution.