That sounds logical, except for the fact that I kept a copy of the xml when it was JUST Fenix, and was working, but today even that is not. I have to start it manually.
Maybe it’s a Friday thing, and will work right tomorrow, who knows.
The only thing I can think of is that all the programs communicate somehow with MSFS and many of them need access to the local network. From what I see, exe.xml is accessed very early in MSFS startup. If the timing is off like a very slow “checking for updates” MSFS might not be ready to communicate with the 3rd party apps in the exe.xml. The app may refuse to start if MSFS is not ready to connect. One app I use tells me to start MSFS even though it is already running and it never connects. Another app I use displays a message that the app is already running which doesn’t make sense.
For anyone who might be interested, here’s a copy of my exe.xml, updated a few minutes ago after I reinstalled GSX Pro, which was also not working automatically before I blew everything away and started from scratch. It also caused my sim to crash every time if I tried to use it with the Fenix, an obstacle I’m going to test either in a few minutes here, or if I fall asleep, in the morning.
<Launch.Addon>
<Name>FenixA320</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Name>BravoLights</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Users\kmoze\AppData\Local\Temp\Temp1_BetterBravoLights_JRpUI.zip\Program\BetterBravoLights.exe</Path>
<CommandLine>/startedbysimulator</CommandLine>
<NewConsole>False</NewConsole>
</Launch.Addon>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
</Launch.Addon>
</SimBase.Document>
After many hours of trial and error I’ve now completely moved to bat files. If you don’t use addons like aerosofts vdgs or vdgs by noolaero I can very much recommend doing this. Makes life so much easier. Just use start “” /b “program path”. If you want you can use timeout [seconds] (without brackets) between programs.
You can start MSFS with this command: powershell Start-Process -filepath explorer.exe shell:appsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App
I’d also recommend to start it in admin mode.
I don’t have any of this software so there is no way I can determine any problems with it except possible typos.
At this point, I’d recommend using a .bat file to start everything as other posters have suggested.
The other alternative is to contact the support or developer of the programs listed in the exe.xml file sending them the exe.xml file. Tell them their software isn’t working properly with MSFS AND the other add-ons. Ask them how to fix the problem.
I think it’s not their fault. The issue is that this bug is very much dependent on what you have in your community folder and which addons you have installed.
Have you been able to determine which add-on(s) in the Community folder is causing the problem? Flying without the Community folder is not a very good workaround.
Not really. I think it seems to be more about the number of addons instead of specific ones. Hard to tell tho.
I only have 4 plugins in that.xml and it doesn’t open for me. Disable the community folder and neither. The pity is that Asobo has not given any type of response in all this time (several months)
1 Like
If you are having the problem with 1,000 addons, test them in groups for a quick solution so you don’t have to do 1,000 tests.
Test 1 use 900 addons. If the problem still occurs,
Test 2 with 800 addons. If the problem disappears with 800 then the problem number of addons is between 900 and 800.
Test 3 with 850 addons. If the problem occurs, then the number is between. 850 and 800.
Test 4 with 825 addons.
Continue reducing the sample size until the number is determined. It shouldn’t take more than 9 or 10 tests to determine the number of addons causing the problem.
The topic is queued for review, but I would not expect an official response anytime soon.
By reading the posts above, I understand that if there is an issue with the exe.xml not loading, the following steps may fix it:
- Check exe.xml syntax
- Check correct file format (cr or lf?)
- Check if listed program paths are correct
- Remove/Limit community folder
- Check if disabling some exe.xml programs helps
Workaround: Only put programs in the exe.xml that are necessary. Create a folder with shortcuts to all other programs. Put a script in the folder that starts all programs via the shortcuts sequentially. (Same script could be used to e.g. start all updaters of mods sequentially).
Powershell script:
gci *.lnk | % { start $_ }
Read-Host -Prompt “Press any key to continue…”
Their response is that unless a CTD occurs there isn’t anything they can fix probably because they would have to acquire or purchase and install a lot of 3rd party software. Maybe what they might say is to only use exe.xml for one program. Or worse they could remove exe.xml completely and have users creat their own .bat files. (I would think developers and testers would have to keep their systems completely free of any 3rd party software.)
its working for me - starting every program - very fast and simple.
the only issue is had - one software i had in mode admin - this doesn’t start - till i changed it to normal.
1 Like
The title “oftine” is correct, sometimes also would be fine. This bug for me it’s happening eventually, but not every time. For example. Normally the first time I open the simulator after booting the computer, normally doesn’t work. After I restart MSFS 2020, the second time opens just fine. I’ve tried using the same format for file and in the XML as explained with “UTF-8” however it’s unpredictable, using the Microsoft Store version.
The only addons I have there is VDGS, Couatl (GSX) and Fenix A320
=)
This didnt work for me (firstobject xml), still same issue.
1 Like
After SU10 my EXE.XML now NEVER starts 
2 Likes
Did you just confuse content.xml with exe.xml? 
Absolutely not, eh eh
I have noticed that MSFS will start any file that has the same permissions as it does. Prior to SU10 I had all of my exe.xml files as Start as Admin along with MSFS to start as Admin and everything seemed to work. After SU10 Beta started I could not change MSFS to start as Admin (I think the actual exe is in the locked Aps Folder and we are only seeing a symbolic link) so it was not opening the others, I changed the other exe files to normal start and they all seem to be starting correctly again.
I am using the EXE.xml to start Axis and Ohs, Better Bravo Lights, and FSUIPC7.
YRMV