Products Support > GSX Support FSX/P3D
Couatl64_P3D.exe - Entry Point Not Found **WINDOWS 7 is no longer supported**
achmedfsx:
By the way: https://support.microsoft.com/de-de/topic/kompatibilit%C3%A4tsupdate-um-windows-7-auf-dem-neuesten-stand-zu-halten-5fe4a218-adf1-9074-9522-bea956cf149b mentions Api-ms-win-downlevel-ole32-l1-1-1.dll 10.0.14393.0 from 22-Jan-2018. Not sure if I get it (maybe for enhanced support - entrprise customers - only ?).
virtuali:
Have you tried downloading from the Catalog link ?
https://www.catalog.update.microsoft.com/search.aspx?q=kb2952664
olseric:
--- Quote from: virtuali on February 18, 2022, 06:59:21 pm ---You must fix the startup error and, as far as I know, the only way to fix it is getting hold of the updated api-ms-win-downlevel-ole32-l1-1-1.dll, because the function we use must have been moved there, so it's not present anymore in the api-ms-win-downlevel-ole32-l1-1-0.dll you have. This .dll is NOT present in Windows 10, so it must have appeared somewhere as an update to Windows 7.
--- End quote ---
I tried that as well. I plugged the 1-1-1 version into Windows and it was still calling the 1-1-0 version. I even went a step further renaming 1-1-1 to 1-1-0 to see what would happen. The error went away, but GSX wasn't loaded properly in FS (showed that I needed to activate it, Coautl not running, etc).
I'll hunt for the older installers now that I know where to seek.
--- Quote from: virtuali on February 18, 2022, 07:09:08 pm ---Have you tried downloading from the Catalog link ?
https://www.catalog.update.microsoft.com/search.aspx?q=kb2952664
--- End quote ---
I'll try that as well and report back.
achmedfsx:
Before downloading KB2952664, I did a "wmic qfe list > qfelist.txt" and opened qfelist.txt with notepad.
-> http://support.microsoft.com/?kbid=2952664 AH3 Update KB2952664 NT-AUTORITÄT\SYSTEM 7/12/2018
It was an update for Win 7 telemetry, the libraries are in folder C:\Windows\System32\CompatTel.
The last minutes, I tried some steps similar to olseric's :
- put C:\Windows\System32\CompatTel at the end of my PATH environment variable (system properties - advanced system settings - environment variables)
- put the library api-ms-win-downlevel-ole32-l1-1-1.dll into folder C:\Games\FSDT\Addon Manager\couatl64 (where couatl64_P3D.exe resides here)
- renamed it there to api-ms-win-downlevel-ole32-l1-1-0.dll
but it will not be taken.
- I didn't copy it to windows\system32 as I feared to destroy my system completely.
- I didn't try to "register" this dll (regsvr), may
Dependency Walker shows the entry point GetErrorInfo in api-ms-win-downlevel-ole32-l1-1-1.dll,
the question is how this library is searched.
I suppose that GetErrorInfo isn't called directly in api-ms-win-downlevel-ole32...dll but from another library.
I searched the registry for api-ms-win-downlevel-ole32-l1-1-0.dll : no luck, so it may not be searched by "dll registration".
I searched the dll's in windows\system32 and found the text "api-ms-win-downlevel-ole32-l1-1-0.dll" in some dll's,
e.g. wininet.dll or jscript9.dll (dependency walker shows them connected to the mentioned ole32.dll).
That may be the reason why replacing api-ms-win-downlevel-ole32-l1-1-0.dll in system32 by 1-1-1.dll may lead to other errors:
all these api-ms-... and the other (important) dll's seem to reference each other in a hardcoded way inside each dll.
If this is true, we will not solve the problem without replacing a whole bunch of system32 libs (destroying Windows ?).
achmedfsx:
Sorry for spaming this thread, but I gave it a last try.
I searched couatl64_P3D.exe for the library name - bingo !
I changed the lib name from ...1-1-0.dll to ...1-1-1.dll in couatl64_P3D.exe
with a hex editor (see the attached image)
while C:\Windows\System32\CompatTel was still at the end of my PATH envvar.
After P3D started, I got a message that couatl64_P3D has been changed,
I clicked OK and was on Eglin's runway.
I pressed Ctrl+Shift+F12, ordered a car to a gate, the car came.
As it's late here, I have to exit (= go to bed).
No visible error at P3D shutdown (have to look in Win event manager tomorrow).
But why is a hardcoded reference to api-ms-win-downlevel-ole32...1-1-0.dll in couatl64_P3D
as this lib doesn't contain GetErrorInfo as you stated before ?!? Strange !
What makes me wonder:
after I removed C:\Windows\System32\CompatTel from the PATH,
P3D start leads to "Couatl64_P3D cannot be started as api-ms-win-downlevel-ole32-l1-1-1.dll is missing on this computer".
But in P3D, I see the addon menus of GSX and XPOI.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version