Well not, it's a bit more complex than that.
It's most likely a combined FSX+Windows bug that happens with any module that is digitally signed (doesn't ever happen on Prepar3D, and the module it's the *same*) and sometimes the trust system gets confused.
The first thing to try is just restarting Windows, sometimes that error just goes away. And, in any case, keep allowing the module to run, even if FSX says it might not work, always allow it, even if it crashes, try a couple of times and try again after a Windows restart.
If that doesn't fix it, assuming you are sure you installed the most current version (to be sure, download and install the Stand-Alone Addon Manager for FSX), check the following:
- No compatibility mode is enabled for in the Properties->Compatibility tab for FSX.EXE
- The antivirus is configured to ignore the FSX\bglmanx.dll module
- The FSX\bglmanx.dll is not corrupted for some reason (bad download, or antivirus corrupting it). To verify this, you can right click on it, select the "Digital Signature" tab, and check if it's stil valid. If it's not, it means the file has been altered on your system.
