Wix 5 Bootstrapper Installer Reopens After Install/Uninstall Completes

[Bondarenko1990]

I use Wix 5 WixStandardBootstrapperApplication. In the Bundle I added my WPF application to the chain

<Chain>
    <MsiPackage Id="Setup" SourceFile="$(var.MyProject.Setup.TargetPath)"  Compressed="yes" />
</Chain>

and I added a custom action in which I install the ImDisk bat file.

string installCmd = $"/silent /lang:english /installfolder:\"C:\\Program Files\\ImDisk\" > install.log 2>&1";
var startInfo = new ProcessStartInfo(".....\\ImDisk\\install.bat", installCmd );

startInfo.UseShellExecute = false;
startInfo.CreateNoWindow = true;

var proc = new Process();

proc.StartInfo = startInfo;
proc.Start();
proc.BeginOutputReadLine();
proc.BeginErrorReadLine();
proc.WaitForExit();

And after the installation is complete, a new copy of the installer opens for some reason.

If I remove silent install ImDisk from CustomAction everything is fine.

Tell me what I'm doing wrong. Why does the installer reopen after the installation is complete? What's interesting is that there is no such problem in Wix 3 WixStandardBootstrapperApplication.

[bevanweiss]

There should generally only be a single 'installer' running at any one time.
So it would be recommended to use the Bundle to launch the ImDisk installation.

You haven't shown how you've authored the CustomAction in WiX, so it's possible that you are executing it multiple times.
But, best practise is to not try to run a subsequent installer from within an MSI

[Bondarenko1990]

@bevanweiss Thanks for the advice. I run the ImDisk installation only once in CustomAction! I checked more than once...
How can I run the installation of ImDisk in a bundle? I mean "install.bat" file.

[wmanning]

I run the ImDisk installation only once in CustomAction!
What does the ImDisk bat file do roughly? Does it run one or more EXE files or another MSI file?

You have this:

<Chain>
    <MsiPackage Id="Setup" SourceFile="$(var.MyProject.Setup.TargetPath)"  Compressed="yes" />
</Chain>

Ideally you'll take the stuff ImDisk does and put it in a MSI file as that would be much more reliable.
If that is too much work maybe you can wrap it in an EXE file and run it like this:

<Chain>
    <MsiPackage Id="Setup" SourceFile="$(var.MyProject.Setup.TargetPath)"  Compressed="yes" />
    <ExePackage SourceFile="some-path/ImDisk-Installer.exe" />
</Chain>

See: https://wixtoolset.org/docs/schema/wxs/exepackagepayload/