[wix-users] Weird chained EXE behaviour

Hoover, Jacob Jacob.Hoover at greenheck.com
Wed Sep 6 08:54:41 PDT 2017

"Bombs out" isn't very descriptive.  I'd suggest looking at the logs of the exe installer (or enable verbose logging if the exe supports it) and then look at the actual log to root cause the problem.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Alex Tuppen via wix-users
Sent: Wednesday, September 6, 2017 10:47 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Alex Tuppen <alex.tuppen at gmail.com>
Subject: [wix-users] Weird chained EXE behaviour


I am having some trouble with an EXE in a chain, I have a custom bootstrapper which installs different things from the chain based on user input. Specifically it installs Microsoft Operations Manager Agent or Microsoft Operations Manager Gateway, then runs some MSIs to configure them and then an EXE to install the certificate and finish configuration. The EXE is behaving strangely though, if I run it after installing the agent it works fine, if I run it after installing the gateway however it bombs out.
I am using exactly the same chain entry for both instances and nothing is changing and the EXE behaves correctly outside the bundle.

Does anyone know of anything in a WiX bundle, with a custom bootstrapper, which would cause an exe to behave like this?

Kind regards,


WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-users mailing list