Why won’t Microsoft Flight Simulator 2020 launch on PC?

Microsoft Flight Simulator 2020 usually will not launch on PC because a Community or Marketplace add-on is incompatible, an update package or cache is damaged, Xbox sign-in or Gaming Services has failed, or a graphics driver, overlay, overclock, security rule, memory shortage or storage problem crashes the simulator before its main menu.

Where does Microsoft Flight Simulator stop loading?

The point at which MSFS 2020 stops is the quickest way to narrow down the fault.

Watch Task Manager before assuming a loading screen has frozen. Continued disk, processor or network activity can mean MSFS is still checking or unpacking content, particularly after an update. A process that repeatedly disappears or sits inactive at the same point needs troubleshooting.

What should I try first when MSFS 2020 will not launch?

The fastest approach is to test the simulator in a clean state before reinstalling anything.

1. Restart Windows and use the correct launcher. Close MSFS, Steam, the Xbox app and Microsoft Store completely, then restart the PC. Launch the simulator through the platform that manages the installation rather than an old shortcut. Allow any pending Windows, Xbox app or Gaming Services update to finish first.
2. Choose Safe Mode when offered. Following an abnormal shutdown, MSFS may offer Normal Mode or Safe Mode. Choose Safe Mode: it disables third-party Community and Marketplace content for that session. If the main menu opens, the base simulator is probably sound and an add-on is the leading suspect.
3. Test with an empty Community folder. Move its contents elsewhere or rename the folder to Community.disabled. Do not merely remove the add-on you think is responsible; shared libraries and utilities can be the real cause. Our guide to finding the correct Community folder and managing MSFS add-ons explains the platform-dependent locations and the InstalledPackagesPath entry in UserCfg.opt.
4. Repair the account and platform layer. For Xbox app, Game Pass or Microsoft Store installations, confirm that the account holding the game licence or subscription is signed in correctly. Sign out and back in if necessary, then use the available Repair options for the Xbox app, Microsoft Store and Gaming Services. Steam installations still require the Microsoft/Xbox sign-in inside MSFS.
5. Remove software and hardware conflicts. Shut down recording overlays, frame-rate counters, RGB or monitoring utilities, graphics injectors and third-party flight-sim tools. Disconnect non-essential USB controllers while testing. Temporarily return CPU, GPU and memory settings to stock, including memory profiles, undervolts and overclocks.
6. Verify or repair the installation. Use Steam’s file verification or the Xbox app’s repair facility, depending on the installation. Steam mainly checks Steam-managed launcher files; much of the large Packages installation is controlled by the simulator’s updater, so a successful verification does not prove every aircraft or scenery package is intact. Use Repair before Reset because resetting an app can remove local settings or trigger package redetection and downloads.
7. Check the rolling cache and free space. If the menus are accessible, disable and delete the rolling cache from the simulator’s Data settings, then recreate it later. If you placed the cache in a custom location and cannot reach the menu, rename that cache file rather than permanently deleting it. Leave adequate free space on both the Windows drive and the drive containing the Packages folder so updates can download, unpack and replace files.
8. Test the graphics driver and memory configuration. Install a suitable GPU driver, or roll back if launch failures began immediately after a driver change. On a laptop, make sure MSFS uses the dedicated graphics processor. Keep the Windows page file enabled and preferably system-managed; disabling virtual memory can cause a desktop crash even when the PC has substantial physical RAM.

How do I find the add-on that is crashing MSFS?

If Microsoft Flight Simulator launches with Safe Mode or an empty Community folder, restore add-ons in batches until the failure returns.

• Begin with an empty Community folder and confirm that Normal Mode reaches the main menu.
• Restore a small group of packages, then launch the simulator again.
• When the crash returns, remove the last group and test those packages in smaller groups.
• Remove duplicate versions, obsolete dependencies and old folders left behind by previous installations.
• Check utilities, traffic packages and shared libraries as well as aircraft and scenery.

A mistake we see constantly is putting every package back after one successful clean launch. That proves only that the base simulator works; it does not identify the faulty content.

An empty Community folder does not isolate every add-on. Third-party Marketplace products normally reside under the Official package structure, and Safe Mode can disable those as well. If Safe Mode works but an empty Community folder does not solve Normal Mode, use Content Manager, where accessible, to remove newly installed or updated third-party Marketplace content. Do not delete the entire Official folder unless you intend to download all of that content again.

What if MSFS is stuck on Checking for updates?

A persistent Checking for updates screen usually points to account authorisation, Gaming Services or network access rather than raw PC performance.

• Confirm account access. Make sure the Xbox app can sign in and that the account with the required licence or subscription is available.
• Correct the Windows clock. An incorrect date, time or time zone can break secure account authentication.
• Repair Gaming Services. Apply available app updates and use Windows’ repair facility before considering a reset.
• Remove network filters while testing. Pause VPNs, proxies and aggressive web filtering, and check that firewall or antivirus rules are not blocking MSFS, the Xbox app or Gaming Services.
• Look for a hidden prompt. A sign-in or permission window can open behind the simulator or on another display.

If the update starts but repeatedly loops, loses progress or reports insufficient space, the problem has moved from launching to package installation. Follow our fixes for stalled and failed MSFS downloads or installations before removing the whole simulator.

Could the PC specification or graphics driver prevent launch?

Yes, although instability and exhausted memory are more likely to cause a launch crash than a slightly underpowered graphics card.

MSFS places sustained load on the processor, memory controller and GPU, so an overclock that appears stable in lighter games can still fail at the splash screen. Test stock settings, close memory-heavy background applications and keep virtual memory enabled. If you are unsure where the machine falls, compare it with our explanation of Microsoft Flight Simulator PC requirements and practical hardware priorities.

What causes a black screen after launch?

A black screen with MSFS still running is most commonly caused by a graphics conflict, damaged cache or content that cannot finish loading.

Test with the Community folder empty, overlays and injectors disabled, and the dedicated GPU selected. Update the display driver unless the fault began directly after updating it; in that case, rolling back to the previously stable driver is the better test. A blank cockpit display after a flight has loaded is a separate avionics or aircraft issue, not a simulator launch failure.

How can I identify a crash with no error message?

Windows Reliability Monitor can show whether the fault repeatedly involves the simulator, a graphics component or an external utility.

Look for a consistent faulting component at the time of each crash rather than treating one isolated entry as proof. Repeated graphics-related failures support a driver or hardware-stability test; platform-service failures point back to Gaming Services or account repair. Record the result before changing several things at once, otherwise it becomes difficult to tell which fix worked.

When should I reinstall Microsoft Flight Simulator 2020?

Reinstall MSFS only after Safe Mode, an empty Community folder, platform repair, file verification and stock hardware settings have all failed.

A clean reinstall is justified when core packages cannot be repaired, an interrupted update left the Official content unusable, or the package drive and installation path can no longer be accessed reliably. Back up the Community folder and note any custom Packages location first. Do not restore add-ons until the newly installed base simulator has reached the main menu in Normal Mode at least once.

Reinstalling only the launcher may leave the large Packages directory untouched, which means damaged content can survive the reinstall. Conversely, deleting the Packages directory forces a substantial download. Decide which action is necessary from the evidence rather than deleting both automatically.