Warning message: probable EXE.xml corruption

[Sagittarius2018 4]

Hi, I bought FS2Crew for Maddog. When I open it I read the error message you see in the image.

How can I fix it?

Thank you.

 

[MaDDogz 242]

Taken from support 

Problem:

The FS2Crew Command Center does not auto start when MSFS loads.  I do not see the FS2Crew Command Center (red airplane nose icon) in the toolbar.

Solution:

1. This is a common problem associated with corrupted EXE.xml files.

On 30 April 2022, a new option was added to each MSFS FS2Crew that allows the Command Center to auto launch when Windows loads.  This option was created to bypass the need to depend on the EXE.xml file to auto launch the Command Center.

Steps to have the Command Center auto launch when Windows loads:

A) Ensure MSFS is running.

B) Launch the associated FS2Crew program either by its desktop icon or by its exe file located in PROGRAM FILES X86 – [FS2CREW PROGRAM NAME]

C) Go to the SETTINGS PANEL in your FS2Crew program.  

D) Check the Auto Launch on Windows start up option.  Note that you only need to this for at least one FS2Crew product, not all of them.

E) Restart Windows.

F) The Command Center should now auto start when Windows launches, and the EXE.xml is effectively no longer used to make the Command Center load!

2. Some anti-virus programs are over sensitive and aggressive and may blocking the FS2Crew installers from writing to the Community folder.  Check that you have have no security programs running that may block access.

3. Your EXE.xml may be corrupt.  The EXE.xml allows 3rd party programs to autostart.  The EXE.xml is a very sensitive file.  Any invalid characters on it will cause it to fail, resulting in the Command Center not auto-loading when MSFS starts.

Steps:

1. Locate your EXE.xml.  You may need to do a file search if you cannot find it.
2. Check the contents of your EXE.xml using Notepad.  Check if anything is obviously wrong.
3. Make a back up copy of your EXE.xml.
4. Delete your EXE xml.
5. Reinstall FS2Crew.  FS2Crew will regenerate a fresh copy of your EXE.xml.
6. Restart your computer.
8. Load MSFS and try again.
9. If the Command Center loads, you know the problem was a corruption on your EXE.xml.  (The Command Center should load when MSFS loads.  You should see a red airplane nose icon in your taskbar).
10. Re-add any other programs that were on your EXE.xml, but do so very carefully so you do not corrupt the EXE.xml

[byork 2,259]

It's all right here:

https://fs2crew.com/fs2crew-command-center-troubleshooting/


Your EXE.xml is corrupt.

Easiest solution is use the Load Command Center on the Windows start option.  This bypasses the DLL.xml entirely,