APP.DLL crash and KB5025221

[airernie]

About two weeks ago I started having multiple API.DLL crashes with FSX.  I ran SFC and DISM without success.  Also FSX repair.  I even wiped and reinstalled SIMstarter NG and FSX, which was the ultimate move due to the addons I would need to reinstall..  None of which resolved the issue.

I eventually ran AppCrashView and noticed the crashes started 4/12/2023,  I started looking at programs that had been installed around that date and found Windows update KB5025221.  I uninstalled it and as of two days later I've not a API.DLL crash.  

I can't say with 100% certainty that that was the issue, but the evidence is pointing in that direction.

Edited April 26, 2023 by airernie

[Epic7]

heyy 
brother can u tell me how can i uninstall this update cuz i also have this but in control panel i where i can uninstall updates this doesnt show up 
thank u

 

[airernie]

Type 'View you update history' in 'Type here to search box on taskbar' and click link to open. Once open select 'Uninstall updates' from top left of window.  Locate KB5025221 in the Microsoft Windows section and right click to uninstall.

Be aware, that Windows might try to reinstall next update unless Microsoft fixed the issue, so you may need to uninstall again.

If the update isn't listed, then install AppCrashView and locate when the issue started and look for something that was installed around that date.

 

Edited May 10, 2023 by airernie

[Epic7]

Hello Ernest 
thank u for solution 2 weeks have passed and no api dll crashes anymore  u are a lifesaver 
thanks

[airernie]

Thanks. I hope your luck continues.  A recent update threw me back into the API.DLL nightmare and if it's the update I think it is, then Windows won't allow me to uninstall it.

Hoping I can find a workaround so I can get my FSX back.

 

[Epic7]

Same thing happened with me i couldnt uninstall the update so i installed a cusotom windows iso it has updates disabled so works fine and also microsoft is now auto updating 21h2 to 22h2 so it might be that the update got installed again
thanks

[jessy0506]

Same issue here! Sadly can't uninstall this update.

 

-jessy

[Mattie941]

Same issue here. It's a shame. 

I recommend everyone that is experiencing the issue to submit a support request with Microsoft: https://support.microsoft.com/en-us/home/contact

This will help increase exposure to the issue and will hopefully expedite a hotfix. 

[Mattie941]

I recently tried running FSX again after the recent windows updates but I still get the API.dll CTD from a clean install of the game. Does anyone know of a fix?

[airernie]

As you can see from the first message in this thread I've been fighting the problem since early April.  A second non-removable update took me down again.  I then upgraded to Windows 11 hoping the problem would go away.. it didn't.

However, I was able to resolve it by not having FSX launched by SIMStarter NG.  Something which may not apply to you.

I still let SIMStarter do its thing, I just start FSX after SIMStarter has completed its tasks.  No recent API.DLL issues. 

It doesn't mean that I'm free and clear.and that SIMStarter is the issue.  However, for the few flights I've done since I've adapted this strategy it's worked.  Prior to the change all but one of my flights ended in a API.DLL crash.

Will update if it changes..

Ernie

Edited September 5, 2023 by airernie

[Mattie941]

Thanks for the reply. 

I don't use SIMStarter so not a fix I can try unfortunately. I was just looking at Windows 11 upgrades, so glad you mentioned it doesn't work before I spent my money. 

For me, it always seems to be when I try to connect external programmes. It's not any programme in particular and can crash when I connect any of them. E.g., vasFMC, vPilot, FSrealWX, VA ACARS, etc.

[JohnDeSoto]

Well. I have learned that his forum is famous for not letting you edit your own forum entry.

So, it must be allowed to think a little bit so that no later edit (by moderator) is necessary.

Back on topic. Randazzo is one man - amongst quite a few - who has helped me with "app crash" issues. I just try to remember what he said. [not quoted word by word]:

1. Until p3dv3 all known simulators have been 32 bit applications, and that's also true for fsx. [...] With a 32 bit application, you always have the problem that this application includes a "4 Gigabyte hard limit". That means, that even with 16 Gigabyte RAM (or more), and on a Windows 64 bit o/s, you're "able" to receive app crash messages, when your simulator software is limited to 4 GB. As I understand Randazzo, it is a pure simulator software problem, which affects ALL 32 bit simulators, e.g. fsx, or p3dv3 (or earlier).

2. Randazzo also has a better name for this problem, not "app crash". He mentions it as "The (32b) application has run out of virtual address space (VAS)".

3. I don't have so many things to add. Fsx was invented in the year 2006 as a "32 bit only" application, so, nothing like "fsx 64 bit" will ever exist.

4. Until the beginning of the year 2023, I was able to say that nevertheless, fsx goes perfectly fine together with Win7 64 bit. But Win10 is something completely different. I'd recommend, also again with the help of Randazzo, p3dv4 (which is 64 bit native) or later, together with Win7 or Win10 (yes, p3dv4 also works with the old Win7 64b).

If you still receive app crash messages although both, your simulator and your o/s is 64 bit, then your hardware isn't strong enough.

So far taken from one of Randazzos unbelievably helpful handbooks, which he sells together with his products.

PS: The worst combination could be, a modern Windows o/s (2015 or later) together with the old fsx (since 2006). I haven't tried that yet, but you say that could cause some difficulties, and I could imagine to not try fsx again, I mean, 17 years since fsx was invented ... Today I can say, that one or two new cpus are on the market since back then, and 64 bit simulators that you like to operate with these new cpus ... 

[airernie]

On 9/5/2023 at 4:04 PM, Mattie941 said:

For me, it always seems to be when I try to connect external programmes. It's not any programme in particular and can crash when I connect any of them. E.g., vasFMC, vPilot, FSrealWX, VA ACARS, etc.

The only executables I run with FSX are Chase Plane, Active Sky 2016, SPAD and HID Macros and those are launched though SIMStarter.. I thought Chase Plane was my problem, but if I didn't pair it with FSX using SIMStarter it worked.

I haven't tried vPilot since my move to Windows 11, so i should give it a go. Unfortunately, I don't use any of the others you mentioned so no feedback.

Edited September 7, 2023 by airernie

[Epic7]

Any updates on this im also again getting this issue with the latest updates from microsoft win10 22h2
idk why they cannot fix it for once 

[airernie]

Sorry, no.  There must be FSX Boxed users who haven't experienced this issue, but none have posted.

The only 'fix' I've heard about is to use a locked pre-update version of Windows 10. Then never update it. Not the best solution, but it seems to work for those using FSX with Windows 7.

As for me, I mentioned my solution in a previous post, but I still get API.DLL crashes.  Just not every time I launch FSX.