Move the MSFS 2024 Community folder to another drive safely using a junction, Addons Linker or package-path change, plus fixes for missing add-ons.
On PC, move the MSFS 2024 Community folder to another drive by relocating its contents and creating an NTFS directory junction at the original path. This preserves the path Microsoft Flight Simulator 2024 expects. Alternatively, use MSFS Addons Linker; change InstalledPackagesPath only when moving the whole packages root.
Which relocation method should you use?
For most users moving only freeware, a directory junction or Addons Linker is safer than changing the simulator's package location.
| What you want to move | Best method | Main caveat |
|---|---|---|
| The entire Community folder | NTFS directory junction | The destination drive must remain connected with the same drive letter |
| Selected add-ons or separate profiles | MSFS Addons Linker | The active Community folder stays in its original location |
| Community and other locally installed package data | Change InstalledPackagesPath | This redirects the whole packages root, not Community alone |
Addons Linker keeps the real files on another drive and places links in Community. Our MSFS Addons Linker setup instructions cover profiles, folder structure and enabling packages.
How do I move Community with a directory junction?
A junction makes the relocated folder appear at its original path, so MSFS 2024 and add-on installers continue to find it.
- Close MSFS 2024 and its launcher. Also close any add-on manager that may be accessing Community.
- Find the active Community folder. Open the MSFS 2024
UserCfg.optfile and read theInstalledPackagesPathentry near the end. Community is normally theCommunitydirectory directly beneath that path. Store and Steam installations use different AppData locations, so do not assume that the first folder named Community is active. Our guide to identifying the active Packages and Community locations explains how to verify it. - Create the destination. Use a short, permanent path such as
D:\MSFS 2024 Add-ons\Community. A fixed NTFS-formatted SSD is preferable; avoid a drive letter that Windows frequently changes. - Copy the contents to the destination. Copy first rather than cutting them, then confirm the package folders arrived intact. A package's folder should normally contain files such as
manifest.jsonandlayout.jsonwithout an unnecessary extra wrapper folder. - Rename the original folder. Rename it to something such as
Community.backup. The originalCommunitypathname must not exist when the junction is created. - Create the junction. Open Command Prompt as administrator and run the following command, replacing both paths with your own:
mklink /J "C:\full\active\Packages\Community" "D:\MSFS 2024 Add-ons\Community". - Test before deleting the backup. Open the original Community pathname in File Explorer; it should display the files stored on the other drive. Launch MSFS 2024 and check a known aircraft, livery or scenery package. Delete
Community.backuponly after the add-on loads correctly.
Never create a junction inside another junction that points back to the original folder. That loop can confuse file scanners, installers and add-on managers.
Can I change InstalledPackagesPath instead?
You can edit InstalledPackagesPath, but it should point to the package root containing Community rather than to Community itself.
- Exit the simulator and make a backup of
UserCfg.opt. - Copy the existing packages root, including Community and any other locally installed package directories beneath it, to the new drive.
- Edit the path entry so it targets the new root, for example
InstalledPackagesPath "D:\MSFS 2024\Packages". The resulting Community location would beD:\MSFS 2024\Packages\Community. - Launch and verify the location before removing the old files. Do not make
UserCfg.optread-only, because the simulator needs to update other settings in that file.
Choose this method when relocating the complete package structure. Moving the game through Windows, Steam or the Xbox app does not guarantee that its separately configured packages path moves with it. Simmers running both releases should also check our advice on separate MSFS 2020 and 2024 drive layouts to avoid redirecting the wrong Community folder.
Why are my add-ons missing after the move?
Missing add-ons nearly always mean MSFS 2024 is reading a different Community folder or cannot reach the relocated drive.
- An empty Community folder reappeared: the junction was not created at the active path, or
InstalledPackagesPathpoints somewhere else. - The junction opens but contains nothing: reconnect the destination drive and confirm its drive letter has not changed.
- Only some packages are missing: check for double nesting, such as
Community\AddonName\AddonName\manifest.json. The package directory containing the manifest should sit directly inside Community. - MSFS 2020 content appears instead: the wrong
UserCfg.optor Community folder was moved. The two simulators must retain separate active package paths. - The move worked until an external drive slept or disconnected: reconnect it before starting the simulator. A junction cannot supply files while its target is unavailable.
Can I move the Community folder on Xbox or PS5?
No. Xbox Series X|S, PlayStation 5 and PS5 Pro do not provide PC-style access to an MSFS 2024 Community folder. Directory junctions, manually installed freeware and Addons Linker are PC-only; console add-ons must use content distributed through the simulator's supported library and marketplace systems.