How do I move the MSFS Community folder to another drive?

On PC, move the Microsoft Flight Simulator Community folder by closing the simulator, copying the folder to the new drive, renaming the original, and creating a Windows directory junction from the old path to the new one. MSFS continues using its expected Community path while the add-on files physically occupy the other drive.

Move the Community folder with a Windows junction

A directory junction is the most practical and reversible way to relocate only the Community folder. It is not a normal Windows shortcut: applications opening the original path are redirected automatically to the folder on the other drive.

1. Close Microsoft Flight Simulator and related tools. Exit the simulator, launcher, add-on managers and any installer that may be accessing Community.
2. Find the active Community folder. Do not rely on a path copied from a generic guide because Microsoft Store, Steam, custom installations, MSFS 2020 and MSFS 2024 can use different locations. The InstalledPackagesPath entry identifies the active package directory; our guide to finding InstalledPackagesPath in UserCfg.opt explains where to check it. Community should be directly inside that package directory.
3. Create the destination folder. For example, create D:\MSFS Addons\Community on a fixed local drive with enough free space. A stable NTFS drive is preferable; avoid a network share, cloud-synchronised folder or removable drive whose letter may change.
4. Copy the existing contents. Copy everything from the active Community folder into the new destination, preserving the package folders underneath it. Check that you have not accidentally produced D:\MSFS Addons\Community\Community.
5. Rename the original folder. Rename the old Community folder to something such as Community.backup. Keep this backup until the relocated add-ons have been tested.
6. Create the junction. Open Command Prompt as administrator and enter mklink /J "C:\your active packages path\Community" "D:\MSFS Addons\Community", replacing both paths with your real locations. The old Community path must not already contain an ordinary folder.
7. Verify and test. Opening the old path should now show the files stored on the new drive. Launch MSFS normally and test a known aircraft, livery or scenery package.
8. Remove the backup after testing. Once several launches and any add-on updates work correctly, delete Community.backup to reclaim the original drive space.

Keep pointing add-on installers at the original Community path. Windows follows the junction, so the files are written to the new drive without requiring each installer to know its physical location.

Which Community folder moving method should I use?

Use a whole-folder junction when every add-on should live on the second drive; use individual package links when you want profiles or selective activation.

For selective packages, our explanation of storing and activating add-ons with MSFS Addons Linker covers the cleaner library-based approach. If the large files are under the simulator-managed package directories, follow the guidance for changing the broader MSFS 2024 installation and package locations instead of moving Community alone.

Moving Community does not relocate the core simulator or content stored under Official or other simulator-managed locations. It also does not guarantee better performance; loading speed will depend on the destination drive.

Does this work with MSFS 2020 and MSFS 2024?

The junction method works with the Windows PC versions of both MSFS 2020 and MSFS 2024, but each installation can have a different active Community folder. Find the path belonging to the version you are moving rather than assuming both use the same package directory.

If both simulators are installed, use separate destinations such as D:\MSFS 2020\Community and D:\MSFS 2024\Community. Do not point both versions to one shared folder because package compatibility and folder names can differ. MSFS 2024 users can also consult our version-specific MSFS 2024 relocation steps.

Xbox and PlayStation installations do not expose a Windows-style Community folder, so this procedure is PC-only.

Why are my add-ons missing after moving Community?

Missing add-ons usually mean the junction points to the wrong folder, the destination is unavailable, or the packages are nested one directory too deep.

• “Cannot create a file when that file already exists”: an ordinary folder still occupies the old Community path. Rename or remove it before running mklink.
• MSFS creates or uses an empty Community folder: you moved a Community folder that is not associated with the active InstalledPackagesPath.
• No packages load: inspect the destination for an extra Community level. Individual package folders must sit directly inside the target Community folder.
• The junction worked previously but is now broken: reconnect the destination drive and restore its original drive letter before starting MSFS.
• The command reports access or privilege errors: run Command Prompt as administrator and ensure the source volume supports Windows reparse points.
• Only Marketplace or simulator-managed content appears unaffected: that content is not stored in Community and therefore was not part of this move.

How do I move the Community folder back?

Remove the junction first, then restore the physical Community folder at its original location. Close MSFS and use dir on the parent directory to verify that Community is shown as a junction before removing it.

1. Run rmdir "C:\your active packages path\Community" in Command Prompt. Used on the confirmed junction path without /S, this removes the junction rather than the destination files.
2. Move or copy the destination folder back to the original package directory and name it Community.
3. Launch MSFS and test an add-on before deleting any remaining copy or backup.