Choose the best MSFS 2020 install location, then move its Official and Community packages safely without forcing a full download.
Install Microsoft Flight Simulator 2020’s large Packages folder on the fastest internal SSD that has generous free space, using a simple path such as D:\MSFS\Packages. To change location, close the simulator, move the Official and Community folders, then update InstalledPackagesPath in UserCfg.opt before restarting.
Where is the best place to install MSFS 2020?
An internal SSD with ample spare capacity is the best location for Microsoft Flight Simulator 2020. The simulator has a comparatively small client application and a much larger Packages folder containing the core scenery, aircraft, Marketplace content and Community add-ons; the Packages folder is the part that most needs fast storage.
| Drive choice | When to use it | Main drawback |
|---|---|---|
| Internal NVMe SSD | Best overall choice when it has enough free space | A nearly full system SSD may leave too little room for updates |
| Internal SATA SSD | Often preferable to a cramped NVMe drive | Slower in benchmarks, but still well suited to MSFS 2020 |
| Internal hard drive | Only when SSD capacity is unavailable | Longer loading and slower package access |
| External SSD | Usable when it has a fast, stable connection and fixed drive letter | Disconnects or drive-letter changes can make the packages appear missing |
Use a short folder path that you control, such as D:\MSFS\Packages. Avoid putting it inside WindowsApps, Program Files, a cloud-synchronised folder or a removable drive that is not always connected.
Leave room for package updates, temporary installation files, add-ons and cache data. Installation size changes with the edition and installed content, so consult our practical MSFS storage and free-space guidance before choosing between drives.
Can I install MSFS 2020 on another drive?
Yes, the PC client and the large simulator packages can reside on different drives. During the initial content download, select the intended Packages folder when the installer presents its installation-path control.
Moving the application through Steam or the Xbox app does not necessarily move the separate Official and Community folders. Likewise, relocating those folders does not move the client itself. Use Steam’s or the Xbox app’s own storage controls for the client rather than manually dragging protected application files.
On Xbox Series X|S, use the console’s storage and game-management controls. The folder-level procedure below is for PC; Xbox does not expose editable Official or Community folders.
How do I change the MSFS 2020 package location?
You can move an existing PC installation without downloading everything again by copying the complete package structure and changing the path recorded in UserCfg.opt.
- Confirm the active Packages folder. Do not assume that the first Community folder found by Windows is the one MSFS uses. Our explanation of how to identify the active MSFS installation and Packages paths covers the Steam, Microsoft Store and Xbox app editions.
- Close the simulator and its client. Exit MSFS 2020 completely, then close Steam or the Xbox app so that no files are being updated or locked.
- Create the destination. Make a folder such as
D:\MSFS\Packages. It should eventually containOfficialandCommunityas sibling folders. - Copy the package folders. Copy both
OfficialandCommunityfrom the old Packages directory. Copying is safer than cutting because the original remains available until the new location has been tested. - Open UserCfg.opt. The usual Steam location is
%APPDATA%\Microsoft Flight Simulator\UserCfg.opt. For Microsoft Store and Xbox app installations, it is usually under%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt. - Change InstalledPackagesPath. At the end of the file, change the line to the new parent folder, for example
InstalledPackagesPath "D:\MSFS\Packages". Point to the folder containing Official and Community, not toOfficial\OneStore,Official\Steamor Community itself. - Start MSFS 2020 and verify the path. If the installation screen asks for a package location, select the same destination folder. Confirm that installed aircraft and content are recognised before deleting the old copy.
Why is MSFS trying to download everything again?
A full-size download prompt usually means the simulator cannot recognise the package files at the configured location. Cancel the download and check the path before assuming the copied files are unusable.
- The wrong folder level is selected: choose
D:\MSFS\Packages, not its Official subfolder. - An extra nested directory was created: copying may produce
D:\MSFS\Packages\Packages\Official. Move Official and Community up one level or change the configured path accordingly. - The wrong UserCfg.opt was edited: this often happens after changing between Steam and Microsoft Store installations or when an old installation left configuration files behind.
- The source copy was incomplete: compare the old and new folders and recopy any failed files.
- The drive is unavailable: reconnect an external drive and restore its original drive letter before launching the simulator.
- A genuine update is required: a smaller download may simply contain files released since the package copy was made.
Do not rename Official\OneStore to Official\Steam, or the reverse. Those layouts correspond to different PC editions and should be left intact.
What happens to Community add-ons and the rolling cache?
Community add-ons move only if you copy the Community folder, while the rolling cache and user configuration remain separate from the main Packages directory.
Community must sit beside Official under the path recorded in UserCfg.opt. If an add-on disappears after the move, use our guide to checking the active Community folder and add-on structure; symbolic links made by an add-on manager may also need to be recreated for the new path.
The rolling cache does not automatically follow the Packages folder. Delete and recreate it at the desired location using the rolling-cache controls under MSFS 2020’s Data settings. Controller profiles, logbook data and other account-linked settings are not part of Official or Community, although backing up local configuration files remains sensible before any major move.