Hello to all, I've just finished the Teamviewer session with asmmag, and the issue was entirely different this time. Yes, even if the message "looks" the same, the problem was totally different.
Still related to Prepar3D, but in a different way. This time, I must admit it WAS a bug of the Addon Manager, there was a problem detecting the correct version of the program, which has been introduced when adding support for Prepar3D 2.0...
The issue is, the problem happened ONLY if the Addon Manager needed to display one of the FSX standard dialogs like the reactivation warning or the scenery outdated warning, if it had nothing to say, the problem would go unnoticed, this because the .DLL in FSX and Prepar3D 1.x that generated alert messages has *changed* its name in P3D 2.0, so the Addon Manager was trying to call an non existing library, because it incorrectly assumed it was running under the P3D 2.0 Beta...
The fixed files are online now, if you reinstall anything (a scenery, GSX, the Stand-Alone Addon Manager) you'll get them and will hopefully fix the problem for most of the remaining users that still had it, provided we don't find yet another reason for it...
I'm sorry, because this one was an oversight that was really my fault but, at least, you now know that all our products will be compatible with P3D 2.0 from DAY ONE, since we are already working on it.
