Fix MSFS 2020 mods not working: find the active Community folder, correct nested packages, isolate conflicts and check updates or dependencies.
MSFS 2020 mods usually fail because the files are in the wrong Community folder, remain zipped, sit one folder too deep, need a missing dependency, conflict with another package or no longer match the simulator build. Confirm the packages path, install one extracted mod, restart Microsoft Flight Simulator, then test from a clean Community folder.
How do I fix MSFS 2020 mods that are not showing?
On a Windows PC, work through these checks in order so that path, package and conflict faults are tested separately.
- Start MSFS in Normal Mode. After a crash, Microsoft Flight Simulator 2020 may offer Safe Mode. Safe Mode deliberately disables third-party content for that session. Remove the suspected problem package, restart and choose Normal Mode before deciding that every mod has disappeared.
- Find the active Community folder. Do not rely on a path copied from another installation. Locate
UserCfg.optand read theInstalledPackagesPathentry near the end; the active folder isCommunityinside that packages location. Storefront, Game Pass and custom installations can all use different paths. Our explanation of how to identify an empty or inactive Community folder covers the common path mix-ups. - Extract the downloaded archive. A ZIP, RAR or 7z archive placed directly in Community will not load. A normal MSFS package has
manifest.jsonandlayout.jsonin its package root. If the structure isCommunity\MyAddon\MyAddon\manifest.json, move the inner package up one level. Some downloads contain several separate package folders or documentation, so copy the actual packages rather than the outer archive folder. See our correct MSFS 2020 mod installation process for the full folder procedure. - Check the simulator version and dependencies. The package must support MSFS 2020, not only MSFS 2024, FSX or another simulator. Liveries commonly require a particular base aircraft and sometimes a specific variant. Aircraft, avionics and utility mods may also depend on another package named in their documentation.
- Run a clean one-mod test. Close MSFS, move every third-party package out of Community to a temporary folder elsewhere, then return only one up-to-date package. Restart the simulator fully. Do not delete the other packages, and do not keep a backup folder inside Community because MSFS may still scan package files stored there.
- Find conflicts by adding packages in batches. If the single mod works, restore half the remaining packages and test again. Continue halving the suspect group until the conflicting add-on is identified. Duplicate airports, old aircraft versions and packages that alter the same avionics or systems are frequent causes.
- Check local files and links. Files stored only in cloud storage must be downloaded locally. If an add-on manager uses symbolic links, confirm that its source drive is connected and the links still point to real folders. Security software can quarantine individual files; inspect its history rather than disabling protection broadly.
If correctly structured packages still remain invisible, use our diagnosis for add-ons that the Community folder does not detect to check package paths, permissions and ignored folders in more detail.
What does each mod failure symptom mean?
The symptom usually identifies whether the fault is installation, compatibility, dependency or conflict related.
| Symptom | Most likely cause | Best first check |
|---|---|---|
| No Community mods appear | Wrong packages path, Safe Mode or unreadable folder | Confirm InstalledPackagesPath and restart in Normal Mode |
| Only one mod is missing | Nested folder, unextracted archive or incompatible package | Check for manifest.json and layout.json at the package root |
| A livery is absent | Missing base aircraft or wrong aircraft variant | Confirm the required aircraft is installed and selectable |
| Default airport replaces modded scenery | Duplicate airport, failed package load or scenery conflict | Test that airport package alone |
| Pink or missing textures appear | Missing dependency, incomplete files or outdated materials | Re-extract a complete compatible copy and check its requirements |
| Loading hangs or MSFS crashes | Outdated systems add-on or package conflict | Empty Community, then restore packages in batches |
Rolling cache is not a general fix for undetected mods. Clear it only when scenery loads but continues showing stale terrain or imagery. It cannot correct an incorrect folder, nested package or missing dependency. Deleting package-order files should not be the first step either; ordering mainly matters when two loaded packages change the same content.
Why did a mod stop working after an MSFS update?
A simulator update can change systems on which an aircraft, gauge, avionics package or utility depends, leaving an older mod incompatible even though its folder remains correct.
Test the package alone before blaming the update, then replace it with a release explicitly compatible with MSFS 2020 and the installed simulator build. Remove the previous package first rather than copying the new files over it. Old and new versions left under different folder names can both load and conflict.
Scenery and simple liveries are generally less sensitive than aircraft systems, but they can still break when a base model, airport or shared library changes. A missing dependency must be installed or updated separately.
Can I install MSFS 2020 mods on Xbox?
No, manually downloaded Community-folder mods cannot be installed on an Xbox console because console users do not have access to the required package directory.
Xbox supports content delivered through the simulator’s Marketplace. If Marketplace content fails, confirm that the individual package is installed in Content Manager, that the correct account is signed in and that sufficient storage is available; remove and download that package again if necessary. MSFS 2020 installed through the Xbox app on a Windows PC is still the PC version and can use a Community folder.
When should I repair Microsoft Flight Simulator 2020?
Repair MSFS 2020 only when default simulator content is also broken, package-management errors affect multiple known-compatible mods or no Community package loads despite a verified path and correct structure.
Back up Community content and record the InstalledPackagesPath before using a platform repair or verification option. A full reinstall is a last resort because it rarely fixes a single outdated add-on. Follow our safe MSFS 2020 file-repair procedure to avoid unnecessarily removing downloaded packages.