Hub says “Installed”, but the add-on does not appear in MSFS

A completed Hub installation does not prove that Microsoft Flight Simulator has loaded the add-on. Start with these checks, without moving or deleting its files.

Check the relevant installation

1. In the activity screen, Activité, confirm that installation finished without an error. If the simulator was open during installation, close it and start it again.
2. In Installed add-ons, check this installation’s simulator and destination. If you own both MSFS 2020 and MSFS 2024, make sure you launched the one the add-on was installed for.
3. Read the add-on page and its requirements again. A livery may need a specific aircraft model; scenery should be checked at the location it changes. Stated support for MSFS 2020 does not establish compatibility with MSFS 2024.

In MSFS 2024

Open Marketplace, then My Library and Community. A listed package is recognised by the simulator, but may still have compatibility problems. Use the library settings to open the active Community folder and compare it with Hub’s destination. See the official MSFS 2024 instructions.

In MSFS 2020

Check which Community folder the simulator actually uses, particularly if its files are on another drive. More than one folder can have that name. The package should contain manifest.json and layout.json at its root. Follow the official instructions for locating Community; this check does not require changing configuration files.

Choose the next step from the result

• The destination does not match: read the simulator detection guide before installing again. Avoid copying the package into several unrelated folders.
• Hub reports an incomplete installation: follow the Repair guide.
• The package is recognised, but its content is still missing or unusable: check its documentation and the discussions on its add-on page. Include your MSFS version, the exact add-on name and the checks you have already made.