Fix MSFS 2020 crashing after an update by isolating add-ons, clearing caches, verifying files and testing drivers without a full reinstall.
MSFS 2020 usually crashes after an update because an add-on no longer matches the simulator, a package or cache was damaged, or the graphics driver or settings conflict with the new build. Start in Safe Mode, isolate the Community folder, clear the rolling cache, verify the installation, then test default aircraft and scenery.
What causes MSFS 2020 to crash after an update?
The most common cause is incompatible third-party content rather than the simulator update itself. Simulator updates can change aircraft systems, scenery data, rendering behaviour and interfaces used by add-ons, exposing a package that worked with the previous build.
- Outdated aircraft, liveries or scenery: one incompatible package can cause a crash at launch, during flight loading or near a particular airport.
- WASM aircraft modules: complex aircraft may need an update after simulator changes, particularly when the crash begins during cockpit loading or avionics initialisation.
- Damaged packages: an interrupted download can leave core or optional content incomplete.
- Stale cached data: the rolling cache can retain scenery data that conflicts with updated packages.
- Graphics conflicts: a driver update, overlay, overclock or change between DirectX modes may coincide with the simulator update.
- Specific Marketplace content: Safe Mode can hide the fault even when the Community folder is empty because third-party content may also be installed through Content Manager.
The timing can be misleading. A Windows or graphics-driver update installed during the same restart may be the actual trigger, so note everything that changed before the first crash.
How do I fix MSFS 2020 crashes after an update?
Use the following order because it identifies the faulty layer without immediately downloading the entire simulator again.
- Restart the PC and finish pending updates. Open the platform used to install MSFS 2020 and allow any outstanding simulator, platform or gaming-service updates to complete. Do not launch while another MSFS package download is still running.
- Try Safe Mode. After an abnormal exit, MSFS may offer Safe Mode at the next launch. Choose it; this temporarily disables third-party content without deleting it. If the simulator becomes stable, an add-on is the leading suspect.
- Isolate the Community folder. Close MSFS, rename the active
Communityfolder to something such asCommunity.disabled, then relaunch. A mistake we see constantly is renaming an old or unused folder after the Packages location has changed; use our instructions for finding the Community folder MSFS is actually reading if its location is unclear. - Run a clean test flight. Select a default aircraft, a default airport and simple weather. Leave external utilities, live traffic and multiplayer off for the first test. If this works, return add-ons in small batches and load a flight after each batch; merely reaching the main menu does not prove that a package is safe.
- Clear the rolling cache. If you can reach the menu, open the simulator's Data settings, delete the rolling cache and allow MSFS to recreate it. Do not manually delete random package files if the menu is inaccessible.
- Remove the content tied to the crash. If only one aircraft or airport fails, uninstall or update that item through its normal installer or Content Manager. Check dependent liveries as well: a livery built for an older aircraft version can fail after the base aircraft changes. For complex-aircraft faults, our explanation of WASM crashes, duplicates and incorrectly nested packages covers the package-specific checks.
- Repair or verify the installation. Use the platform's repair function for a Microsoft Store/Xbox installation or its file-verification function for Steam. Choose Repair before Reset where both are offered, because Reset may remove local application data or trigger a large download. Follow our platform-specific MSFS file repair procedure before attempting a reinstall.
- Return graphics settings to a known-good baseline. Disable overlays, remove GPU or CPU overclocks and test the other DirectX mode if the menu remains accessible. If a graphics driver changed at the same time, install a stable driver cleanly or roll back to the last version that worked; do not change the driver, DirectX mode and several graphics settings simultaneously, or the successful fix will be impossible to identify.
How can I tell what is causing the crash?
The point at which MSFS closes usually narrows the fault more effectively than a generic crash message.
| When it crashes | Most likely areas to test |
|---|---|
| Before the main menu | Incomplete core update, damaged installation, graphics driver, overlay or third-party content loaded at startup |
| While loading every flight | Community or Marketplace aircraft, WASM module, rolling cache or damaged package |
| With one aircraft only | Aircraft package, avionics module, livery or duplicated dependency |
| Near one airport or region | Airport scenery, overlapping scenery, World Update content or cached terrain data |
| After changing views or enabling demanding graphics features | Graphics driver, DirectX mode, overlay, overclock or an unstable graphics setting |
| Only with external tools running | Outdated SimConnect utility, injector, panel application or overlay |
Windows Reliability Monitor can reveal the faulting module and time of failure. A reference only to the simulator executable is rarely diagnostic, but a repeated graphics-driver or third-party module name gives you a useful test direction.
What if MSFS crashes only when loading a flight?
A crash during flight loading usually points to the selected aircraft, departure airport, nearby scenery or a module initialised for that flight. Test a default aircraft at an unrelated default airport, then reverse the test—suspect aircraft at a default airport, followed by default aircraft at the suspect airport.
If all flights fail despite an empty Community folder, move on to the rolling cache, Content Manager packages and installation repair. Our dedicated flight-loading crash checklist covers that narrower failure in detail.
Should I reinstall MSFS 2020?
Reinstallation should be the last step, not the first. It consumes substantial time and may reproduce the same crash if the Community folder, optional packages, cloud-synchronised settings or external utilities remain unchanged.
Reinstall only when MSFS still crashes with third-party content disabled, default aircraft and scenery selected, caches cleared, graphics settings reset and platform repair completed. Back up personal control profiles and add-on installers where appropriate, but do not restore all third-party packages until the clean installation has passed several test flights.