thank you for your assistance. But I still guess, that the problem is triggered through the installation of JFK.
It's not. It just happened, but it hasn't been triggered by it.
1) The system is running since february 2010, untill JFK was installed, the activation of FSX was never lost.
That doesn't really proves anything, except that your system ran fine since february 2010, it doesn't discount the chance the problem could have happened now.
With this logic, would you stop making regular backups, just because your system has been running fine for months ? Obviously not, a problem can happen anytime, that's why people made regular backups (at least, they should...). Your problem just happened after installing JFK, but that doesn't mean it was caused by it.
2) Last weekend a tried at least five times to install JFK, always after recovering the sytem with true image. I installed YFK before installing Zurich and Chicago, after installing Zurich and/or chicago etc, alwasy the same effect: FSX was acivated before installing JFK, and it was deactivated after installing JFK. This effect was five times only to be seen after installing JFK.
The FSX activation loss, instead, CAN be very likely created by the use of True Image, instead. Since you are always reinstalling JFK after using True Image, you are associating it with JFK. The FSX activation IS located in hidden and normally unaccessible areas of the hard drive sectors.
A 3rd party installer like JFK, cannot access this data in any way, even if it tried. A low-level hard drive access utility like True Image, instead, CAN.
By keep using True Image, you are replicating each time all the conditions that lead to the activation loss so, if you are keep restoring the system when it was in a situation were the loss of activation was imminent, keep trying you'll get the same result and, since you are doing always the same steps, which includes installing JFK, you get the wrong impression JFK was the trigger, when it clearly wasn't.
3) After installing JFK, other third parties software like UT2, Level D, goflight, aerosoft etc. were no longer recognized as trusted software.
This might have happened for two reasons:
1) The Windows secure store might have had a problem. This CAN be caused by something like True Image, but also can be any other system-related problem. And this CAN cause the loss of the FSX activation as well. But, this CAN'T be caused by the JFK installer, because it doesn't (and it can't) access the Windows trusted store in any way.
2) Your FSX.CFG file might have become corrupted. This *might* have been (in theory) caused by the JFK, because it reads and write the FSX.CFG, to read/store its settings.
But if this was the case, FSX would recreate a new one from scratch on the next start and, will NOT lose its activation, because nothing related to the FSX activation is stored in any of the FSX config files. You can verify this as many times as you like: remove your FSX.CFG, the FSX activation will always stay. Yes, you will have to re-trust all your modules, but this will not affect the FSX activation in any way.
This also was only to be seen after installing JFK, not after installing Zurich and/or Chicago withhout JFK.
There's no difference in operation between those installers, except the .BGL files they install.
This is the final proof the activation loss was entirely unrelated to the JFK installation. We compile all the installers from a common source code, and the .Dll module used (as you can clearly see during the installation) it's always the same, because it's downloade online by the installer so, it's absolutely the same things that gets installed and it's exactly the same operations that are being done, except for the actual scenery files.
In any case, a scenery installer can't cause this, not even theoretically because it can't access the FSX activation data, even if it could, because it's not stored in any of the FSX config files (is not even inside the FSX folder) the installer is accessing.
