P3D loading crash after last Addon Manager

[ColoniaAir]

Hello

Today I updated the Addon Manager. After that Update P3D failed to start, during loading Screen Message:

"Prepar3D exe stopped working.."

The Error Message in the Eventviewer:

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.4.22.19868, Zeitstempel: 0x588f7cbf
Name des fehlerhaften Moduls: MSVCR120.dll, Version: 12.0.21005.1, Zeitstempel: 0x524f7ce6
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000a46a9
ID des fehlerhaften Prozesses: 0x1cf8
Startzeit der fehlerhaften Anwendung: 0x01d282f2a48fcce5
Pfad der fehlerhaften Anwendung: D:\P3D\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Berichtskennung: 3c7bb22e-ffbc-476e-94b9-c33018e29d0c

Then I opened the dll.xml in the Program Data\Lockheed Martin\Prepar3D v3\ folder and removed this line:

  <Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>


P3d starts without problems but without FSDT Addons of course. So I guess there is something worng with the last update and the bglmanx.dll, beacause when I restore this line, p3d crash again during loading. I'm using latest P3D Version with HF3 in Windows 10.

[FloRyan]

Same problem here for me!

[Fi5kuS]

Same problem.

If I uninstall Addon Manager, OR disable it in the C:\ProgramData\Lockheed Martin\Prepar3D v3\dll.xml file, P3D starts up without any issues.

[virtuali]

There's nothing wrong with the last update and, of course, I just tried it again, to be 100% sure, and there are no issues whatsoever, with P3D + Hotfix 3.

Try a clean reinstall:

- Uninstall the Stand-Alone Addon Manager, reply YES to the question "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl engine ?"

- Restart Windows

- Reinstall the Addon Manager.

[Fi5kuS]

There's nothing wrong with the last update and, of course, I just tried it again, to be 100% sure, and there are no issues whatsoever, with P3D + Hotfix 3.

Try a clean reinstall:

- Uninstall the Stand-Alone Addon Manager, reply YES to the question "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl engine ?"

- Restart Windows

- Reinstall the Addon Manager.

Tried it, didn't work unfortunately. Also on the same P3D version + hotfix as you are.

[ColoniaAir]

Also tried it, the problem is still there...

There was a new fsuipc update yesterday which I installed (4.962) before the addon manager update, perhaps this matters

[Dean B]

I am also having the same issue.

Does this version require all P3D 'hofixes' to be installed?  I was told there is no requirement for the last hotfix unless you are using SLI configuration.  I use a single 980ti, therefore it's not installed.

I am still using P3D v3.4.18.19475 because of the terrible VAS leak I was experiencing using 3.4.

-Dean.

* I also updated FSUIPC to the 4692 beta before updating SAM.

[virtuali]

Try installing again, it's possible that with all these people downloading, you might have got a bad download,

[Joshsum]

Same here. Tried to load my FSDT stuff to a bran new install of p3d and the program crashes when trying to start. I tryed 3 times doing a clean install each time.

[virtuali]

Try installing again, it's possible that with all these people downloading, you might have got a bad download. I'm repeating this, because I just reinstalled the Addon Manager now, and it works normally.

[zk]

I am having the same issue too.  Tried it a handful of times.  Same results.  bglmanx is definitely the culprit.  Please help!

[Joshsum]

I just downloaded and installed again with the same result. This is 4 times today that I have done this. First I thought I needed to update the client of p3D to the latest but same thing. I even did the updater thing too.

[Joshsum]

Well I just did it a fifth time and now it works. strange

[FloRyan]

Well I just did it a fifth time and now it works. strange

Yep works!

[virtuali]

Well I just did it a fifth time and now it works. strange

That's what I suspected...