# What is the Best way to test a compressed MSI that is within a setup.exe

**URL:** https://www.finalbuilder.com/forums/t/what-is-the-best-way-to-test-a-compressed-msi-that-is-within-a-setup-exe/1194
**Category:** Discussion
**Created:** [May 4, 2009, 8:02am UTC](https://www.finalbuilder.com/forums/t/what-is-the-best-way-to-test-a-compressed-msi-that-is-within-a-setup-exe/1194 "2009-05-04T08:02:36Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![djmarks](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/d/b487fb/32.png) [@djmarks](https://www.finalbuilder.com/forums/u/djmarks)
#### Post date: [May 4, 2009, 8:02am UTC](https://www.finalbuilder.com/forums/t/what-is-the-best-way-to-test-a-compressed-msi-that-is-within-a-setup-exe/1194/1 "2009-05-04T08:02:36Z")

</div>

Most our installs have the MSI exposed for install, but we do have 1 click installs, as well as compressed within the setup.exe

In Finalbuilder&nbsp; 6 I am trying to establish a testing process for all cases mentioned above.

Most of the time I am finding using the&nbsp;Executable that is included with the MSI is a better solution, simply it is comon with all packages.&nbsp; It also has more functionality to detect on upgrades when executed.&nbsp;
