Few days ago FS20 started well as usual, but I was hearing my CPU fans whining all the time, so I opened the task manager to verify what's wrong and I saw for the first time that the Fenixbootstrapper starts everytime the sim starts and occasionally it's pegging the CPU at 55/65%. I was shocked, so I decided to shut down the app and fortunately the sim continued to work flawlessly.

After a Google and a Fenix Discord research I decided to open a ticket to the Fenix support asking for help, and 2 days later I got this answer:

Quote

Hi, Fenixbootstrapper won't use any CPU until you load into the Fenix.

My eyebrows became evil and for the sake of God I avoided any reply, but my shock was doubled after this a not so very smart support.

So guys, is there any way to avoid this Fenixbootstrapper thing is started everytime I start the sim?

To the Fenix guys and in general the paid devs: I received an excellent support from the so called "free addons" teams like Working Title and FlyByWire, this means that the new Asobo MSFS20 is a dynamic reality that requires much more dedicated work to fix the bugs and to add new features both the paid and the free addons. I tend to be more indulgent with PMDG, although their DC-6 can't fly properly since 6 months, because their ticket support works well and it's very efficient (but please, take care of our beloved DC-6!). 

 

Sorry but what other reply would you like. They are literally telling you how it is end it via task manager you just have to manually launch when wanting to use the Fenix. 
 

The bootstrapper is 3-4 lines of code that helps MSFS connect with the Fenix.

Edited January 9, 20233 yr by carlanthony24

Sorry, your reply didn't help me either to avoid the damned Fenixboot trap to start when FS20 starts, possibly without uninstalling the entire Fenix A320. I know perfectly what is this Fenixboot word not allowed software.

Edited January 9, 20233 yr by Claudius_

I start MSFS, and do not see the Fenix program launch, unless I am flying the Fenix. 

Thanks Bob, in my MSFS version (no beta), that things starts everytime the sim starts, indipendently from the Fenix A320. The Fenixbootstrapper is a background service, check your task manager, it's linked to the MSFS execution.

Edited January 9, 20233 yr by Claudius_

