the reason why in my case Couatl is never starting with MSFS is the strange fact that none of the .exe files defined in the exe.xml file are executed when firing up MSFS. Neither Couatl, nor Fenix or Aerosofts VDGS.
Surely I know about that, because I am affected too, my exe.xml starts randomly, like 1 times out of 5. I reported it to Asobo, they are aware of it, and are looking for a fix.
It seems to be a buggy "licensing" problem and, in my case, I SUSPECT it happens because I have two separate copies of MSFS installed, one is the Microsoft Store version running SU10 Beta, the other is the Steam version running SU9, they are completely separate installations with separate licenses. However, since even on Steam you are required to log into MSFS with a Microsoft account, and that's clearly the same, I think this confuses the licensing system, because each time I switch from using one version to the other one, it thinks I'm logging from "another device", so it asks for confirmation. This is likely triggering some kind of bug, because the failed XML startup is in fact triggering a Windows error code that is related to a licensing problem. If I enable the Simconnect diagnostic log, it tells me I don't even have the *license* to run the Diagnostic log!
Asobo replied to me about this, saying the issue is likely the MSFS is trying for some reason to validate the license of child process started from the EXE.XML, which it obviously can't (MSFS can't possibly know anything about 3rd party licenses) so, the failure result in the .EXE not being started.
