Nearly unpossible. Till today I've installed only GlobalX, Switzerland Prof, ActiveSky, RealEnvironmX, PMDG 737 and WilcoAirbusses.
Fact you were able to install other addons, doesn't mean anything, and antivirus might still have blocked the download of the *Addon Manager* files, creating the mismatch between versions.
Can you right-click on the bglmanx.dll file in your FSX root, select "Properties", select "Details", and check the version number ?
About the DLL.XML, that it WAS corrupted it's a fact. That the Wilco installer can corrupted it, is also very well known:
http://forum.avsim.net/topic/330232-wilco-corrupts-xml-file/http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspxNote that, it's not entirely correct the Wilco installer "corrupts" the XML file, it's the *PMDG* installer that, if run after Wilco one, will get confused by the change of CR/LF characters, which shouldn't really be a problem.
In fact, our installer works either way and it's not being confused, but it WILL report a file corrupted by ANOTHER installer that ran before and WAS confused by the Wilco installer...
No, completely actual - yesterday and this morning updated
Have you run a full update AFTER installing one of our sceneries ?
I searched for the bglmanx.dll and had a look in the dll.xml.
There stands the following line: <Path>bglmanx.dll</path>
The bglmanx.dll is located at c:\ProgramFiles\....etc.
Could that be a problem?
No, because the line Path is relative to the FSX path, so that's correct. And, of course, because you HAVE been asked permission to run the Addon Manager
ZurichX uninstalled again: Now my FSX misses the Extras-Menü - with the Addons (FSUIPC etc.)
This because, when the installer found your ALREADY corrupted DLL.XML file, and offered a choice to create a new one from scratch, the new one doesn't contain anything except the Addon Manager line. The installer hasn't said it would have "fixed" your already-corrupted DLL.XML file, it said it will create a new one from scratch, so it can't contain all the previous modules you had before.
Note that, fact you had other addons working, it's not proof your XML wasn't corrupted. It was, but FSX is tolerant enough that in presence of a corrupted XML file, it will still load the sections not corrupted.
In any case, nothing of this matters at all with the problem you are having. As I've said in my previous message, if you ARE being asked permission to run the Addon Manager, it means your DLL.XML file it's OK!! So, stop worrying about it, because that's not the problem.
It's possible to activate the Simconnect diagnostic mode, this way:
Open notepad, and copy the following text:
[SimConnect]
level=verbose
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell you what's going wrong. Let me know what you are getting, so we can have an idea what's happening.