GSX Issue after last update

[Nap Qdr]

Hey guys,

I purchased GSX and the expansion level 2 a while back and it was working really good and properly, but after the last update, that I did today, the GSX menu is not showing up on my Addons Menu.
I only can see the Addon Manager menu and when I open it up, shows that my GSX is in trial mode. I tried to re activate it with my codes, but when I click on Register Serial Number, it pops up a message saying that my antivirus has blocked the addons and I have to add it as an exclusion. the funny thing is I dont even have an antivirus, I'm running on Windows 10 and the Windows Security doesnt even show it as an unsafe or threat. Anyway, I added the file as an exclusion on Windows Security and I re-install the addon, and still is not working. I can't see it on my menu so I can't pop up the ground services actions menu and I tried to click on register serial number again to reactivate it and it keeps on showing the same message.
Please help me

[virtuali]

I added the file as an exclusion on Windows Security and I re-install the addon, and still is not working

You must add the WHOLE Addon Manager folder, not just a file, to the Antivirus Exclusions. Do that, and run the FSDT Live Update again.

[Nap Qdr]

Im sorry, thats what I did, I added the whole folder, not the file but is still not working.
Thats what I meant

[Nap Qdr]

I added the file as an exclusion on Windows Security and I re-install the addon, and still is not working

You must add the WHOLE Addon Manager folder, not just a file, to the Antivirus Exclusions. Do that, and run the FSDT Live Update again.

How can I downgrade the app? It's not working...... and I use it to record my videos for my channel.
Please I need help

[hud11]

I have the exact same problem. I thought at first that it was because I moved to a new computer, but I remembered that I had already used GSX in the new computer. It might be therefore the problem with the update.

[Nap Qdr]

I have the exact same problem. I thought at first that it was because I moved to a new computer, but I remembered that I had already used GSX in the new computer. It might be therefore the problem with the update.

It has to be the update.. Im still running it without the GSX and the sad part of this is nobody is helping us out lol

[methax112]

I added the file as an exclusion on Windows Security and I re-install the addon, and still is not working

You must add the WHOLE Addon Manager folder, not just a file, to the Antivirus Exclusions. Do that, and run the FSDT Live Update again.

No working that "solution", please fix the problem.

[Guggibob]

Same problem here. After making an update "Coautl scripting engine isn't running anymore". I spent my half sunday, trying to solve this problem, but nothing of the suggestions lead to a solution.
And it's really ridiculous, that there is no chance to make a roll back to an earlier version of the software, which works without problems. Kind of fooling around the customer, who has already payed for the shit!

[ricsaraiva1]

Due to the lack of support from Virtuali, I did some research and came up with a TEMPORARY SOLUTION, THAT I HOPE VIRTUALI FIXES IT AS SOON AS POSSIBLE IN THEIR NEXT UPDATE. Here it goes: Go to your "Prepar3D Add-ons folder", then to "FsDreamTeam Addon Manager" and open "add-on.xml" with WordPad. On the last category ("EXE"), where you have <Path>F:\Addon Manager\couatl64\couatl64_P3D.exe</Path> ("F:" is the disk where my FSDT Addon manager is installed, yours may be different!!)
, edit this line to <Path>F:\Addon Manager\couatl\Couatl.exe</Path>. Apparently everything works fine after I did that...

[methax112]

Due to the lack of support from Virtuali, I did some research and came up with a TEMPORARY SOLUTION THAT I HOPE VIRTUALI FIXES IT AS SOON AS POSSIBLE IN THEIR NEXT UPDATE. Here it goes: Go to your "Prepar3D Add-ons folder", then to "FsDreamTeam Addon Manager" and open "add-on.xml" with WordPad. On the last category ("EXE"), where you have <Path>F:\Addon Manager\couatl64\couatl64_P3D.exe</Path> ("F:" is the disk where my FSDT Addon manager is installed, yours may be different!!)
, edit this line to <Path>F:\Addon Manager\couatl\Couatl.exe</Path>. Apparently everything works fine after I did that...

Did it, but doesnt works

[ricsaraiva1]

Try doing a full reinstall and then do what I wrote on the last post

[ricsaraiva1]

I uninstalled first and then I reinstalled it

[lidsrock]

Due to the lack of support from Virtuali, I did some research and came up with a TEMPORARY SOLUTION THAT I HOPE VIRTUALI FIXES IT AS SOON AS POSSIBLE IN THEIR NEXT UPDATE. Here it goes: Go to your "Prepar3D Add-ons folder", then to "FsDreamTeam Addon Manager" and open "add-on.xml" with WordPad. On the last category ("EXE"), where you have <Path>F:\Addon Manager\couatl64\couatl64_P3D.exe</Path> ("F:" is the disk where my FSDT Addon manager is installed, yours may be different!!)
, edit this line to <Path>F:\Addon Manager\couatl\Couatl.exe</Path>. Apparently everything works fine after I did that...

I was having a problem activating GSX and GSX Level 2.  Doing this worked for me!  Thank you!  I uninstalled GSX and reinstalled, ran the Live Update and then found the .exe file and edited the line.  I am now able to activate both products within the sim flawlessly.

[ricsaraiva1]

Glad it worked for you 

[Guggibob]

Due to the lack of support from Virtuali, I did some research and came up with a TEMPORARY SOLUTION, THAT I HOPE VIRTUALI FIXES IT AS SOON AS POSSIBLE IN THEIR NEXT UPDATE. Here it goes: Go to your "Prepar3D Add-ons folder", then to "FsDreamTeam Addon Manager" and open "add-on.xml" with WordPad. On the last category ("EXE"), where you have <Path>F:\Addon Manager\couatl64\couatl64_P3D.exe</Path> ("F:" is the disk where my FSDT Addon manager is installed, yours may be different!!)
, edit this line to <Path>F:\Addon Manager\couatl\Couatl.exe</Path>. Apparently everything works fine after I did that...

Due to the lack of support from Virtuali, I suggest you start a career at FSDT.  After reinstalling GSX and editing the addon.xml as you suggested, everything works fine now here on my PC. Thanks for your help and always good landings.