thx for your reply. this registry line did let me install addonmanager and couatl again:
Ok, at least we know the problem was a Windows setting.
in departure mode all of your airports are visible. in approach mode i only see jetways, although they are all licenced except PHNL demo.
Try to approach the airport, and check if you have this file:
%APPDATA%\virtuali\Couatl.err
If you have it, post its content.
Maybe you didn't understood me exactly, the meanings was that i installed VC++ 64bit for an other reason, but i monitored that exactly this install caused the reactivating process of your 6 airports. Maybe it shouldn't but it did! Directly after install of this 64bit redist-pack i opened FSX and there was a dialogue to reactivate all your airports.
I understood you just fine, it's just that this shouldn't simply happen. Unless, there's bug in the VC++ 64 bit installer, that in some way changes the Windows configuration so badly, that is detected as an hardware change. Probaly a minor one, that hasn't consumed any activation, but it shouldn't happen, and you are the first one reporting it.
I only reinstalled the PMDG-747X on this day which renews the 32bit VC++ for the 747-8 update, but after install of this addon there was no FSDT reactivation dialogue, cause i also openend FSX directly after that.
That's to be expected because, the PMDG use the VC++ 2008 redistributable, we use the 2005 one so, it's a different version altogether, it's not like 64 vs 32 bit of the same version.
Even though if we imagine it was the 32bit VC++ package, why must this happen? Nearly every FSX addon needs a proper VC++ package, and renews this automatically. How a licence can depend on this?
It shouldn't, plain and simple. I have all the different VC++ 2005 runtimes that were released so far, all installed at the same time, and I never seen such thing.
However, there are reports of troubles when having both VS 2008 and VS 2005 installed on the same system:
http://www.fsdeveloper.com/forum/showpost.php?p=94172&postcount=19Apparently, the VS 2008 installer "updates" one of the VS 2005 .DLL and replace it with a buggy version. MAYBE, this could have an effect on the correct behaviour of our programs.
We use the VS 2005, for the very simple reason FSX itself is using VS 2005 runtimes so, we thought this would be the most compatible way.
Can you try the following:
- Uninstall ALL VS runtimes, both 2005 AND 2008, both 32 AND 64 bit versions.
- Reinstall any of our sceneries, which will put back just one VS 2005 version, and try if it makes any difference.