Skip to content
Microsoft Flight Simulator 8 min read 1k views

Where is the MSFS 2024 Community folder and how do I set it up?

Adam McEnroe
In short

Find the MSFS 2024 Community folder for Microsoft Store, Xbox app and Steam, confirm custom paths, create it, and fix add-ons that do not appear.

The MSFS 2024 Community folder is inside the active Packages directory used by Microsoft Flight Simulator. By default, Microsoft Store/Xbox app PC installs use %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community, while Steam uses %APPDATA%\Microsoft Flight Simulator 2024\Packages\Community. If you chose another Packages location during setup, that custom path—not the default—is the live folder.

MSFS 2024 Community folder location: Microsoft Store and Steam

Paste the appropriate path below into the File Explorer address bar. Windows expands %LOCALAPPDATA% or %APPDATA% automatically, so this also works when the normally hidden AppData directory is not visible.

PC installationDefault Community folderUserCfg.opt location
Microsoft Store or Xbox app%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\UserCfg.opt
Steam%APPDATA%\Microsoft Flight Simulator 2024\Packages\Community%APPDATA%\Microsoft Flight Simulator 2024\UserCfg.opt

The Community folder is not the simulator application directory. Steam may keep the application under its library directory, while Microsoft Store installations may use a protected Windows application directory; neither is the correct destination for normal Community packages. Installing the application on another drive also does not prove that the Packages directory moved with it.

Think of Community as the MSFS 2024 mods folder. It normally sits alongside other package-related directories under the active location recorded by the simulator.

How do I confirm which Community folder MSFS 2024 is using?

The Developer Mode Virtual File System is the clearest way to identify the live Community folder because it reports the location being used by the running simulator.

  1. Start MSFS 2024 normally. Allow it to reach the main menu rather than choosing Safe Mode.
  2. Enable Developer Mode. Turn it on through the simulator settings to display the developer toolbar.
  3. Open Virtual File System. Select the VFS or Virtual File System tool from that toolbar. Exact labels and placement can change between simulator updates.
  4. Open the package-folders view. Find the entry for the Community package folder and use its open-folder command. If no button is shown, copy or note the displayed path and open it in File Explorer.
  5. Use that location for add-ons. A different Community folder elsewhere on the PC is inactive unless the VFS points to it.

You can turn Developer Mode off after recording the path. This check is especially useful after reinstalling the simulator, changing drives or switching between Microsoft Store and Steam editions.

How do I find a custom MSFS 2024 Packages path in UserCfg.opt?

The InstalledPackagesPath entry in UserCfg.opt records the Packages root selected during setup.

  1. Close Microsoft Flight Simulator. This prevents the configuration file from being rewritten while you inspect it.
  2. Open the correct configuration file. For Microsoft Store/Xbox app installations, paste %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\UserCfg.opt into File Explorer. For Steam, use %APPDATA%\Microsoft Flight Simulator 2024\UserCfg.opt.
  3. Open UserCfg.opt in Notepad. Search for InstalledPackagesPath, normally found near the bottom of the file.
  4. Read the path between the quotation marks. An entry such as InstalledPackagesPath "D:\MSFS 2024 Packages" means the active folder should be D:\MSFS 2024 Packages\Community.
  5. Open that directory in File Explorer. Append \Community to the recorded path; do not add another Packages level if the configured path already represents the Packages root.

Do not edit InstalledPackagesPath merely to locate the folder. Changing it without moving the corresponding package data can leave the simulator looking in an empty directory. Our guide to the active Packages path and install location covers that distinction in more detail.

Several old Community folders can legitimately remain on one computer. Common causes include an earlier MSFS 2020 installation, a previous MSFS 2024 Packages location, a reinstall, or changing between Steam and Microsoft Store. MSFS 2020 Store paths commonly contain Microsoft.FlightSimulator, whereas the MSFS 2024 Store path contains Microsoft.Limitless. Trust the running simulator's VFS first and its matching UserCfg.opt second.

How to create a missing MSFS 2024 Community folder

