Problem with bglmanx Version 2.9.0.8 , works with 2.9.0.6

[DdD]

For Information, it seems to have a problems with the bglmanx.dll version 2.9.0.8

After an Hard Drive failure, I re-installed completely my FSX and addons on a new HD, I have reinstalled all the FSdreamteam scenery addons without any problem (Ihave all the collection),
But when I tried to reinstall GSX, I received the error about bglmanx and had a crash to desktop.

After reading few messages about the same issue and try different solution (uninstall, reinstall scenery, fs_addon_manager) without any success, (even if some peoples said that it is not related to FSdreamteam product) I uninstall GSX and remove the following files from the FSX folder:

bglmanx.dat
bglmanx.dll (2.9.0.8 )
bglmanx_aerosoft.dat
bglmanx_fbeam.dat
bglmanx_fsdt.dat
bglmanx_qwings.dat

I Noticed that every time, the Version 2.9.0.8 is installed during the installation process.

And by luck, I have kept my old HD, and I have restored the bglmanx.dll 2.9.0.6 and replace the files from my "old" installation.
I started my FSX without anyproblem, the detection of bglmanx.dll was fine.
Then, I reinstalled GSX and upgraded bglmanx.dll 2.9.0.6 to 2.9.0.8 without any problem.

I hope it may help some people.

[virtuali]

For Information, it seems to have a problems with the bglmanx.dll version 2.9.0.8

Then, I reinstalled GSX and upgraded bglmanx.dll 2.9.0.6 to 2.9.0.8 without any problem.

So, you don't really have a problem with 2.9.0.8, because it now runs on your system. It seems you get the bogus message about the module not being safe only *after* trusting the previous version ?

That would indicate some kind of problems with the Windows trust system, which is the main reason for that message to appear. Prepar3D, for example, doesn't require modules to be trusted anymore, so that message doesn't exists there.

[DdD]

If I did not restor my files from my old HD, I would be still trying to solve the issue :-)
So it seems that I don't have the problem with the current version because I used the 9.0.2.6 certification process.
So yes, with the 9.0.2.8 it crashed some few seconds after click "YES" to trust the file and worked perfectly with the 9.0.2.6.

I don't exactly if the problem comes from the certification of  windows trust system or the 9.2.0.8, but what I know is that the 9.2.0.6 doesnt't cause the problem. So, as IT guy, I only can notice that something is different in the 9.2.0.8 that doesn't allow a correct certification during the process compare the 9.2.0.6. And by upgrading the version after, the problem doesn't appear cause the certification process is not done completely because it is already done.

So even, it is not the "real" main problem, the difference between these version make than one work and the other don't.

Where I'm surprise is that if Windows doesn't trust a file, it is because the certification key is not correct somewhere. So if one version correctly is trusted, why the other don't? Because Windows?

[Tanner]

I also join me to report the same problem. I just bought exactly the scenery of JFK V2, once installed and having updated the software automatically I received the same error causing crashes to the desktop. The problem I think is due to version 2.9.0.8 bglmanx.dll. I had to uninstall GSX and Zurich because I can not start FSX. A real discomfort I would say, quite serious.

Can you tell me how to solve?

[DdD]

btw, thank you for your answer! :-)

[DdD]

@Tanner. Cause the copyright reason, I'm not able to send you the impacting file. Bit I would suggestion from FSdreamTeam to send you all the bglmanx 2.9.0.6 (or give me the authorization to do so). and see if it solved your problem?

Because in term of time optimization it is quite faster to replace these file than trying to uninstall, re-install, all your FSD product.

[Tanner]

I thank you for your availability and the help! This is a problem that needs solving staff directly. It is normal to experience such an error. Now, unfortunately, without this file I find myself not being able to use their product no

[virtuali]

And by upgrading the version after, the problem doesn't appear cause the certification process is not done completely because it is already done.

I don't know what you are saying here but, it's seems is exactly like I've said: 2.9.0.8 DOES WORK on your system, but only if you trust the previous version first.

Which clearly proves the problem is not the file *itself* because, as you said, the SAME file now WORKS. Which means, the file itself IS working, but something went wrong during the previous trusting session.

There's no difference whatsoever between the previous and the current version from a certificate point of view. The digital signature we use hasn't changed since last year, and will expire in 2016, both things you can of course verify by checking the "Digital Signature" flags.

[virtuali]

@Tanner. Cause the copyright reason, I'm not able to send you the impacting file. Bit I would suggestion from FSdreamTeam to send you all the bglmanx 2.9.0.6 (or give me the authorization to do so). and see if it solved your problem?

There's no problem sending him that file. Note that, a bglmanx.dll without the related bglmanx*.dat files of the *same* version it came with, won't work in any way.

[DdD]

Yep sorry, I used my tablet but don't really like tapping on it.

"it's seems is exactly like I've said: 2.9.0.8 DOES WORK on your system, but only if you trust the previous version first."

- Right :-)

 "Which clearly proves the problem is not the file *itself* because, as you said, the SAME file now WORKS. Which means, the file itself IS working, but something went wrong during the previous trusting session."
"The digital signature we use hasn't changed since last year, and will expire in 2016, both things you can of course verify by checking the "Digital Signature" flags"

- It is where I would have another interpretation. Cause what I tried to say is that the problem seems not really related to the certificate itself but during the process. If that was the case, I would have an certification error, not a crash. As you said, the bglmanx.dat and bglmanx.dll are different from another version, maybe it is not the dll itself but the dat file or somethings used in this file that is different from older version? I confess that I did not compare both file and did not try the 2.9.0.7.

The only difference between the installation where it crash and where it works are theses files, maybe it is not related directly to these files but at the end, a difference(s) between these files make them not working.

But anyway, in my case I solved my problem and now I keep a copy of the 2.9.0.6 files in case of. The next time I have to reinstall my computer, I'll try to notice if this issue appear again.
Thank you for your time and your support ! :-)

[DdD]

@Tanner.

"There's no problem sending him that file. Note that, a bglmanx.dll without the related bglmanx*.dat files of the *same* version it came with, won't work in any way."

This evening, I will send you these files as "Umberto" (thank you!) gave me the authorization to send you these files. To see if it solve the issue for you, if you want to?

[Tanner]

Yes, that's fine, then wait for the files, thanks a lot!!

[molino]

Hi,

I have a very similar issue.

I bought GSX yesterday and installed onto my machine (WinXP 32bit) but I cannot make bglmanx 2.9.0.8 work.

I have followed the typical steps I have found throughout the fsdreamteams forum topics (uninstall GSX, turn off antivirus, install GSX, check compatilibility mode on fsx.exe, check if certificate is valid etc.) but no luck so far.

Is it possible to get Add-on Manager 2.9.0.6 somehow so that I can give it a try?

Thanks!

[virtuali]

Is it possible to get Add-on Manager 2.9.0.6 somehow so that I can give it a try?

Please try the solution explained here:

http://www.fsdreamteam.com/forum/index.php/topic,9341.0.html

[Hor1463]

Hi, I have reinstalled all my airports, but the issue when starting FSX?? Can you send me the version 2.9.0.6? Roland

E-mail: Hor1463@aol.com
Thanks