CTD loading in!

[babybus]

Every time I load in any A350 variant or livery I get a CTD during the loading process. File below! This has only been since the last updated. 

 

Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001f0ffe2
Faulting process id: 0x3F4C
Faulting application start time: 0x1DBFA0C29252D92
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 19009dbd-ed76-46f0-bd9b-82f7fa193623
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[haza2]

33 minutes ago, babybus said:

Every time I load in any A350 variant or livery I get a CTD during the loading process. File below! This has only been since the last updated. 

 

Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001f0ffe2
Faulting process id: 0x3F4C
Faulting application start time: 0x1DBFA0C29252D92
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 19009dbd-ed76-46f0-bd9b-82f7fa193623
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Hello,

Have you tried a reinstall and deleting your WASM folder? 

Kindest

[babybus]

Hello, I have never had to do that before. Would you mind explaining how I clear the WASM folder and also if it will affect any of my other add ons?

[babybus]

I can't even uninstall the product. ini has really dropped the ball! Not impressed. 

[Miksu1977]

20 hours ago, babybus said:

I can't even uninstall the product. ini has really dropped the ball! Not impressed. 

Same problem here also, can't uninstall A350 using ini manager. It doesn't do anything. 

Edited July 23 by Miksu1977

[Miksu1977]

Managed to manually remove A350 folders and did reinstall inimanager and everything works again

Try to load 1000-variant first and if it loads shut the sim down, restart and try to load 900 again, this way i got it working

Edited July 24 by Miksu1977

[babybus]

Thank you. Really shouldn’t have to do all this. Not impressed. 

[Eddie]

Hello,

Apologies for the inconvenience. We're having some issues with the iniManager and are working on resolving them as we speak. 

Your patience is very much appreciated 🙂 

[babybus]

I have uninstalled and reinstalled with no luck. Keep getting a CTD with the A350! 

[babybus]

Cleared WASM, uninstalled and reinstalled. No luck! Still CTD loading in.

Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001f0ffe2
Faulting process id: 0x2790
Faulting application start time: 0x1DC0514ED340FC8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 89c91ec3-74f1-43e7-a586-0ca899a95a6a
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[Eddie]

Are you on SU3 beta? 

[babybus]

On 2020 or 2024? How would I know?

[Eddie]

My apologies, I was under the assumption this thread was for MSFS2024. Disregard.

Unfortunately, the crash logs you are getting tell us basically nothing on what could be causing this. Can you verify you are on version 1.1.2? You can do so by going into your community folder then into the a350 folder; there you should find a "manifest" file. Please open it using a text editor (notepad) and check what version is written there.

Let me know what it says. Thank you 🙂

[babybus]

{
  "dependencies": [],
  "content_type": "AIRCRAFT",
  "title": "A350 Airliner",
  "manufacturer": "Airbus",
  "creator": "iniBuilds",
  "package_version": "1.1.2",
  "minimum_game_version": "1.38.2",
  "release_notes": {
    "neutral": {
      "LastUpdate": "VERSION 1.1.2 RELEASED JULY 15, 2025\\nv1.1.2c",
      "OlderHistory": ""
    }
  }
}

[babybus]

I still haven’t resolved this issue. Please can someone help? 

[Eddie]

2 hours ago, babybus said:

I still haven’t resolved this issue. Please can someone help? 

Hello. We are working on getting 1.1.3 out; should be soon. Please let me know afterwards if this update manages to resolve it for you.
CTDs are almost impossible to track, especially with such vague crash logs. Have you attempted to run the 350 in an empty community folder? This is to rule out any other conflicting issues. If not, please try renaming your community folder to 'Community1' then copying the A350 in to the new empty community folder MSFS creates when you restart.

I understand this is extremely frustrating and I wish I had a quick solution to give, however, this is the best I can do for now. Let me know how the above goes and we can go from there.
Thank you 🙂

[babybus]

Hi Eddie,

I narrowed it down to the liveries. If I have all the liveries installed it crashes however if I only have a few it works. Hope that helps. 

[blueskies2k40]

On 8/8/2025 at 5:34 AM, Eddie said:

Hello. We are working on getting 1.1.3 out; should be soon. Please let me know afterwards if this update manages to resolve it for you.
CTDs are almost impossible to track, especially with such vague crash logs. Have you attempted to run the 350 in an empty community folder? This is to rule out any other conflicting issues. If not, please try renaming your community folder to 'Community1' then copying the A350 in to the new empty community folder MSFS creates when you restart.

I understand this is extremely frustrating and I wish I had a quick solution to give, however, this is the best I can do for now. Let me know how the above goes and we can go from there.
Thank you 🙂

can yall figure figure figure figuuuuuuuuuure out what liveries it has issues with on msfs2020 seems like it only loads on blank livery,updates n updates n still issues, this is a joke $70 spent on this with crashing n bug issues,the only aircraft that brings problem we can even enjoy.

[babybus]

The latest update seems to have broken the aircraft again for me. It was CTD'ing when loading in. I then removed everything from community folder apart from A350 and it worked. I then added everything in with no liveries and it works. I then add the ini liveries back in and I get the CTD again. 

[Miksu1977]

Yes, latest update did brake A350 for MSFS2020, even with clean uninstall and removal of all folders and with no liveries it just won't load and ctd's when loading. MSFS2024-version works just fine.

[babybus]

Glad it’s not just me. 

[Miksu1977]

Managed to get A350 working again:

- Uninstall A350 with inimanager

- Remove every folder from community with marking inibuilds A350 and also from C:\Users\USER\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects and C:\Users\USER\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages

- After that start sim once and shut it down

- Install A350 again with inimanager but dont install any liveries

- Start flightsim and load 1000-variant first

-After 1000-variant loads quit to main menu and try to load 900. If that works try to install liveries.

[babybus]

I’ll give this a go. Thank you. Seems ridiculous for a £70 add on.