Mattie941

For those that are interested, SteveFx's suggestion in another thread has fixed my CTD issues: https://www.avsim.com/forums/topic/633405-appdll-crash-and-kb5025221/?do=findComment&comment=5039267

Thanks. This seems to have fixed my CTDs

Hi - I'm just trying to find a fix for this myself and thought I'd give your recommendation a go. What do you mean my the documents folder? Is this the folder where FSX save files are stored? Or do you mean the FSX root folder?

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.

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?

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.

Thanks. 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.

A complete reinstall of Windows has not fixed the issue. Therefore I'm out of ideas...

Where did you find the latest version of SimConnect? How did you install it? I'm having issues with 10.0.61637.0 as detailed in my thread here: https://www.avsim.com/forums/topic/635654-fsx-apidll-crash-no-fixes-in-other-threads/?tab=comments#comment-4985819

I tried installing from Just Flight and from the Acceleration SDK. I run through the steps to install Acceleration SDK but when i run the SimConnect.msi, it still installs SimConnect 10.0.6129.0. It's strange because when I run the SimConnect.msi file, the "run as administrator" pop up asks if I would like to install SimConnect 10.0.61637.0 but then when I click "yes", the installer window appears it says SimConnect 10.0.6129.0. When I check for the version installed it is SimConnect 10.0.6129.0 and FSUIPC is still reporting a mismatch. The file properties of the Microsoft.FlightSimulator.SimConnect.dll file in "...\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib\managed"says that it is version "10.0.616.37.0 (FSX-Xpack.20070926-1421)" and yet it does not install this version. I'm not sure what I'm doing wrong? Found here: https://support.justflight.com/support/solutions/articles/17000100065-simconnect-files-for-fsx-p3d

John Dawson noticed that there is a mismatch between my FSX version and the Simconnect version: 31844 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) I tried uninstalling SimConnect but the latest version on the FSX Acceleration SDK is 10.0.61259.0. When I reinstall and start the sim, I still have the same mismatch. Therefore: How do I remove 10.0.61637.0 so that the FSX version matches? Or where do I find/download 10.0.61637.0 to update my SimConnect version

I have been running FSX from a fresh reinstall. Therefore the FSX.cfg, DLL.xml and EXE.xml are all stock files. I have not been able to recreate the crash from the fresh reinstall at the moment. I can only recreate the crash once I have installed FSUIPC and some addons to run using it: FSrealWX lite, FSFO v3, vasFMC 2.1, vPilot and Skytrack (my VA ACARS). The API.dll CTD does not seem to be related to any single one addon or combination of addons (I have tested with individual addons and combinations of addons). I have recreated the CTD on start-up when the simulator crashes while at the splash screen before I can load the menus: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x0003afa2 Faulting process ID: 0x5ec Faulting application start time: 0x01d9b313f32959f4 Faulting application path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL Report ID: dc23c17b-fdb3-42dc-9e2d-66f93253de7d Faulting package full name: Faulting package-relative application ID: From Process Monitor, the last file FSX tries to read before "Thread Exit" is the kernel32.dll file. The last file before "Process Exit" is the quartz.ttf file in the "Fonts" folder. However, in the Result column in Process Monitor, it reads "SUCCESS" for both. I'm not too sure what this means though...

The crashes first started happening for me at the beginning of May. However, I was away for April so the timeline works regarding the Windows update. I have since managed to complete a few ~2 hour flights offline. The crashes are definitely more frequent on VATSIM. I run the latest version of vPilot as my client. I've had a error message from the FSX on startup "Flight Simulator has detected a problem with a third-party software program", blaming FSUIPC for thr crash. Could this be an issue with FSUIPC or vPilot and the April Windows update?

Hello, I keep running into an API.dll crash. I have completely reinstalled FSX. I have UAC turned off. I run on very minimal settings and I have monitored VAS and it is peaking at 2GB and yet I am still running into API.dll crashes according to the event viewer log. The sim also sometimes CTD with an API.dll error on start-up, before I get to the loading screens. The same issues persist with the sim installed on the SSD in C:\FSX and in it's current location on the HDD. Example crash log: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x0003afa2 Faulting process ID: 0x2fa4 Faulting application start time: 0x01d9aeaeab4a9ebe Faulting application path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL Report ID: 310022d2-51c7-41ac-acaa-e6bdbc0050e5 Faulting package full name: Faulting package-relative application ID: I have a 2017 Medion P6661 gaming laptop: GeForce GTX 950M Graphics card 15.6 Inch Screen Intel Core i5 6200U Processor 8 GB RAM 1TB Hard Drive + 128GB SSD Windows 10 Any ideas on what could be causing the crash?

