What's the status of the MSI "converter" / "compiler" aka SBMSI?

Is SBMSI and the exe2msi function a current solution? The threads on this subject are pretty old, so I dont know if that's because the feature is stable, not in demand, dead, or something else:)

I have high security (Federal, military and similar) folks asking for a MSI because their security software will accept a MSI without much contention, but will reject a EXE by default.

Mark


(detail from the user)

"I know this would not be a trivial update, but if possible, could you provide us an MSI file to install your app? EXE files are often blocked by our host intrusion prevention software. MSI files never seem to have an issue with being blocked by HIPS. I can submit a request for a HIPS exception to install the program. But it can take a couple of months for exceptions to go through and I need to submit a new exception for every version of your app that we want to use. Also, sometimes new security policies will break the install process which will again require me to submit another HIPS exception request."

Hi Mark,

what "exe2msi" does is, it embeds the high-performance SetupBuilder executable into a .msi package. On the target machine, the .msi exctracts the .exe and launches it.

Side note: we plan to make an option available in Q2 2020 to create native .msi files. Of course, most of the cool and flexible SetupBuilder functions are not available in .msi because the Microsoft technology simply does not support it. But you can then create native .msi.

Friedrich

Thanks Friedrich.

Mark

I'd be interested in beta testing this prior to its release to the general public. I'm waiting on a new computer and a new screen recorder software to be able to continue to make my SetupBuilder tutorials and boy would this be something to cover on that video series.