i already said that i did all those simconnect libraries install.it didn't solve the problem.
And I already said that this doesn't ALWAYS fix the problem.
i will try to delete simconnect libraries in safe mode but i need to know how to delete registry for simconnect entries.
The other user that replied to you, which I also pointed it out, already explained how he did it. I'll copy it here, again:
What I did was search the registry with the keyword "simconnect" delete the folder entry and repeat using F3, reboot. Make sure you back up your registry before deleting anything.
i am very very disappointed at FSDT. people who are having these issues have common addons e.g. ASN,PMDG777,REX4.before saying a product is fully compatible with release,i think developer should test it more thoroughly before final release.
GSX is 100% Fully compatible with P3D 3.1, and it has obviously tested with it ( I don't have any other P3D version installed ), but you cannot expect it would FIX your SIMCONNECT PROBLEM that doesn't have anything to do with it.
i am sorry i can't agree with you.even what u r saying regarding the simconnect behavior.there should have been a release note regarding this issue in the first place with the latest gsx release.
There's shouldn't be any release note, because a failure to load Simconnect SP2 is NOT something that is supposed to happen, and it's not obviously caused by our software, which is instead a VICTIM of it, but that we are supporting anyway, even if it's not caused by any of our software or installers.
because honestly the fact is users are unable to even start the simulator just because of a simple addon conflict is a catastrophic failure.
The error message you see, is NOT coming from the Addon Manager. It's coming from Windows itself, because Simconnect SP2 is not loading, so P3D doesn't start because of this. Under FSX, if Simconnect fails to load, the affected addons will just disappear but sim will continue to load. This seems to be a different behavior in P3D, which is of course outside our control.
i am sorry everyone for being angry.but,at this point i am very angry with FSDT.Simply because we have works to do other than solving some stupid libraries conflict which wasn't suppose to happen & it was the job of developer to make sure smooth experience as user end.
Your problem is that Simconnect SP2 is not loading. There's nothing we can do to fix this, other then tell you different ways to fix it, which is exactly what we did.
The real problem is the official Simconnect installer doesn't seem able to restore every issue, and sometimes you must act manually, as already suggested by the other user.
I hope you are not suggesting OUR installer should try to replace the Microsoft one and trying to hack your registry and fix things!!
ban me or whatever u like to do.but,as a paid user i do have right to ask proper product support that i paid in the first place.
I'm AM supporting you. And you have been given several different solutions so, what's the "ban" it's about ?