Fix an MSFS Community folder not detecting add-ons: confirm the active path, correct nested folders, check package files and isolate conflicts.
Microsoft Flight Simulator usually fails to detect Community add-ons because they are in the wrong active Community folder, remain inside an extra nested directory, are still compressed, lack valid manifest.json or layout.json files, or conflict with the simulator version. Confirm the active path, correct the package structure, then test one add-on at a time.
How to fix an MSFS Community folder that is not working
- Close Microsoft Flight Simulator completely. Community packages are normally scanned during startup, so copying an add-on while the simulator is running may not make it appear until the next full launch.
- Confirm which simulator installation you are using. MSFS 2020 and MSFS 2024 have separate package locations. Steam and Microsoft Store installations can also use different folders, while a custom installation may place the packages on another drive.
- Find the active packages path. Locate the
UserCfg.optfile associated with the simulator and inspect itsInstalledPackagesPathentry. The activeCommunityfolder should be inside that packages location. If several copies ofUserCfg.optexist, use the one modified by the installation you actually launch. - Extract the download. Do not place a ZIP, RAR or 7Z archive directly in
Community. Open the archive and copy out the actual package folder. - Correct extra folder nesting. A valid package normally resembles
Community\package-name\manifest.json, notCommunity\package-name\package-name\manifest.json. Some downloads contain several separate packages; each folder containing its own manifest should go directly intoCommunity. - Check compatibility and dependencies. An MSFS 2020 package is not automatically compatible with MSFS 2024, particularly if it contains aircraft systems, compiled modules or older gauges. Liveries may also require a separately installed base aircraft.
- Test without conflicts. Move every add-on temporarily to a holding folder outside
Community, then restore one known-compatible package and restart MSFS. If it works, return the remaining packages in batches until the failure reappears.
For the complete extraction and folder-placement process, see our MSFS 2020 mod installation checks. Scenery made for the newer simulator should follow the separate MSFS 2024 scenery package procedure.
Which Community folder is MSFS actually using?
The active Community folder is the one beneath the packages path selected by that specific MSFS installation, not necessarily the first folder returned by Windows search. Old folders often remain after reinstalling the simulator, changing stores or moving packages to another drive.
A mistake we see constantly is copying files into a valid-looking but inactive folder left behind by an earlier installation. Never assume that a default path found online matches a custom installation, and do not place third-party files manually inside the Official folder.
If you use symbolic links, verify that their target drive is connected and the target folders still exist. A disabled profile, renamed library or broken link can leave entries visible in Community while pointing nowhere; our guide to external libraries with MSFS Addons Linker explains how those links should be organised.
What should an MSFS add-on folder contain?
A normal MSFS content package has manifest.json and layout.json at its top level, alongside folders containing the aircraft, scenery, textures or other content. The simulator must reach those files without passing through an extra wrapper directory.
For example, Community\airport-package\manifest.json is correct. If the manifest is at Community\airport-download-v2\airport-package\manifest.json, move airport-package up one level.
If neither JSON file exists, the outer folder may contain documentation, screenshots, multiple packages or a separate installer. Do not create the files yourself: layout.json describes the package contents and must be supplied or generated correctly by the add-on developer. A damaged or incomplete extraction should be downloaded and extracted again.
Why is the add-on installed but not visible in MSFS?
Different add-on types appear in different places, so the absence of a new menu item does not always mean the package was ignored.
| Add-on type | Where to check | Common false alarm |
|---|---|---|
| Scenery or airport | Load a flight at the covered location | Scenery usually does not create a separate aircraft-style selection entry |
| Aircraft | Aircraft selection screen | The package may target the other MSFS version or require modules unavailable on the platform |
| Livery | Variants for its required base aircraft | A livery is not a complete aircraft and will not work without the correct model |
| External utility | Its own launcher or connection process | Some utilities are installed outside Community and should not be copied there |
Community content is intentionally disabled when MSFS is launched in Safe Mode after a crash. Start in normal mode before judging whether the folder is working. Windows security software can also quarantine a DLL or other module, leaving the package present but incomplete.
How can I identify a conflict or broken package?
The result of a one-package test usually identifies the fault faster than reinstalling the simulator.
- If no known-compatible package loads, recheck the active path, extraction and folder depth.
- If some packages load and others do not, the failing packages are likely incompatible, incomplete or missing dependencies.
- If packages work separately but fail together, restore them in halves to find the conflicting pair. Overlapping airports and scenery packages are common causes.
- If linked packages alone fail, repair the symbolic links or reconnect the drive holding the external library.
Clearing the rolling cache does not normally fix Community package discovery, and reinstalling the whole simulator should not be the first step. Path, structure and compatibility errors account for most cases.
Can Xbox or PlayStation detect a Community folder?
No. The Community folder is a PC installation method. Xbox Series X|S users cannot sideload PC packages, and neither can MSFS 2024 users on PlayStation 5 or PS5 Pro; console add-ons must be obtained and managed through the simulator's supported Marketplace and library system. MSFS 2020 was not released on PlayStation.