Hi again, i know it's a bit frustrating for you and also for us that all the solutions you are giving us are not working. i just made all the possible solutions even from this post:
http://www.fsdreamteam.com/forum/index.php/topic,17484.msg122656.html#msg122656i'll start by making very clear that i have never installed or had any 3rd party antivirus or firewall or software that behaves like it, also by saying that the virus and firewall that comes with the system are totally disabled, this is real time, cloud.delivered protecion, automatic sample submission, controlled folder access are all disabled. exlusions folder I have an attachment on that one, so you could see all the files exluded. Also firewall which are domain, private and public network are all disabled.
I uninstalled and reinstalled all x64 x86 2005 2013 2015 VC++ . I restarted the system. after that i checked all virus potection were still disabled as well as the firewall protections disabled. then i installed the standalone addon manager from your website (version 4.5.0.10), inmediately after, i run fsdt live update so i checked the bglmanx64.dll file with this
http://onlinemd5.com/ (there's another attachment on that one) , just to make sure any missing VC++ or anything else i also run the .MSI located in here Prepar3D v4\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.MSI , and finally tried to rerun p3d.
sadly it did not work.
what for me was very curious is that, when checking the folder where bglmanx64.dll is located ( in my case is located in here: C:\Program Files\Lockheed Martin\P3D V4 Addons\Addon Manager ) i found two files named very similar: bglmanx64.dll and the same file without X64 so just bglman.dll.
i tried to run p3d without one of those files and guess what? p3d started as usual when i removed bglmanx64.dll , but when opening the addons window after loading whatever scenario to fly, just SODE was displayed.
i honestly don't know what else i could do in order to have everything working as always.
for the record the standalone addon manager version is a bit different from bglmanx64.dll file, where addon manager is 4.5.0.10 and bglmanx64.dll 4.5.0.17
also for the record, when i removed the bglmanx64.dll file from the folder, i rerun the fsdt live update and it was introduced the file again, which means, if i'm not wrong, the system is not interfering with the update neither VC++ or antivirus and firewall.
i hope that this one would make it very clear and letting you know i'm doing the exact same thing you're giving us a solution that, appearently in my case, it's not working.