GSX Inactive since WIN10 Update (?)

[pisco]

Hello,
Not sure that there is a link but since WIN10 (painfull) upgrade to 1803 version

1/ first time in P3D V4 : GSX was inactive, tried to activate via addon menu manager in P3D (reactivate the key), with no effect
2/ I tried to install GSX again, and addon menu manager in P3D disappeared


thank you

[hornet971]

Having same issue.

Please look in topic

[virtuali]

I updated to Windows 10 1803 a week ago, no problems whatsoever with GSX.

If you are missing the Addon Manager or the GSX menu (or both) from the "Addons" menu of the sim, the only possible reasons are either the antivirus blocking the update, or a problem with your VC++ libraries, which might be missing/corrupted, even by something not related to flight sim.

Disabling the antivirus while installing its NOT enough. In addition to that, when the antivirus is suspected to be the cause of the problem (it's the more common one), you MUST also configure it to exclude the Addon Manager folder before starting the sim.

About missing/corrupted VC++ libraries. They are the 2005 SP1, the 2013 and the 2015 version. Our software doesn't require all of them but, indirectly, Simconnect itself requires it so, if one of them it's missing, you'll have lots of issues, and not just with our software.

The linked thread named "Addon Manager not showing up in P3Dv4 **SOLVED**, was quite exhaustive:

http://www.fsdreamteam.com/forum/index.php/topic,17484.msg122656.html#msg122656

[pisco]

merci, but …
Tried
- re installation with antivirus disabled
- exclusion of the addon manager path from antivirus
- removing VC++Libraries and installing again + PC restart
(note that VC++2015 Cannot be installed because newer versions are already installed / attached my VC++ list)

without any effect on my issue

The fact is that GSX worked perfectly well, until this win10 update
I didn't change anything else on my computer and/or on P3D in between

 

[virtuali]

See this post here:

http://www.fsdreamteam.com/forum/index.php/topic,17734.msg124544.html#msg124544

The user reported he managed to fix it by unistalling/reinstalling P3D. Note that, we are not compatible with P3D 4.0 anymore so, you must have 4.1 at least.