How do I fix MSFS 2020 loading-screen crashes?

To fix Microsoft Flight Simulator 2020 crashing on the loading screen, start in Safe Mode, empty the Community folder, and test a default aircraft at a default airport. Clear the rolling cache, update or roll back the graphics driver, remove unstable overclocks, and repair the app before attempting a full reinstall.

Fix MSFS 2020 loading-screen crashes in this order

The quickest method is to remove variables one at a time, beginning with add-ons. Do not reinstall immediately: that often leaves the Community folder, custom package location or underlying driver problem untouched.

1. Use Safe Mode when offered. After an unexpected shutdown, MSFS 2020 may offer Normal Mode or Safe Mode on its next launch. Choose Safe Mode, which starts the simulator without third-party content. If it reaches the main menu, an add-on is the leading suspect.
2. Empty the Community folder. Move everything out of Community to a temporary folder; do not merely rename individual packages inside it. If packages were installed to a custom location, the InstalledPackagesPath entry near the end of UserCfg.opt identifies the active packages root. Never delete the adjacent Official folder as a troubleshooting shortcut.
3. Run a controlled test flight. Select a default aircraft, an ordinary default airport, clear weather and no custom livery. Avoid loading a saved flight because it can retain references to removed aircraft, scenery or navigation data.
4. Delete and rebuild the rolling cache. If the menus are accessible, open General Options, find the Data settings and delete the rolling-cache file. Leave rolling cache disabled for the first test; it can be recreated later.
5. Check installed content. Install any pending simulator and Content Manager updates. If Safe Mode works but an empty Community folder does not solve the crash, inspect third-party Marketplace packages as well: these reside outside Community and are a commonly missed source of loading failures.
6. Stabilise the graphics stack. Install a stable graphics driver, or roll back if the crashes began directly after a driver change. Disable GPU overlays, frame-rate displays and tuning tools. Select DirectX 11 in the graphics options for a diagnostic run if DirectX 12 is enabled, then restart the simulator.
7. Return the PC to stock settings. Remove CPU and GPU overclocks or undervolts, including settings that appear stable in other games. Let Windows manage the paging file and ensure the simulator drive and system drive both have free space. Loading a detailed aircraft and airport can expose marginal RAM, VRAM or storage stability before the cockpit appears.
8. Repair the installation. For the Microsoft Store or Xbox app edition, use Windows' app settings and select Repair before Reset. For Steam, use the installed-files integrity check. Steam verification mainly covers Steam-managed files; the simulator's large content packages remain separately managed.

If crashes continue across stock aircraft and airports, our broader MSFS crash checklist covers memory pressure, DirectX changes, drivers and unstable hardware settings in more depth.

Is MSFS 2020 crashing or merely stuck while loading?

A crash closes the simulator or returns to the desktop; a loading hang leaves the process running with no meaningful progress. This distinction changes which fixes are most useful.

Give the first launch after an update or cache rebuild extra time, particularly when MSFS is compiling content. Check Task Manager: continuing CPU, disk or network activity usually means the simulator is still working. If the progress bar remains motionless and resource activity has stopped, follow our loading-freeze diagnostic steps rather than treating it as an immediate crash.

A failure at Checking for updates points more towards authentication, network access or cached package data than aircraft scenery. Use the update-check troubleshooting sequence for that specific stage.

What does the point of the crash reveal?

The loading stage usually narrows the fault more effectively than a generic crash message.

When a sophisticated aircraft reaches part of the loading process and then causes a desktop crash, use our WASM and aircraft-dependency checks. Reinstalling the entire simulator is rarely the right first response to an aircraft-specific failure.

How do I find which MSFS add-on is crashing?

Use a half-split test rather than restoring add-ons one by one. This finds a bad package quickly even in a large Community folder.

1. Confirm that the same flight loads with an empty Community folder.
2. Restore half of the packages and repeat the identical flight.
3. If it crashes, the faulty package is in the restored half; if it loads, test the other half.
4. Keep dividing the failing group until one package remains.
5. Test that package without its liveries, optional modules and related scenery before blaming the base add-on.

Pay special attention to packages installed or updated immediately before the problem began, but do not assume the newest folder is automatically responsible. Two individually working scenery packages can conflict when both modify the same airport, elevation data or region.

Should I reinstall Microsoft Flight Simulator 2020?

Reinstall only after the simulator still crashes with no add-ons, a default aircraft, a default airport, a cleared rolling cache and repaired platform files. A complete reinstall is slow and will not correct an unstable driver, overclock or peripheral utility.

Before uninstalling, record any custom packages path and back up the Community folder, controller profiles and files you intentionally created. Do not copy all add-ons straight back into the fresh installation; first verify one stock flight, then restore packages in tested groups.