Couatl engine hasn't started - How to report a problem

[virtuali]

Addon has both the coutal and couatal64 files in it but when I run the Updater the coutal icon does not appear

Please clarify what do you mean:

- It doesn't appear as a Desktop shortcut

OR

- It's not being launched by the sim

[Baldeagle53]

It does not appear as a Desktop shortcut. I have uninstalled and re-installed as run the checkin and no desktop shortcut

[Baldeagle53]

How do I get the coutal engine to appear as short cut icon on my desk top because it has not appeared despite uninstalling and reinstalling GSX

[Baldeagle53]

Could please favor me with a response about how to get the Coutal icon returned to my desk top so that I can start the Coutal engine because now GSX is not functioning

[virtuali]

The icon is created by the FSDT Universal Installer.

[Baldeagle53]

I have the Addon as an exception to my anti virus, I have uninstalled and reinstalled, I have run the check operation, I have deactivated and activated the product, I haveupdated  the latest version of GSX and still no coutal icon and thus GSX is totally inoperative

[virtuali]

still no coutal icon and thus GSX is totally inoperative

Your message is not very clear. I was referring to the "Start Couatl for GSX MSFS" icon, which is created on the Desktop by the FSDT Universal Installer (that's not the FSDT Installer). Were you referring to the icon on the Traybar notification area instead?

If you are missing the Couatl icon in the Traybar, it means:

- the Couatl engine hasn't started automatically by the sim, so you can use the "Start Couatl for GSX MSFS" Desktop icon to start it manually. Does it work this way?

OR

- the Couatl engine might have started, but it might have crashed. So, again, you can use the Desktop icon to start it.

[Baldeagle53]

I used the FSDT Universal Installer and the coutal icon is now on the desk top and the product is now functioning. Thanks fr your help

[Baldeagle53]

It functioned for 6 days and now the coutal engine icon is no longer on the desk top, not starting FSDT and showing the same error message:

                      C:\Program Files (x86)\Addon Manager\coutal64_MSFS,exe
                      The file or directory is corrupted and unreadable

Perhaps there is an issue with the coutal engine, Please advise
                                 

[virtuali]

Perhaps there is an issue with the coutal engine, Please advise

There's are no issues with it, of course. The only issue here is your antivirus that might have either corrupted it or altogether removed it because it mistakenly assumed it was a threat.

So, again, you must be sure you have added the entire Addon Manager folder to the antivirus Exclusion, then run the FSDT Updater again, which will restore the file that has been corrupted/removed.

[Baldeagle53]

I have done that and it is not functioing. What is shown on my Desktop is the empty coutal icon without the dragon in it

[virtuali]

What do you mean with "empty icon" ? Something that doesn't point to anything, like a file that was removed?

Again, you must be sure you have added the entire Addon Manager folder to the antivirus Exclusion, then run the FSDT Updater again, which will restore the file that has been corrupted/removed. Nothing else can cause a removal, we surely don't remove our files!

[Baldeagle53]

I have done what you suggested and it worked for a week and then was corrupted again. I do not understand how the entire Addon Manager folder is in the anti-virus exclusion, the updater and the universal installer are run and then coutal becomes corupted again

[Baldeagle53]

Mr. Colapicchioni, I would like to hear from you as I have followed all of your instructions but do not have the coutal icon on my desk top and thus cannot run the product. I have run the updater and have the latest version of the program installed so my virus protection does not appear to be the issue. I do not appear to be the only person with an issue.

[virtuali]

It's weird because it was working fine but after updating it started giving this error.

Since the error in your log is caused by your username contaning non-ascii characters, I can't see how this could possibly be related to the update, since it's happening in a part of the code that hasn't changed in a while. We need to fix this, of course, but it's not related to the update.