FSDreamTeam in Trial Mode

[KJConlon 17]

Is anyone else having issues with FSDT products?  For me all of the add-on's I have purchased reverted to TRIAL mode.  I'm thinking this has to do with the move away from their e-commerce vendor. 

Any solutions?

 

Kevin

 

[pgde 571]

No problem here. Why don't you post on the FSDT site?

[Simicro 247]

12 minutes ago, pgde said:

Why don't you post on the FSDT site?

Maybe he did.

And it can be convenient to post on AVSIM to have other (independant?) points of view or reach quickly a wider audience. Not everybody visit every developer's forum everyday?

[KJConlon 17]

55 minutes ago, pgde said:

No problem here. Why don't you post on the FSDT site?

There was another reported issue that I added to, so of  course I posed in their forum - about an hour or 2 before here. 

That being said,  these forums tend to have a higher visibility and broader reach, meaning the ‘ask’ was to see if this is a localized issue or one that may be more wide spread. 

 

[Speedbird21 17]

Yep, same issue here with KIAH. Was registered the other day and now it's in trial mode 🤔

[TurboKen 221]

I had this happen a while back too... I think I removed it and reinstalled it and that fixed the problem by adding the correct registry entry. 

[KJConlon 17]

1 hour ago, Speedbird21 said:

Yep, same issue here with KIAH. Was registered the other day and now it's in trial mode 🤔

I found another thread on the FSDT forum .... I had to reboot then re-run FSDT Live Update 2 more times and it seems to have fixed the problem.  I wonder if there was a bad update somewhere recently.

 

Kevin

 

[Speedbird21 17]

19 minutes ago, KJConlon said:

I found another thread on the FSDT forum .... I had to reboot then re-run FSDT Live Update 2 more times and it seems to have fixed the problem.  I wonder if there was a bad update somewhere recently.

 

Kevin

 

Thanks, I will give that a try and see if it fixes it.

[krono 13]

Hi

I had the same problem. After reading through forums it was touted as an antivirus problem. I had to turn off Windows Defender and the reinstall and register again and all was fine.

Ken

[virtuali 4,419]

Exactly, the problem doesn't have anything to do with our update, or the fact we switched to another activation system, because Esellerate is still there, and the Esellerate servers will still run until September 30th so, until then, our software will first try to connect there, and only if it fails, it will try to connect to the new system ( Soraco ).

Of course, if you already have a new kind of Serial Number, one that starts with "A" instead of "FSDT", it will go directly to the new server so, under normal conditions, everything will work seamlessly, regardless if you have a new or an old serial, because both activation servers are supported and both are up. And even after Esellerate will close its servers, your old Esellerate serial numbers are already recognized on the new server, with no actions required on your part, it will just work.

If all products seemed to have reverted to Trial, what really happened, is the antivirus has mistakenly blocked the updated Couatl.exe program from running so, without it, the Addon Manager will report them in Trial.

This usually happens after an update, because some antivirus by default don't trust a new executable JUST because "it's new", and this in spite of us always following ALL suggestions from both Microsoft and antivirus vendors to digitally sign all the executables, both with an authenticode signature and with a Taggant signature, which is specifically designed to prevent false positives.

That's why we always suggest to configure the antivirus to exclude the whole Addon Manager folder from scanning, and this will also result in faster startup times, since the antivirus won't have to lose any time scanning for non-existent threats in that place.

It's also highly suggested to add the whole simulator folder to the antivirus Exclusion list, which can have a dramatic effect on loading times.

[ClaudeF 8]

I too had this problem after running the FSDT Live Update of the GSX PBR Update. I decided to run the "Full GSX Installer" based on a  comment from Virtuali in his forum post announcing the new PBR update..."In general, we noticed that, due to the large number of updated files and new files to be downloaded, it might be best to use the FULL Installer method". That solved the issue.

 

Edited July 13, 2019 by ClaudeF

[Ray Proudfoot 8,927]

@KJConlon, yes, same problem for me at JFK but I checked my product was registered in Addon Manager and it confirmed it was. Umberto has replied so I shall follow his advice on preventing it.

[Speedbird21 17]

I rebooted, ran the updater and all is well, Houston is mine again.