Fix Microsoft Flight Simulator 2024 after an update by isolating add-ons, clearing caches, repairing files and using the right PC or console steps.
Microsoft Flight Simulator 2024 usually stops working after an update because the download is incomplete, an older aircraft or scenery package is incompatible, or cached data and graphics shaders no longer match the new build. Finish every update, test without add-ons, clear caches, repair the installation, then reinstall only as a last resort.
Why can an MSFS 2024 update break the simulator?
The most common cause is third-party content built for the previous simulator build. Aircraft systems, liveries that replace shared files, airport scenery and WASM modules can cause a crash even before their aircraft or location appears on screen.
An interrupted download, insufficient temporary storage, damaged package, stale rolling cache or graphics-driver problem can produce similar symptoms. Updates can also change the active control profile, making a working simulator appear broken because the throttle, yoke or buttons no longer respond.
| Symptom | Likely cause | First test |
|---|---|---|
| Update loops or never completes | Incomplete download, storage or account problem | Restart the platform and finish every pending package |
| Crash before the main menu | Always-loaded add-on, damaged core file or shader cache | Start without add-ons, then repair files |
| Menu works but a flight crashes | Aircraft, livery, scenery, WASM or streamed-data fault | Use a default aircraft at a default airport |
| Only one aircraft or airport fails | That package or one of its dependencies | Disable and reinstall the affected content |
| World data or aircraft are missing | Online services, account authentication or cache problem | Check data settings, connection and account |
| Controls no longer respond | Wrong profile or conflicting assignments | Select the intended device profile and inspect bindings |
How do you fix MSFS 2024 after an update?
Work through these checks in order and test after each one; changing several things together hides the actual cause.
- Complete all update stages. Fully quit Microsoft Flight Simulator 2024 rather than leaving it suspended, restart the PC or console, and check the platform download queue. Open the simulator again and allow any mandatory in-simulator packages to finish. Updates may need considerably more working space than their displayed download size. If the download is stuck or reports an installation error, use our platform-specific failed-update recovery steps.
- Run a clean default flight. On PC, accept Safe Mode when the simulator offers it, or temporarily move everything out of the
Communityfolder. Close external utilities that start with Windows as Safe Mode may not stop them. On Xbox or PlayStation 5, disable or uninstall optional third-party packages through the simulator or console library. Test a standard aircraft at an unmodified airport with a simple weather preset. - Clear replaceable caches. If the menus open, delete and recreate the rolling cache where that option is enabled. PC users can also clear the graphics shader cache through the operating system or graphics driver's normal cache function. The next launch may take longer while shaders are rebuilt. Do not delete the cloud save, the entire packages directory or folders such as official simulator content at random.
- Repair the installation. On PC, use the platform launcher's verify or repair command first. Choose repair before any destructive reset option; file verification may check only core files, so a faulty optional aircraft or scenery package can still need separate removal and reinstallation. On consoles, perform a full shutdown, confirm all mandatory game content is installed and check available storage. On PS5, restore licences only when installed content appears unowned, and use the console's cache-clearing function if the application data appears damaged.
- Check the graphics driver separately. Install a stable driver intended for the installed GPU, then rebuild its shader cache. If an NVIDIA app change happened at roughly the same time as the simulator update, follow our steps to separate NVIDIA application and shader-cache faults rather than assuming the simulator update caused everything.
- Verify account and online data access. Confirm that the intended platform and Microsoft accounts are signed in, online functionality is enabled and the connection is not being blocked by a VPN, proxy or security rule. Do not unlink a console account merely as a test. Authentication and streamed-data failures can leave the menus working while aircraft or world assets fail to load.
- Reinstall only after a clean test still fails. A full reinstall is justified when core-file repair fails, mandatory packages repeatedly report damage or the simulator cannot start with every optional add-on removed. Test the clean base installation before restoring any third-party content.
How can I tell whether an add-on caused the problem?
A default aircraft at a default airport must work before third-party content is restored. An empty Community folder is not always a complete test because separately installed library or Marketplace packages may remain active.
If the clean flight works, return add-ons in halves rather than one at a time. Test, divide the failing group again and repeat until one package remains. Update or remove that package and check its required dependencies; copying the entire collection back immediately is the mistake we see most often.
Complex aircraft deserve extra attention because their compiled systems may depend on simulator interfaces changed by an update. Repeated faults mentioning a module or an aircraft that uses compiled gauges call for the more focused procedure to isolate a broken WASM aircraft module.
What if MSFS 2024 starts but crashes during a flight?
The exact failure point usually identifies which content should be removed or repaired.
Crashes when selecting an aircraft
Start with that aircraft's liveries, then disable the aircraft and any shared dependency packages. A livery made for an earlier model revision can crash the selection screen even though the base aircraft itself is compatible.
Crashes while loading Free Flight
A loading-screen crash points towards the selected aircraft, departure scenery, streamed world data or a damaged core package. Our targeted Free Flight loading-crash checks help separate those causes without reinstalling the whole simulator.
Loads successfully but the controls are dead
Reinstallation is unlikely to help. Check that MSFS 2024 has selected the intended profile for each controller, confirm the device was detected, and remove duplicate axis assignments. Updates or USB device re-enumeration can cause a different profile to become active.
Should I delete my save or configuration data?
Do not delete cloud data as a routine post-update fix. It can contain control profiles, settings and Career Mode progress, while a damaged aircraft package or shader cache will remain unfixed.
If support instructions eventually require a reset, record custom control mappings first and preserve the Community folder outside the simulator directory. After any reset or reinstall, prove the base simulator works before returning optional packages in small groups.