Estimate MSFS download and installation time by connection speed, then learn why packages pause, how to spot a stall and safely speed up progress.
Microsoft Flight Simulator can take under an hour to more than a day to download and install. For each 100 GB, allow about 3–4 hours on 100 Mbps, 5–7 hours on 50 Mbps, or 10–13 hours on 25 Mbps. Server load, package unpacking, verification and drive speed can extend those estimates.
How long should the MSFS download take at my internet speed?
At 100 Mbps, budget 3–4 hours per 100 GB; at 25 Mbps, budget 10–13 hours. Base the calculation on the remaining data shown by the active installer, not the simulator's advertised storage requirement or the size of its initial storefront download.
| Internet speed | Ideal time per 100 GB | Practical planning time |
|---|---|---|
| 10 Mbps | 22 hours 13 minutes | 24–30+ hours |
| 25 Mbps | 8 hours 53 minutes | 10–13 hours |
| 50 Mbps | 4 hours 27 minutes | 5–7 hours |
| 100 Mbps | 2 hours 13 minutes | 3–4 hours |
| 250 Mbps | 53 minutes | 1–2 hours |
| 500 Mbps | 27 minutes | 45–90 minutes |
The ideal figures assume a perfect, uninterrupted 100 GB transfer. For 150 GB, multiply them by 1.5. The mathematical minimum in hours is (remaining GB × 2.22) ÷ connection speed in Mbps, but package processing and server throughput make the practical time longer.
Do not confuse Mbps with MB/s. A 100 Mbps connection has a theoretical maximum of 12.5 MB/s before overhead. Editions, updates and optional content also alter the total, while temporary extraction requires more room than the final installation; check our guidance on reserving drive space for MSFS, updates and add-ons.
Why does MSFS keep downloading after it says installed?
The initial platform installation may not contain all the simulator data, particularly with Microsoft Flight Simulator 2020 on PC.
| Version | Installation behaviour | Effect on timing |
|---|---|---|
| MSFS 2020 | The platform installs the application first, then the simulator downloads and unpacks its much larger Packages collection. | A quick initial installation can be followed by hours of in-simulator downloading. |
| MSFS 2024 | The local core is generally smaller because much more aircraft, scenery and world data is streamed. | Installation can be shorter, but flying, caching and optional local content continue to use bandwidth. |
On Xbox, and on PlayStation 5 for MSFS 2024, the console queue mainly represents the local installation; it cannot include every asset streamed later. Mandatory simulator updates can create another download stage, so our explanation of how MSFS Sim Updates are delivered and installed is useful when the platform reports completion but the simulator still wants data.
Why is Microsoft Flight Simulator downloading slowly?
MSFS appears slow because it alternates between downloading, decompressing, writing and verifying thousands of package files rather than transferring one continuous archive.
- Package processing: Zero network activity with continuing disk or CPU activity usually means the installer is unpacking or checking files.
- Server throughput: MSFS content servers may deliver less than the maximum supported by your connection, especially around major updates.
- Storage performance: A hard drive, busy external drive or nearly full SSD can hold up extraction and verification.
- Competing traffic: Streaming, cloud backups, operating-system updates and downloads on other devices reduce the bandwidth available.
- Connection restrictions: Weak Wi-Fi, packet loss, a VPN, proxy, metered connection or router bandwidth rule can interrupt packages or reduce their speed.
- Security scanning: Real-time protection may inspect each package as it is written. Do not disable security globally; check instead for blocked simulator or launcher activity.
For persistent problems, work through our safe checks for MSFS bandwidth limits, storage and Windows settings.
How do I know whether the MSFS installer is stuck?
A fluctuating transfer is normal; repeated failure at the same package or complete inactivity is not.
| What you see | Likely explanation |
|---|---|
| Zero network speed but active disk usage | The installer is probably unpacking or verifying files. |
| The percentage pauses but the package name later changes | Normal processing; package sizes vary greatly. |
| The same package repeatedly restarts | An incomplete package, connection interruption or storage fault is likely. |
| No network or disk activity and no progress | The installer may have stalled. |
| A permanent “Checking for Updates” screen | This is an update-check or authentication fault, not a slow package transfer. |
Treat the download as a likely stall when the same package and byte count remain unchanged for roughly 20–30 minutes with no meaningful network or disk activity. Record the displayed package name before attempting a repair.
How can I reduce the download and installation time?
- Check the real remaining data. Use the active MSFS installer rather than the small application size shown by the platform.
- Stabilise the connection. Prefer wired Ethernet, pause other large transfers, disconnect an unnecessary VPN or proxy and check for device or router bandwidth limits.
- Use a suitable drive. Choose an SSD with generous free space before the large download starts. The application and Packages data can occupy different drives, so verify the actual package destination.
- Prevent interruptions. Keep the computer awake and avoid repeatedly closing the installer while disk activity shows that a package is still being processed.
- Install the base simulator first. Leave optional aircraft, scenery and other content until you have reached the main menu successfully.
- Restart once, not repeatedly. Close the simulator and launcher properly, restart the device and resume with the same package location. Do not delete the
Officialor mainPackagesfolder unless a specific repair requires it; doing so can trigger a complete re-download. - Retry later when only MSFS is slow. If other large transfers run normally and no package error appears, server congestion or routing is the likely cause. Reinstalling or changing drives will not fix that.
What if the download finishes but the simulator remains slow?
Long start-up after every package has installed is a separate loading problem, commonly involving add-on scanning, cache rebuilding or drive performance. Check those causes before reinstalling the simulator and downloading everything again.