The exe.xml is just a list of programs that are started by MSFS. If an application isn’t started or started correctly in the exe.xml, then the application developer should be contacted for a solution. If it isn’t working for you, it shouldn’t be working for the application developer either.
well, it isn’t working for:
- Fenix A320
- GSX PRO
- Aerosoft VDGS
so it isn’t working for any .exe I have in that .xml
And its like this for several months now.
Since SU6 (?) the sim isn’t even regenerating the exe.xml file if you delete it.
For me a sign it is not really supported any longer.
I might be wrong, but only an official statement from the DEVs would convince me. Unfortunately I get no response. Neither here nor via Zendesk…
For now I got my workaround and except for VDGS everything is now working for me with the Batch file I wrote…
1 Like
I second this issue, my exe.xml, although present and correct, does not start those three addons anymore. No idea what could be the issue here…
1 Like
Hi, I’ve got a firend with exactly the same addons as mine and it wotks perfectly for him, Exe.xml will launch everything FSUIPC, GSX, FENIX bootstrap etc…, so I think the problem is something else maybe in our registry…
Why we are not getting any input from the developers, at least they can say we are working on it.
The 3rd party software developers aren’t providing any input for their software? What is their response about your problem? Are they working on it? Are they using exe.xml when running MSFS? If yes, then they should provide information about their exe.xml. If no, then maybe their app isn’t designed to work with exe.xml.
Realistically there is no way that MSFS could test and verify EVERY 3rd party app works with exe.xml.
I have been using exe.xml to start two software apps (not any of the apps documented above) for months without issues.
I have the same problem as others here with the EXE.XML file, but I have found a pattern that always works: the first time I load MSFS it NEVER works, but if I quit and restart MSFS it ALWAYS work, loading everything in it (Fenix, FSUIPC, FSRealistic, Coautl and FS2Crew). Would be great to have a definitive answer on this matter. On the GSX forums there are many users saying that Coautl doesn’t start and it’s due to the EXE.XML not starting withouth them knowing, so they blame GSX. That’s just an example, the same could happen for every single addon based on it.
For me, I found out it works when I have only a small number of Addons in the community folder.
Not sure what is the exact number (or file size?), though…
If I had to speculate, I’d say during the initialization when exe.xml would be initialised the Sim must be done by reading the files in community folder or else there is a conflict and exe.xml is not getting initialized properly.
But as said, this is pure speculation and it would really be nice to here from the developers on this issue.
3 Likes
My exe.xml used to work everytime until I changed to a new PC. Has never worked since - until I edited the exe.xml in Notepad++ and changed the encoding to UTF-8-BOM.
It’s worked 100% of the time since. Whenever anything gets appended to the exe.xml it stops working again until I change the encoding in Notepad++.
Of course it may not work for everyone and could be pure coincidence but it’s certainly seems to be working for me. HTH.
{edit to add} The only thing the exe.xml refuses to start is the aerosoft VDGS regardless of the change in encoding - thats probably some sort of licence call issue I suspect. It does start when launched directly but as I only had 1 airport that used it and now use GSX it’s become a non-issue for me.
3 Likes
That is an interesting find, I will certainly try to check that via Notepad++ the next time, thanks.
For the Aerosoft VDGS: this is going to be uninstalled now I have GSX. No need for two VDGS addons…
1 Like
I’ve found that to be the case as well. I use MSFS Addons Linker, and have found that if I use my “clean slate” preset (which disables most addons) that the exe.xml file runs consistently - FSUIPC, FSRealistic and Couatl all start automatically like they should. If I re-enable all my addons, then sometimes the exe.xml file will work and sometimes not. I spent a lot of time playing around, disabling addons I thought might be causing the issue, but it has never been consistent. I’m wondering if it’s like you said - too many addons may be causing the issue - perhaps a memory issue? Speculation on my part of course…
I am suspecting that as well. I had thought it was my AI aircraft as when I removed AIG or another set, the exe.xml worked flawlessly. Got rid of the other set and solely used AIG with no issue. However, I then went and updated AIG and added more liveries that were new and now all of a sudden, I am back with this issue. I think the new liveries pushed the addons past this “limit” that causes the xml file not to load the 3rd party addons.
Not sure if this is the actual issue, but it sounds like it could be.
Did some more testing and this indeed seems to be some limit we are hitting. When i remove a few addons, no matter which ones they are, the EXE.xml starts to run again consistently. Once i add them back and cross this limit, it fails.
At least we seem to figure out the cause and make it reproducable.
So lets DEVs are reading here and can come up with a solution.
Thank you all for confirming it really seems to be the number of community content causing it.
1 Like
Any chance this one might be in some way connected to the “memory could not be read” CTD?
This can be a cause, but it should be consistent all across the board if that is the MAIN cause = EXE.XML should never start if you have too manu addons. In my case sometimes it starts and sometimes not and I never touch it (I have many AIG liveries too). My EXE.XML is programmed to start 5 different addons at the moment
Removed all add ons and still didn’t start. Crazy this bug
1 Like
Yes it is. I stopped trying to troubleshoot. I’m lucky enough that if the first time It doesn’t run, the second it will for sure. I just have to start MSFS max two times or start everyhting manually. Hope a definitive solution will come around with the next updates.
1 Like
Hello they don’t read every post, you need to open a Zendesk Ticket 
1 Like
Hello I have changed to UTF-8 BOM, didn’t change anything for me, juste to let you know. Exe.xml still doesn’t launch anything