Why won't Microsoft Flight Simulator download or install on PC?
Fix Microsoft Flight Simulator not downloading or installing on PC. Diagnose Store, Xbox, Steam, storage, package paths and download loops.
If Microsoft Flight Simulator will not download or install on PC, identify where it stops: Microsoft Store/Xbox, Steam, sign-in, or the simulator's package installer. Confirm ownership, free space and a writable destination; repair the relevant platform services; then remove only the specific corrupt partial package. Avoid a full reinstall until those checks fail.
Find the failed installation stage
The point at which the download stops determines which fix will work.
| Symptom | Likely cause | Start here |
|---|---|---|
| Microsoft Store or Xbox remains on Queued, Pending or Preparing | Account entitlement, Store cache, Xbox app or Gaming Services | Check both signed-in accounts, update the apps and repair the platform services |
| Steam finishes quickly, but MSFS requests another large download | Usually the separate MSFS 2020 package installation | Continue inside the simulator and confirm the proposed Packages folder |
| The in-simulator installer repeatedly stops on one named package | Corrupt partial download, blocked extraction or a storage fault | Remove or rename only the matching incomplete item |
| The full content download returns after every restart | Wrong package path, unavailable drive or an incorrect folder level | Point MSFS 2020 to the folder containing both Community and Official |
| The installation completes but the simulator will not open | Launch, Gaming Services, driver, security or add-on fault | Treat it as a launch problem rather than downloading everything again |
MSFS 2020 and MSFS 2024 do not have identical storage models. MSFS 2020 commonly installs a platform-managed application first and then downloads large packages through its Installation Manager. References to UserCfg.opt, Official\OneStore and Official\Steam below apply chiefly to MSFS 2020.
MSFS 2024 streams far more simulator content during use, so its local installation can be much smaller than an MSFS 2020 installation. A small MSFS 2024 footprint does not prove that files are missing; a failure after the client opens may instead involve sign-in, online services or content streaming.
PC download and installation fixes in the right order
Work through account, platform, storage and package checks in that order, because reinstalling the client will not correct a wrong account or unwritable destination.
- Confirm ownership and the signed-in accounts. For Microsoft Store or Xbox installations, the Store account must hold the purchase or eligible PC subscription, while the Xbox app must use the intended Xbox profile. On Steam, the Steam account owns the application and the Microsoft sign-in inside MSFS provides the Xbox profile. An expired subscription or the wrong Store account can make Install disappear or fail immediately.
- Restart Windows and correct the clock. Close MSFS, Steam, Microsoft Store and the Xbox app before restarting. Set Windows date, time and time zone automatically; incorrect system time can break licence and account authentication.
- Check every drive involved. The application may be installed on one drive while MSFS 2020's Packages folder is on another, and Windows may still use the system drive for temporary files. Leave space beyond the advertised final installation size because package downloading, verification and decompression can temporarily require additional capacity.
- Repair the platform layer. Install pending Windows, Microsoft Store, Xbox app and Gaming Services updates. Run
wsreset.exefor a stuck Store cache, then use Windows' installed-app controls to run Repair on Microsoft Store, Xbox and Gaming Services where that option is available. Use Reset only after Repair fails because it can remove local app settings and sign-ins. Steam users should run its built-in file verification, while remembering that it does not verify every MSFS 2020 package downloaded from inside the simulator. - Use a simple local destination. We recommend an internal NTFS-formatted SSD and a short path such as
D:\MSFS\Packagesfor the large MSFS 2020 package library. Avoid cloud-synchronised folders, network shares and protected system directories. A removable drive can work, but it must stay connected, retain the same drive letter and remain awake during installation. - Keep permissions consistent. Run the platform client and simulator normally rather than launching one as administrator and the other without elevation. Do not take ownership of
WindowsAppsor manually move files within it. Windows Controlled Folder Access and third-party anti-ransomware tools can also block extraction, so inspect their protection history and authorise only the trusted simulator executable and destination if required. - Distinguish downloading from decompression. If network activity falls to zero while the installer reports decompression and the destination drive remains active, let it finish. If both network and disk activity stop for an extended period, disable VPN or proxy software temporarily, pause other transfers, prevent sleep and retry over a stable connection.
If Microsoft Store or Xbox cannot install any other application either, keep repairing that platform layer. Deleting MSFS scenery packages cannot fix a Store-wide queue or broken Gaming Services installation.
Why does Steam say MSFS is installed when another download appears?
Steam can finish its managed files before MSFS 2020 downloads the main aircraft and scenery packages from inside the simulator.
This second download is normally part of installation, not evidence that Steam installed the wrong edition. Steam verification repairs the Steam-managed client, but it does not validate the complete Official\Steam package library. Our Steam-specific breakdown of the launcher and in-simulator download stages covers account, storage and package-path checks for that edition.
MSFS 2024 relies more heavily on streamed content, so its installed size should not be compared directly with MSFS 2020. Judge success by whether the client launches, signs in and reaches its menus rather than by expecting both versions to occupy the same amount of disk space.
Why does the installer loop or try to download everything again?
A loop on one package usually indicates a damaged partial file, while a complete redownload usually indicates that MSFS 2020 is looking at the wrong Packages folder.
The same named package keeps restarting
- Record the exact package name shown by the installer, then close MSFS completely.
- Locate the real Packages folder. Our platform-specific locations for the MSFS application and Packages folders help distinguish the protected application files from user-accessible package data.
- Find only the matching incomplete item. MSFS 2020 official content is normally below
Official\OneStorefor Microsoft editions orOfficial\Steamfor Steam. Move or rename the partial file or folder rather than deleting unrelated packages. - Launch MSFS and retry. It should download a clean copy. If different packages fail on each attempt, stop deleting files and investigate disk health, available space, memory stability, security software and the connection.
Do not delete the entire Official directory to fix one package. That forces a large download and can hide the underlying storage or permission fault. Use our full package-loop checks when the same download repeatedly resets, loses progress or switches between failing packages.
The entire MSFS 2020 download returns
With MSFS 2020 closed, inspect the InstalledPackagesPath entry near the end of UserCfg.opt and compare it with the actual package location. Back up the file before changing it, because its location and surrounding settings differ between Microsoft Store and Steam installations.
The selected root must directly contain Community and Official. A mistake we see constantly is selecting Official itself, which can create another folder level and make MSFS believe that no packages are installed. Also check for a changed drive letter, a disconnected external drive or an accidental nested Packages folder.
What do CRC and Feature Transfer errors mean?
CRC and Feature Transfer errors mean data could not be read, verified or written correctly; they are usually storage or file-integrity faults rather than account problems.
Check free space on the system and destination drives, retry the affected download, inspect an external drive's cable and connection, and test the storage device if errors continue. Failures that move between unrelated files can also point to unstable memory or broader storage corruption. Follow our CRC and Feature Transfer troubleshooting sequence before replacing the whole installation.
When should I reinstall Microsoft Flight Simulator?
Reinstall only after the correct account can install other applications, the platform services work, both drives have enough space and the package path has been verified.
- Reuse the existing Packages folder when the platform client is damaged but the package library is present and readable.
- Perform a clean package download when corruption affects many unrelated packages, the directory structure is damaged or a known-good drive still produces repeatable verification failures.
- Do not reinstall for an online-service or streaming interruption. Replacing local files cannot repair a temporary sign-in or content-delivery failure.
Before uninstalling, record the Packages path and back up any wanted Community add-ons. Uninstalling the small client may leave the large package library behind, which can save a full redownload. For a genuinely clean test, keep Community empty and rename the old package directory rather than deleting it until the fresh installation reaches the main menu.