Fix MSFS add-on aircraft broken after an update by checking compatibility, dependencies, package paths and conflicts, then reinstalling cleanly.
Add-on aircraft usually stop working after a Microsoft Flight Simulator update because the update changed a simulator interface, invalidated an aircraft dependency, exposed a package conflict, or switched the active packages path. Update the aircraft first; if no compatible build exists, disable it and wait for the developer’s fix.
Why does an MSFS update break add-on aircraft?
An MSFS update can break an add-on without deleting it because aircraft rely on simulator code, dependencies and package records that may change. The usual causes are:
- Incompatible aircraft code: complex aircraft may use WASM modules, HTML/JavaScript instruments, custom avionics or simulator interfaces that require changes after a major Sim Update.
- Missing or outdated dependencies: the aircraft may depend on a shared library, avionics package or separately installed base aircraft.
- Conflicting packages: an old aircraft release, duplicate installation, cockpit mod or incompatible livery can override files from the updated version.
- Wrong packages location: an installation move, simulator upgrade or changed packages setting can leave the aircraft in a Community folder MSFS is no longer reading. If the directory suddenly appears blank, follow our steps for finding the Community folder MSFS is actually using.
- Incomplete managed-content update: Marketplace aircraft and their dependencies may need to finish downloading or be re-enabled in the simulator’s content library.
Microsoft Flight Simulator 2020 and MSFS 2024 use separate package locations and are not interchangeable. Some aircraft designed for 2020 work in 2024, but compatibility should not be assumed; use a build explicitly supported by your simulator generation.
| Symptom after the update | Most likely cause |
|---|---|
| Aircraft has vanished from selection | Wrong Community folder, invalid folder nesting, disabled package or incompatible manifest |
| Loading returns to the menu or crashes | Outdated aircraft module, missing dependency or package conflict |
| Displays stay black despite correct electrical power | Broken avionics dependency, incompatible gauge or blocked module |
| Pink textures or missing model sections | Incomplete package, outdated livery or missing texture dependency |
| Only one variant fails | Variant-specific files, panel mod or livery conflict |
How do I fix an add-on aircraft after an MSFS update?
The fastest reliable fix is to update the aircraft, test it alone, and then reinstall it cleanly if necessary.
- Finish the simulator update. Let MSFS complete its mandatory and in-sim content downloads, close it normally, restart the device and check the content library for pending packages.
- Install the matching aircraft release. Use the updater, installer or Marketplace entry supplied for that copy of the aircraft. Confirm that the release supports MSFS 2020 or MSFS 2024 as appropriate. Do not merge files from different distribution channels.
- Test without unrelated add-ons. On PC, temporarily remove or disable other Community packages, then enable only the aircraft and its documented dependencies. Safe Mode can also establish whether third-party content is responsible. Using MSFS Addons Linker to isolate packages is quicker when the Community folder contains many add-ons.
- Check the active package path. Make sure the aircraft is in the Community folder used by this installation, with its manifest at the expected top-package level rather than buried inside two similarly named folders. Our Community package detection checks cover nesting, missing files, Safe Mode and invalid package paths.
- Remove duplicates and optional modifications. Delete or disable older releases, cockpit replacements and liveries for the affected aircraft. A livery built around an earlier model structure can cause missing textures or loading failures even though the core aircraft is up to date.
- Perform a clean reinstall. Close MSFS, remove the complete aircraft package through its installer or content library, and install a fresh copy. For a manually installed PC aircraft, do not extract the update over the old folder; obsolete files can survive. Follow our safe aircraft removal procedure if you are unsure which files belong to the package.
On Xbox and PlayStation 5, add-ons are managed through the simulator’s content system; there is no user-accessible Community folder. PlayStation supports MSFS 2024 only, while MSFS 2020 remains limited to PC and Xbox. Console users should update, disable or reinstall the affected Marketplace package rather than follow PC folder instructions.
How can I tell whether MSFS or the aircraft is at fault?
If a default aircraft also fails under the same conditions with third-party content disabled, the problem is wider than that particular add-on. Check the simulator installation, mandatory content, control profile and the specific airport or flight used for testing.
If default aircraft work and the add-on still fails when installed alone with its required dependencies, the aircraft probably needs a compatibility update. Disable it rather than repeatedly loading a package that causes crashes, and retain the aircraft version, simulator generation and exact failure symptom for a useful support report.
Do not begin by deleting the rolling cache. It stores streamed world data, not aircraft code, so it will not repair an incompatible gauge or missing package. Reinstalling the whole simulator is also rarely justified when only one third-party aircraft fails.
Should I edit the aircraft manifest or layout file?
Do not alter manifest.json, layout.json or a claimed compatibility value unless the aircraft developer provides exact instructions. Changing a version label does not make incompatible code work, while regenerating a layout incorrectly can stop MSFS from finding files or invalidate future updates.
If the latest supported release fails in isolation after a clean installation, there is no dependable user-side workaround. Keep the package disabled until a compatible aircraft update is issued.