[wix-users] .NET installer exit codes not being detected properly

[Brandon Welch]

I've been tasked with moving our main product from a ClickOnce installation process to Wix. I have our installer/bootstrapper nearly complete, but I've hit a slight snag. I'm seeing more or less the same problem that is described at this link: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-Burn-bootstrappers-and-reboots-td7582062.html<https://u911468.ct.sendgrid.net/wf/click?upn=XxDEhgF-2F1mV0aAtnOuZM-2FNZ3g0Gz3C64XN-2Fckxl7XLqQH4OeV-2BhPYXvVocOKhn7cz3o73DafvuhNtU79GHbviFjAEaZTCmb6g77vJx2BRznXAbEPu5IsVdv-2Fo44VS58G2JQUgs5MvRpQAKWxCvuMDfEKhxoOWzqPdJzu5JpM8dU-3D_hfIqhjxrH5PXl2rHT1sLDfQ-2BdQACrXzfCrB4ON04e-2B8gqY23RN-2FFG5-2FlP1hUDrZtwPHlk6BzS61d0riqEAbLrni2YkJB2JxYN-2Fogw-2BQK1LhflNtisL7xHYSUosjKv3APRtRfNOudYdPI11u-2BL4oDHkpVTl2AwQhs5uuQ8fICQ7Xl4im4poJaMXWD6wo-2FRDmU2ZrI-2FxkU-2BJ4eeq9RtvXXjw-3D-3D>

Our bootstrapper includes .NET 4.6.1, which sometimes requires a reboot to complete its installation. The .NET installer prompts you for a reboot when necessary, but the bootstrapper seems to ignore this request, even with appropriate forceReboot ExitCodes included in .NET's ExePackage in Bundle.wxs. This leaves Windows hanging as it attempts to close the bootstrapper process, which never ends up happening. In the Burn log, I can see that the bootstrapper is seeing an exit code of 0, which shouldn't be the case if a reboot is necessary.

I'm currently using Wix v4.0.4305.0 and Visual Studio 2015.

These are the ExitCode elements that are contained within the .NET ExePackage:

       <ExitCode Behavior="forceReboot" Value="1641" />
       <ExitCode Behavior="forceReboot" Value="3010" />
       <ExitCode Behavior="success" Value="0" />

Do you have any advice?