Thanks for the replies all. I found the issue and have a solution. The fault was not with GSX (sorry for the accusation). The fault was a mixture of another scenery and my meddling. The scenery used custom ground vehicles and updated the LWCFG.spb file to use these custom vehicles. Due to the limitations of my setup, I move my scenery folders to another drive, outside of my main FSX root folder. However, doing this meant that the fallback in the texture.cfg for new ground vehicles in the Simobjects/Groundvehicles folder could no longer locate the necessary textures because they were not in the Addon Scenery folder. I can think of 3 solutions for this: 1) Move the scenery back to the Addon Scenery folder in the FSX root directory 2) Copy the textures from the scenery into each ground vehicle texture folder (however this defeats the original desire to save space on my small SSD) 3) Find the textures the new ground vehicles are using and copy them to one of the ground vehicles texture folder and adjust the fallback in the texture.cfg for all vehicles to find the copied textures I went with option 1 for now (only because I don't have the time to implement option 3)

Hi, I recently installed the trial version of GSX and uninstalled once I had checked it out. However, some airport ground vehicle models still exist without textures (see image). I've tried reverting to a backup of my Simobjects/Groundvehicles folder and restored old backups of the veh_air_*** files in the Scenery/Global/Texture folder, but the black models still remain. Where can I find and delete these ground vehicle models to restore the FSX default vehicles? Cheers, Matt

Thanks! I ended up changing the links manually in the regedit but it looks like the link you provided essentially does the same thing.

Thanks for the response. I have the default aircraft.cfg from the model. The gold nugget is the [flightsim.X] sections of the FLAi aircraft.cfg files because that needs to match the VMR file that I also have. It's tricky and extremely time consuming trying to recreate that. I understand that it could be a grey area with regards to IP. However, since I already have the models, repaints and core aircraft.cfg text, I didn't think it would be an issue. Thanks anyway.

Hi guys, My PC recently had an issue and was repaired in a PC shop. They've fixed it so all seems well. However, I now have an issue where FSX saves my save files, setting files, etc. The files used to be stored in "D:\Users\[USER]\Documents\Flight Simulator X Files" but now they are being saved in "D:\Users\[USER]\OneDrive\Documents\Flight Simulator X Files" Being saved in OneDrive is causing some issues with locked files, etc. How has this happened? How do I changed it back to how it was before? I think this is a Windows issues because the same thing has happened for save files for other games and vpilot VMR files. Thanks in advance

Hi guys, I'm somehow managed to corrupt a few of my aircraft.cfg files from the FLAi model matching data I have. I know I'm asking a lot, but could someone please send me the aircraft.cfg files for the below aircraft? I have the IP problematic stuff like models and repaints, I just need the aircraft.cfg files. Please please please can someone do me a huge favor? CRJ2 B789 B738 AT45 AT75 A320

Thanks for the reply. The solution is here: https://www.flightsim.com/vbfs/showthread.php?290729-Installing-FSXSave-1-05-issues

Hi guys, I have had MSFS 2020 installed and working before Christmas. I tried again today and I can't load the menu. The "please insert disc" pop-up appears and I cannot load the game. The ~2 GB installer is in the default location and I installed the remained of the game to the D : I have tried: - turn off firewall - exempt the game in the firewall - change DNS settings to Google - launch from desktop tile - launch from MS Store - launch from Xbox app - launch as administrator - reset router - exemption in window defender - confirmed correct system time and date settings I have since uninstalled the game and deleted all the file in the "D:\Users[USERNAME]\AppData\Local\Packages" folder. Now when I re-download the ~2 GB installer from the MS Store, the game loads and the "please insert disc" pop-up appears. I can't reinstall the files I have deleted and I can't get anything to work. Please help. Any solutions? Platform: Digital - Windows Store Windows 10 version: Insider Preview (20H2) Windows 10 OS Build: 19042.867 Dev mode wasn't activated

I know I'm a little bit late to the party here. I'm currently trying to install FSXSave into FSX and I'm having the same install issue most of the people I've seen. Unfortunately the link provided doesn't seem to work anymore. The problem I've got is that I cannot unpack the setup.exe to get access to the FSXSave.exe. I only have the setup.exe or the FSXSave.msi files that present in the zipped folder downloaded from the website. I've added the fsxsave105 folder to the FSX/modules folder. For the entry in the dll.xml file, is it as simple as copying the FSUIPC entry and replacing "/Modules/FSUIPC.dll" with "/Modules/FSXsave.msi"? Or I've also read it might be the exe.xml file. Is it as simple as adding the below? Is there anything else that needs adding anywhere? <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSXSave</Name> <Path>Modules\fsxsave105\setup.exe</Path> <NewConsole>True</NewConsole> </Launch.Addon> Do I need to do both of these? Or one? Or neither and something else?

No luck unfortunately. The sim crashed about 20 minutes into my flight. Really frustrating. The new error log is uploaded to the above link. I'll add it to the thread when the embed links allows. Any idea why this is suddenly started happening?