[SOLVED] Couatl64_msfs.exe is corrupted and unreadable

[karspilot]

Hi, after the last update my gsx doesn't work anymore.

Coautl64_Msfs.exe is corrupted and unreadable.

Nothing on my pc has changend (like virus scanners etc).

Even reinstalling won't help.

Please advise.

[karspilot]

I fixed it.

Unlink and uninstall from the FSDT installer.

Remove FSDT installer via software panel in Windows.

Then reinstall. (I used the offline version; don't know if this makes a difference)

[virtuali]

Hi, after the last update my gsx doesn't work anymore. Coautl64_Msfs.exe is corrupted and unreadable.

The file is corrupted because your antivirus has mistakenly flagged it as a threat, so it tried to "heal it" from a non-existing threat, making unreadable.

Configure the antivirus and be sure you add the whole "Addon Manager" folder to the antivirus EXCLUSIONS, then run the FSDT Installer and do an update CHECK on GSX Pro.

[EmileB]

Yesterday I loaded MSFS, GSX started automatically but showed advisary that it was out of date.
So I closed the sim and ran FSDT Live Update.
Restarted the PC.
Loaded MSFS : this time GSX did not start automatically.
Clicked GSX on the MSFS toolbar.
GSX then attempted to start but then advisory came up that the script engine had not started in the expected time, or words to that effect.
Ran Couatl64_MSFS.exe manually (and not as administrator, just double-clicked it) : error message came up stating file or directory is corrupted and unreadable.

I ran FSDT Live Update again this morning - just in case the file had been fixed - but same outcome.

Here are the first few lines of the Couatl log file :
16/09/2024 12:09:02: Couatl64_boot Log started
16/09/2024 12:09:02: Working folder set to C:\Program Files (x86)\Addon Manager\couatl64 according to FSDT registry root key
16/09/2024 12:09:02: Thread "couatl64_MSFS.exe"  added to monitoring
16/09/2024 12:09:02: Starting couatl64_MSFS.exe
16/09/2024 12:09:02: EXCEPTION The file or directory is corrupted and unreadable
16/09/2024 12:09:03: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:04: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:05: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:06: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:07: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:08: Waiting to connect to Couatl64 shared memory
16/09/2024 12:09:09: Waiting to connect to Couatl64 shared memory
etc

Before yesterday's FSDT live update, GSX had been loading automatically with MSFS and working without problems.
MSFS is up to date.  My PC runs Windows 11 Home.

I searched the forum in other threads about Couatl issues but to no avail.  Hence this post.  Any help appreciated !

Thanks a lot,
Emile.

[koosherselman]

I'm having exactly the same problem. Very frustrating.

[EmileB]

I just uninstalled and re-installed GSX.  Made no difference : problem still there  .  Hope Virtuali will get on to this soon.

[toddl]

Same problem for me.

[flyseven]

Exactly the same error happend to’ me

my antivirus is off on my msfs pc ??

[virtuali]

Nothing like this happens.

The only possible explanation, because we updated the .exe, a defective antivirus has corrupted trying to heal it from a non existent threat, which mistakenly detected because it assumed "it's new, it might be dangerous", because some buggy antivirus trust their flawed heuristics more than our proper Digital Signature, which is used precisely to help antivirus not catch false positives.

The usual:

- Configure the antivirus to add the whole "Addon Manager" folder to the antivirus EXCLUSIONS

- Run the FSDT Live Update again.

[airline54]

I been having the same issue. It was working fine Saturday. Sunday, I updated and know I can't get it to work either. I've turn off my antivirus and downloaded it and no luck. I uninstalled it and reinstalled, same thing. I been working on this for a few days now and can't get it work anymore. My icon lizard is gone. I don't know what to do. Help

[StrateJ]

So I was waiting for my account on here to be approved. I was wrapping my brain yesterday and this morning found a potential reason. I'm going through a reinstall again so will be forever before I come up with results but Malwarebytes is detecting the Couatl MSFS exe as malware and quarantining it.

[EmileB]

Nothing like this happens.

Sorry, but are you implying that me and the other posters here were only imagining that GSX wouldn't load ?

The only possible explanation, because we updated the .exe, a defective antivirus has corrupted trying to heal it from a non existent threat, which mistakenly detected because it assumed "it's new, it might be dangerous", because some buggy antivirus trust their flawed heuristics more than our proper Digital Signature, which is used precisely to help antivirus not catch false positives.

The usual:

- Configure the antivirus to add the whole "Addon Manager" folder to the antivirus EXCLUSIONS

- Run the FSDT Live Update again.

After doing "the usual" as above, GSX still wouldn't load.

Only after then uninstalling GSX with FSDT Installer and re-installing it with FSDT Installer, was GSX working again.

Your "only possible explanation" is a bit arrogant as well as unprofessional.  My "buggy", "defective" payware ESET Internet Security with its "flawed heuristics" found nothing wrong with GSX when I first installed it, issued no warnings, and GSX worked fine (I only used the pushback and jetways operation features sofar but am very happy with it  ).  The problem started with the GSX update to V3.1.5.

[kaanaslan]

Hello, same issue with others and I don't use an antivirus software.

Nothing like this happens.

The only possible explanation, because we updated the .exe, a defective antivirus has corrupted trying to heal it from a non existent threat, which mistakenly detected because it assumed "it's new, it might be dangerous", because some buggy antivirus trust their flawed heuristics more than our proper Digital Signature, which is used precisely to help antivirus not catch false positives.

The usual:

- Configure the antivirus to add the whole "Addon Manager" folder to the antivirus EXCLUSIONS

- Run the FSDT Live Update again.

[EndoYurika]

I guess you should check the router's setting instead. Turn off the router's firewall and problem solved.
The reason why the file was only 1kb is simply because the firewall blocked this exe file during the downloading stage, weird.

Nothing like this happens.

Sorry, but are you implying that me and the other posters here were only imagining that GSX wouldn't load ?

The only possible explanation, because we updated the .exe, a defective antivirus has corrupted trying to heal it from a non existent threat, which mistakenly detected because it assumed "it's new, it might be dangerous", because some buggy antivirus trust their flawed heuristics more than our proper Digital Signature, which is used precisely to help antivirus not catch false positives.

The usual:

- Configure the antivirus to add the whole "Addon Manager" folder to the antivirus EXCLUSIONS

- Run the FSDT Live Update again.

After doing "the usual" as above, GSX still wouldn't load.

Only after then uninstalling GSX with FSDT Installer and re-installing it with FSDT Installer, was GSX working again.

Your "only possible explanation" is a bit arrogant as well as unprofessional.  My "buggy", "defective" payware ESET Internet Security with its "flawed heuristics" found nothing wrong with GSX when I first installed it, issued no warnings, and GSX worked fine (I only used the pushback and jetways operation features sofar but am very happy with it  ).  The problem started with the GSX update to V3.1.5.

[majs]

Same problem here. never had any problems with GSX until this update. done as instructed but still not working