If you really want to stop it from running with the sim (which I don't recommend), just remove the following lines from exe.xml in your LocalCache folder (or change the Disabled parameter to True):

    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>C:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>

As mentioned before, FenixBootstrapper is just light weight code that keeps you from having to manually start the external Fenix app whenever you want to use the A320... it shouldn't have any impact on performance whatsoever.  If it's causing your CPU to churn, the most likely culprit is "over-zealous" anti-virus software.

Edited January 9, 20233 yr by MadDog

8 minutes ago, MadDog said:

If it's causing your CPU to churn, the most likely culprit is "over-zealous" anti-virus software.

I'm using the Windows 11 default security routine, no over zealous antivirus software, that FBS is pegging my CPU at over the 60% randomly, as I told in my aperture message. Also, I don't want other background not wanted and not used services.

Edited January 9, 20233 yr by Claudius_

17 minutes ago, Claudius_ said:

I'm using the Windows 11 default security routine, no over zealous antivirus software, that FBS is pegging my CPU at over the 60% randomly, as I told in my aperture message. Also, I don't want other background not wanted and not used services.

As others said, it's a simple edit-remove of the exe.xml and it won't auto start with MSFS. Then you have to start the FenixApp manually when you fly the Fenix. The answer from the Fenix support could have told you that, I agree.
Actually I've had a similar problem with the bootstrapper: When I quit MSFS the bootstrapper would suddenly use 99% of my CPU and MSFS wouldn't close. This happened even when I didn't use the Fenix at all. Somehow it stopped a week ago, no idea why.
However please keep in mind that this auto start is a smart idea for most users; just imagine the amount of support requests if everyone had to manually start the Fenix app. So it's neither an unusual nor a bad way to do this, actually it's the only way to use external apps in MSFS, the Maddog now also does this since the latest update (mdclient.exe is being auto started).

3 hours ago, Fiorentoni said:

As others said, it's a simple edit-remove of the exe.xml and it won't auto start with MSFS. Then you have to start the FenixApp manually when you fly the Fenix. The answer from the Fenix support could have told you that, I agree.
Actually I've had a similar problem with the bootstrapper: When I quit MSFS the bootstrapper would suddenly use 99% of my CPU and MSFS wouldn't close. This happened even when I didn't use the Fenix at all. Somehow it stopped a week ago, no idea why.
However please keep in mind that this auto start is a smart idea for most users; just imagine the amount of support requests if everyone had to manually start the Fenix app. So it's neither an unusual nor a bad way to do this, actually it's the only way to use external apps in MSFS, the Maddog now also does this since the latest update (mdclient.exe is being auto started).

Thanks, I have been having an issue with MSFS (Steam) not closing when I exit the game. I will try this. sorry, but are you saying delete the actual exe.xml file in the MSFS folder and have it rebuild without Fenix loaded?... or just remove the "fenixbootstrap" portion in the exe.xml file?

Regards

 

Edited January 9, 20233 yr by TomCYYZ

3 hours ago, MadDog said:

If you really want to stop it from running with the sim (which I don't recommend), just remove the following lines from exe.xml in your LocalCache folder (or change the Disabled parameter to True):

    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>C:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>

As mentioned before, FenixBootstrapper is just light weight code that keeps you from having to manually start the external Fenix app whenever you want to use the A320... it shouldn't have any impact on performance whatsoever.  If it's causing your CPU to churn, the most likely culprit is "over-zealous" anti-virus software.

Sorry for the false alarm, Thanks MadDog as well, this answers my Question, don't know how I missed it.

Regards

3 hours ago, Claudius_ said:

I'm using the Windows 11 default security routine, no over zealous antivirus software, that FBS is pegging my CPU at over the 60% randomly, as I told in my aperture message. Also, I don't want other background not wanted and not used services.

You might consider having Win11 antivirus exclude Fenixbootstrapper.exe or its entire folder.

I am not saying that is the reason for the cpu hammer, but there is a chance it is.  Anyway, I thought most of us already excluded the sim folder as good practice, so the Fenix may be similar.

32 minutes ago, TomCYYZ said:

Thanks, I have been having an issue with MSFS (Steam) not closing when I exit the game. I will try this. sorry, but are you saying delete the actual exe.xml file in the MSFS folder and have it rebuild without Fenix loaded?... or just remove the "fenixbootstrap" portion in the exe.xml file?

Regards

 

If you have the Leonardo MD80 installed it’s their MDClient causing steam not to recognize the sim is closed.  The MDClient starts automatically with the sim (regardless of whether or not you actually use the MD80), and doesn’t close when you exit the sim.

39 minutes ago, TomCYYZ said:

Thanks, I have been having an issue with MSFS (Steam) not closing when I exit the game. I will try this. sorry, but are you saying delete the actual exe.xml file in the MSFS folder and have it rebuild without Fenix loaded?... or just remove the "fenixbootstrap" portion in the exe.xml file?

Regards

 

Well I did neither of it, when I had the problem I just manually ended the bootstrapper in the task manager.
Anyway no don't delete the exe.xml, it will NOT rebuild! Just delete the part with the bootstrapper like someone posted here above.

That's interesting, I noticed this Fenixbootstrapper file for the first time on the weekend while I was playing with Process Lasso. 

All this tinkering under the hood is precisely what I told myself not to do this time when getting back into MSFS last year. But alas, here I am.

14 hours ago, flyhalf said:

That's interesting, I noticed this Fenixbootstrapper file for the first time on the weekend while I was playing with Process Lasso. 

All this tinkering under the hood is precisely what I told myself not to do this time when getting back into MSFS last year. But alas, here I am.

the FBS is coded in that way, it runs when the sim starts, independently if you are using the A320 or not, but it's bugged and we know that it pegs the CPU randomly. I love the Fenix A320 and I love flying it manually with "fingertips", but I don't love so much how it was organized by the devs.