No problem. This must be the one you need.
GOT IT...
That's the scenery.cfg corruption in action. I've fixed it, now I bet the Addon Manager will run. As you can see, the file is now much shorter, look below for an explanation.
To everybody having the same problem:
There must be some 3rd party addon around that is corrupting the scenery.cfg. The affected lines are (how hironical) the scenery Titles for Cloud9 products. It's not a problem of Cloud9 products or our products, somehow, this installer is not able to properly deal with .INI files with characters outside the standard ASCII range. Because Cloud9 used the standard (c) Copyright symbol in the title, an installer should be aware of the correct encoding, not blindly parse it as if it were an ASCII text.
What happens is that, the (c) symbol for Cloud9 sceneries in the scenery.cfg, gets replaced by this faulty installer, with a *very* long (more than a thousand chars) string of random text.
Since our Addon Manager *also* parses the scenery.cfg at start, but does it in the "correct" way, with the official Windows API call to read INI sections, that long random string of texture that used to be the (c) symbol for Cloud9 areas, creates a BUFFER OVERFLOW, not in our code, but into the Windows API call itself, making the Addon Manager, and the whole FSX crashing with it.
There's no way we can fix it in the Addon Manager, because it's the Windows API call that gets confused, but we might be able to fix it in our installer.
For the time being, until we fix it in the installer, if you run into this issue, try to edit your scenery.cfg file, look for Cloud9, and change the area title to anything you like, removing the 1400+ characters long string that was created by an unknown installer of something else (it's surely a scenery).
If you are not comfortable with editing the scenery.cfg, just post it here, I've modified the forum config to accept .cfg files without renaming.
[attachment deleted by admin]
