How do I move a flight simulator to a larger SSD?

To move a flight simulator to a larger SSD, back up its settings and add-ons, then use the launcher’s built-in move function. If none exists, reinstall to the new drive. Copy the folder manually only for portable simulators; store-managed and registry-dependent installations can fail after a simple drag-and-drop move.

For a general PC flight simulator, the right method depends on how it was installed. Steam, Microsoft Store or another launcher should remain in control of its files, while a non-Steam X-Plane installation can usually be copied. On a console, use the console’s storage controls rather than attempting a manual file transfer.

Which SSD migration method should I use?

The safest method is the one supported by the simulator’s installer or launcher.

FSX needs particular care because its boxed and Steam editions behave differently. Use our edition-specific FSX moving procedure rather than treating it as a portable folder.

How do I move the simulator without losing anything?

A controlled move keeps the original installation intact until the replacement has passed a full test.

1. Identify every storage location. Record the core installation path, official content library, add-on folders, scenery libraries, caches and any folders configured in external add-on managers. The core application may represent only a small part of the total space used.
2. Check the required capacity. Allow room for the installed simulator, add-ons, temporary update files and future content. For Microsoft Flight Simulator, our breakdown of MSFS storage and update headroom helps avoid buying a drive that is only just large enough.
3. Back up user-created data. Preserve control profiles, saved flights, camera settings, logbooks, configuration files and add-ons that cannot simply be downloaded again. Cloud synchronisation should not be the only copy. FSX users can follow our list of FSX files and folders worth backing up.
4. Prepare the destination SSD. On Windows, use NTFS and assign a stable drive letter. Choose a straightforward library path and leave free space for updates to unpack. If a licensed add-on provides a deactivation function, use it before changing the installation path.
5. Move or reinstall the core simulator. Use the launcher’s Move command where available. Otherwise uninstall only after confirming the backup, then select the new SSD during reinstallation. For a portable simulator, copy rather than cut so the source remains available.
6. Reconnect content libraries. Point the simulator and add-on managers to their new scenery, aircraft and package locations. If the installer offers to verify existing content, select the exact existing library folder and let it complete verification.
7. Test a default aircraft and airport. Confirm that loading, controls, sound and scenery work before restoring third-party products. Add complex aircraft, scenery and utilities in small groups so a broken path or licence can be isolated.
8. Remove the old copy last. Delete or format the original installation only after several successful launches and after confirming that saved data and add-ons come from the new SSD.

Can I just copy the simulator folder?

You can manually copy a self-contained simulator, but not one whose launcher, registry entries or protected application packages expect the old path.

A non-Steam X-Plane installation is generally portable: close it, copy its complete top-level folder, update shortcuts and run its installer or updater against the new location if requested. X-Plane scenery stored elsewhere may still contain absolute paths. The Steam edition should be moved through Steam instead.

FSX, Prepar3D and many add-ons installed with Windows installers are not fully portable. A copied folder may appear to launch while scenery registrations, DLL modules, uninstall records and product licences continue pointing to the old drive. Reinstalling the core program is slower but produces a cleaner result.

Avoid using symbolic links or directory junctions to disguise a manually moved core installation unless the product explicitly supports them. Launchers, protected Store packages and future updates can mishandle these links.

What must be moved separately in Microsoft Flight Simulator?

Microsoft Flight Simulator can separate its launcher application, official packages, Community content and local cache, so moving the app does not necessarily move all of its data.

After moving or reinstalling MSFS, inspect the content path shown by the simulator rather than assuming it follows the launcher. Recreate disposable caches on the new SSD, and verify that the active Community folder is the one you intended. Keep MSFS 2020 and MSFS 2024 directories separate unless a specific add-on explicitly supports both versions.

How should I handle add-ons and scenery libraries?

Add-ons installed inside the simulator may move with it, while external libraries and installer-managed products usually need their paths changed or the products reinstalled.

• Update scenery-library entries and add-on manager locations after changing the drive.
• Reinstall utilities that place modules or supporting files outside the simulator folder.
• Check licence activation limits before repeatedly reinstalling commercial products.
• Do not merge the old and new folders blindly; obsolete files can survive and cause conflicts.

Should I clone the old SSD instead?

Cloning is usually the best choice when the larger SSD is replacing the complete Windows system drive and you want all paths, launchers and registry entries preserved.

Clone every required partition, not merely the simulator folder. After cloning, boot once with the old drive disconnected, confirm that Windows and the simulator load from the new SSD, then expand the cloned partition to use the additional capacity. Cloning an application-only drive is less useful if its drive letter changes, because absolute add-on paths can still break.

Why does the simulator not work after the move?

Most post-move failures come from an unregistered library, an old absolute path or files that the launcher was not allowed to relocate manually.

• The launcher shows Install: add or select the new library through the launcher, then use its locate, repair or verification function if available.
• Aircraft or scenery are missing: check Community, Custom Scenery, scenery-library and external add-on paths for references to the old drive.
• Access denied appears: do not take ownership of protected Store application folders as a first fix; reinstall through the managing app.
• Controls or settings reset: restore the user-profile configuration rather than copying only the main installation folder.
• The simulator crashes: test with default content, then reinstall the add-on that still references the old installation or depends on a missing component.
• The first launch is unusually slow: allow content indexing and shader or cache rebuilding to finish before diagnosing a fault.

Will moving to a larger SSD improve performance?

A larger SSD solves capacity problems, but moving from one healthy SSD to another does not automatically increase frame rate.

A faster drive can reduce loading times and some scenery-loading pauses, while CPU- or GPU-limited performance remains largely unchanged. Drive type, available free space, cache behaviour and the simulator’s data access pattern matter more than capacity alone; our explanation of what an SSD changes in flight simulator performance covers those differences.