How can I prevent two custom bootstrappers from opening?

[michaelgburton]

I have a custom bootstrapper application that installs a 3-part bundle. I have added a repair/remove screen to the installer, so when I use the modify/uninstall action from Add/Remove programs, I get my BA in the desired state.

When I open the original bundle EXE, however, I initially get my BA in the desired state, but as soon as it begins the apply phase, a second copy of the BA opens, and it appears to be in an invalid state.

The log for the second copy begins with this line:

[0C54:1234][2024-09-10T15:18:50]i003: This bundle is being run by a related bundle as type 'Upgrade'.

Is there a way to prevent this? Am I going about this all wrong? The example BAs I've seen get around this somehow, but I'm not sure how they do so.