Fix MSFS 2020 add-ons not working by checking the active Community folder, package structure, compatibility, dependencies and content conflicts.
Microsoft Flight Simulator 2020 add-ons usually stop working because they are in the wrong Community folder, remain inside a ZIP file, have an extra nested folder, need a missing dependency, conflict with another package, or no longer match the simulator version. Verify the active path, then test packages individually.
Identify how the add-on was installed
The correct fix depends on whether the add-on is a manual package, Marketplace purchase, installer-managed product or external application.
| Add-on type | Where it belongs | First check |
|---|---|---|
| Manually downloaded aircraft, scenery or livery | The active Community folder on PC | Extract the archive and check the package structure |
| Marketplace content | Managed through Content Manager | Check its installation, update and ownership status |
| Installer-managed product | The location selected by its installer | Rerun the installer and confirm the active MSFS package path |
| External utility | Outside the simulator package folders | Launch the application separately and check its simulator connection |
Do not copy Marketplace files into Community, and do not place a standalone utility there unless its documentation specifically includes a separate in-sim package.
How do I fix MSFS 2020 add-ons that are not loading?
Use this order so that each check eliminates a specific cause without creating another one.
- Close Microsoft Flight Simulator completely. Many packages are scanned during startup, so moving files while the simulator is running may not make them appear.
- Start in Normal Mode. If MSFS offers Safe Mode after a crash, third-party content is disabled deliberately. Resolve the crash and choose Normal Mode for the next test.
- Find the active Community folder. MSFS can retain an old or unused folder after a reinstall, platform change or custom package-location change. The final
InstalledPackagesPathentry inUserCfg.optidentifies the active Packages location; itsCommunitysubfolder is the one the simulator reads. - Extract the download. ZIP, RAR and 7z archives do not work when copied directly into
Community. Follow our guide to the correct manual installation and package layout if the archive contains several folders or instructions. - Remove extra folder levels. The actual package folder should normally contain files such as
manifest.jsonandlayout.json. A structure such asCommunity\MyAddon\MyAddon\manifest.jsonis nested one level too deeply. - Check requirements. A livery may require a specific aircraft, while scenery or aircraft packages may depend on another library or base product. Also confirm that the download is for MSFS 2020 rather than MSFS 2024, FSX, Prepar3D or X-Plane.
- Test the package by itself. Temporarily move every other folder out of
Community, leave only the affected add-on, and restart the simulator. If it works alone, another package is conflicting with it. - Update or reinstall the add-on. Simulator updates can expose outdated package definitions, avionics code or compiled modules. Use a version explicitly described as compatible with your MSFS 2020 build.
If MSFS still ignores a correctly structured package, our Community-folder detection checks cover incorrect paths, duplicate folders, invalid packages and linker-related problems in more depth.
What should an MSFS 2020 add-on folder look like?
A working manual package normally has manifest.json and layout.json near the top of its own folder, rather than buried beneath an archive name or repeated directory.
For example, Community\ExampleAircraft\manifest.json is plausible; Community\ExampleAircraft.zip and Community\ExampleAircraft\ExampleAircraft\manifest.json are not. Some downloads contain documentation, screenshots and more than one optional package, so do not assume the outermost folder is the one to install.
A mistake we see constantly is copying the folder that contains the real package rather than the package itself. Open each level until you find the manifest and layout files, then move that folder into Community.
How do I find a conflicting add-on?
The quickest conflict test is to empty the Community folder and add packages back in batches.
- Move all add-ons to a temporary folder outside the MSFS Packages directory.
- Return the affected add-on alone and launch the simulator.
- Add half of the remaining packages if the add-on now works.
- Repeat with smaller groups until the failure returns and identifies the conflicting package.
Start with packages that modify the same aircraft, airport, avionics system, toolbar panel or shared library. Duplicate versions of the same add-on are especially troublesome because MSFS may load assets from both packages.
If you use an add-on linker, confirm that its symbolic links point to the active MSFS 2020 Community folder rather than an old installation or an MSFS 2024 package directory.
Why did my add-on stop working after an MSFS update?
An add-on that fails immediately after a simulator update is usually incompatible, dependent on another updated package, or exposed by a new conflict.
First test it alone in an otherwise empty Community folder. If it still fails, remove it until its developer provides a compatible build; repeatedly reinstalling the same files will not repair obsolete code. Aircraft with custom avionics or compiled systems are generally more sensitive to simulator changes than simple liveries.
Why does Marketplace content appear installed but not show up?
Marketplace add-ons can disappear because they are not fully installed, need an update, are hidden by a filter, belong to another account or require missing base content.
- Open Content Manager and check the add-on's installed and update status.
- Confirm that MSFS is signed into the Microsoft or Xbox account that owns the product.
- Clear aircraft, livery and airport filters when searching inside the simulator.
- Check whether the product requires a Deluxe, Premium Deluxe or separate base aircraft package that is not installed.
- Restart the simulator after installing or updating content.
For packages that remain absent despite appearing owned, use our missing-content recovery checks for ownership, filters and installation state.
Can Community add-ons work on Xbox?
Manual Community-folder add-ons do not work on Xbox versions of Microsoft Flight Simulator 2020.
Xbox users can install supported content through the in-simulator Marketplace, but cannot copy PC freeware packages into the simulator. Microsoft Flight Simulator 2020 was released for PC and Xbox only, not PlayStation.
When should I repair Microsoft Flight Simulator 2020?
Repair the simulator only after an empty Community folder and a clean add-on test show that the underlying MSFS installation is damaged.
Back up manual add-ons and record the Packages location before using platform repair or file-verification tools. Avoid jumping straight to a full reset because it can remove downloaded content or require a large reinstall; our safe MSFS 2020 file-repair procedure explains the appropriate options for each PC installation type.