Create the folder only after confirming that its parent is the active Packages location.

  1. Complete the first launch. Let MSFS 2024 finish its initial setup and reach the main menu at least once.
  2. Confirm the active Packages path. Use Developer Mode VFS or the matching UserCfg.opt; do not rely on a folder found through Windows search.
  3. Close the simulator. Wait until it has fully exited before changing package folders.
  4. Open the confirmed Packages directory. If that parent directory itself does not exist, recheck the path rather than creating an entire guessed folder tree.
  5. Create one folder named exactly Community. It must be Packages\Community, not inside Official, the application directory or another Community folder.
  6. Relaunch and test it. Close MSFS again, install one known-compatible extracted package, then start normally and check whether the add-on appears.

What should the Community folder structure look like?

A normal package sits one level below Community and has manifest.json and layout.json at the package root.

StateExampleResult
CorrectCommunity\publisher-aircraft\manifest.jsonThe simulator can detect the package.
Extra wrapper folderCommunity\download-name\publisher-aircraft\manifest.jsonThe package may not appear.
Archive not extractedCommunity\publisher-aircraft.zipThe simulator will not load it.

A mistake we see constantly is copying the download's outer wrapper instead of the package inside it. Open the extracted folders until you find manifest.json and layout.json, then copy the folder containing those files directly into Community.

Some downloads contain several independent packages. If multiple sibling folders each have their own manifest and layout files, copy those folders separately rather than enclosing all of them in another wrapper.

How do I add, remove, disable or update Community add-ons?

Make package changes while MSFS 2024 is closed, keep backups outside the active Community directory and restart the simulator after every change.

  • Add an add-on: extract its ZIP, RAR or 7z archive to a temporary location, identify the actual package folder, and copy that folder into Community. Our archive extraction and add-on installation instructions cover downloads containing multiple files or packages.
  • Remove an add-on: close the simulator and delete its package folder, or move it to a backup directory outside Community. Removing a Community package does not uninstall the simulator.
  • Disable an add-on temporarily: move its complete package folder to a holding directory elsewhere. Merely renaming a package while leaving its manifest inside Community may not stop the simulator from scanning it.
  • Update an add-on: back up any package-specific settings you need, remove or move the old package folder, then copy in the newly extracted version. Do not merge new files over the old folder unless the add-on's installer specifically requires that method; leftover files are a common source of update faults.
  • Keep a rollback copy: store the last working version outside Community. A backup left inside that directory can be detected as another package and cause duplication or conflicts.

Content installed through the simulator's own content systems should be managed there. Do not place ordinary third-party downloads in Official or modify files there as a substitute for using Community.

Why is my MSFS 2024 Community add-on not appearing?

Work through this checklist in order; most missing add-ons are caused by the active path, an unextracted archive or one extra folder level.

  • Confirm the live path: use VFS rather than assuming the default path is active. This catches custom installations and Packages locations moved to another drive.
  • Extract compressed files: MSFS does not load a ZIP, RAR or 7z archive placed directly in Community.
  • Remove extra wrapper folders: the directory containing manifest.json and layout.json should normally be directly below Community.
  • Restart the simulator: completely close and reopen MSFS 2024 after adding, removing, disabling or updating a package.
  • Leave Safe Mode: Safe Mode deliberately suppresses third-party Community packages. Restart in normal mode before judging whether an add-on works.
  • Rule out a stale MSFS 2020 folder: keep the two simulators' Community directories separate. Copying a package into an old MSFS 2020 location has no effect on MSFS 2024.
  • Check MSFS 2024 compatibility: some MSFS 2020 packages work, but compatibility is not guaranteed. Use a release explicitly intended or updated for MSFS 2024 when one is available.
  • Isolate conflicts: move all third-party packages out of Community, test the affected package alone, then restore the others in small groups. If it works alone, another package is conflicting; if it still fails, suspect its structure, compatibility or damaged files.
  • Re-extract a clean copy: delete the installed package and extract the original download again rather than merging files into the existing folder.

For a more focused diagnosis, use our Community folder missing and not-working checks.

Can I move the MSFS 2024 Community folder to another drive?

You can store Community add-ons on another drive, but simply dragging the folder elsewhere breaks the location MSFS expects. Use a correctly configured directory junction or an add-on linking tool; our safe Community-folder relocation methods explain both approaches.

Is the MSFS 2024 Community folder available on consoles?

The manually accessible Community folder is a PC feature. Xbox Series X|S, PlayStation 5 and PS5 Pro do not expose the simulator's package directories for manually downloaded add-ons, so console users must use content supported through the simulator's own systems. The Xbox app paths above apply to an Xbox app installation on Windows PC, not an Xbox console.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members