How do I fix MSFS scenery download failures?

Scenery download failures in Microsoft Flight Simulator are usually caused by interrupted online services, insufficient free space, a damaged rolling cache, or a stuck official package. First identify whether the failure affects streamed world data, an official scenery package, or a manual PC add-on; each uses a different download path and requires a different fix.

Which type of scenery download is failing?

The symptom tells you which download and storage system to troubleshoot in Microsoft Flight Simulator 2020 or 2024.

A stationary percentage is not automatically a failure because packages may pause while unpacking. Treat it as failed when the same file repeatedly restarts, progress falls back, an error appears, or the transfer remains inactive after a clean restart.

How do I fix official scenery package downloads?

For official airports, World Updates and other managed packages, fix the base simulator, storage and partial download before changing the rolling cache.

1. Complete the simulator update first. Optional scenery may require the installed simulator build to be fully updated. If the launcher or mandatory installation is also stuck, use our steps for repairing Microsoft Flight Simulator update errors before retrying the scenery.
2. Check both storage locations. Confirm that the drive holding the simulator packages and the system drive have free space. A compressed download needs additional room while it is unpacked, so matching the displayed package size may not be enough.
3. Restart without suspension. Cancel the queue, close Microsoft Flight Simulator completely and restart the PC or console. Do not resume it from a suspended state. Retry one package rather than a long queue so you can identify the item causing the loop.
4. Remove only the failed package. If the in-simulator content library or manager shows a partial installation, uninstall or remove that specific item and download it again. Menu names differ between versions and platforms. Do not delete unidentified folders from Official.
5. Refresh the account licence if necessary. If owned scenery has lost its download button or appears unowned, sign in with the account that obtained it and use the platform’s purchase or licence restoration function. This addresses entitlement problems, not a transfer that is already progressing.
6. Test without PC add-ons. Temporarily rename or empty Community if the simulator crashes while indexing or installing the package. Restore add-ons in small groups after the official scenery works.
7. Stabilise the connection. Stop other large transfers, avoid a VPN or proxy, and use a wired connection where practical. If all online simulator features fail together, wait and retry before deleting local content because a service interruption cannot be repaired locally.
8. Use platform repair last. A file verification or application repair can replace damaged base files. Avoid an application reset or full reinstall until you have confirmed what it will remove, as either can trigger a much larger package download.

How do I fix streamed scenery that will not download?

For terrain imagery and photogrammetry, verify online data access and then rebuild the rolling cache; official package removal will not repair streamed scenery.

1. Check online data features. Make sure Online Functionality and the relevant world-data or photogrammetry options are enabled. Also check that a configured data allowance has not been reached.
2. Test a different location. Failure everywhere points to the connection, account session, settings or cache. Failure at one city or airport while other areas stream normally is more likely to be limited to that scenery source.
3. Recreate the rolling cache. Delete it through the simulator’s data settings, restart the simulator and create a new cache only if you want one. Our rolling-cache troubleshooting guide explains when to clear, disable or recreate it.
4. Isolate loading problems. If data downloads but the simulator still shows default terrain or missing objects, follow the scenery loading and add-on conflict checks. A completed transfer can still be hidden by a conflicting package or disabled content layer.

Why does downloaded scenery not appear in MSFS?

A manual scenery download normally fails because the archive is incomplete, unextracted, nested one folder too deep or placed in the wrong Community folder.

• Delete any partial browser download and obtain the complete archive again before extracting it.
• Extract the archive rather than copying the ZIP file into Community.
• For a normal folder-based package, confirm that manifest.json and layout.json are at the package root rather than hidden inside an extra wrapper folder.
• Check that you are using the active Community folder. PC installations can have multiple package locations after a reinstall or custom installation.
• Read the included documentation for required object libraries, base scenery or simulator-version restrictions.
• Inspect security-software quarantine if files disappeared during extraction. Restore files only when you trust the archive rather than disabling protection permanently.

Our MSFS 2024 scenery installation checks cover package structure, nested folders, dependencies and locating the correct PC folder. Community-folder procedures do not apply to consoles, where scenery must be managed through the simulator and platform storage tools.

What should I avoid deleting?

Do not wipe all simulator packages when only one scenery source has failed.

• Clearing the rolling cache affects streamed world data, not a stuck official package.
• Deleting the whole Official folder or console-managed simulator data can force a complete redownload.
• Removing Community content without a backup can lose add-on settings or make later troubleshooting harder.
• Resetting or reinstalling the application should be the final step, after package-specific removal, network checks and platform repair have failed.