MSFS 2020 stuck on Checking for updates: how do I fix it?

When Microsoft Flight Simulator 2020 is stuck on Checking for updates, fully quit it, update the launcher in Microsoft Store, the Xbox app or Steam, sign in again, and test without VPN filtering or Community add-ons. Rebuild package indexes only after checking the service, account, package path and launcher; never delete the Official folder.

Choose the right fix for your MSFS 2020 update problem

Match the symptom before changing files because launcher updates, account entitlement, package paths and service outages require different fixes.

Why does MSFS 2020 get stuck on Checking for updates?

The update screen verifies the licence, launcher version, mandatory content manifest and configured package location before opening the main menu.

• Service or sign-in failure: the Xbox profile, Microsoft Store or update service is unavailable or holding an expired session.
• Launcher mismatch: the platform client has not installed the small application update needed before the in-simulator installer can download larger packages.
• Unavailable package drive: the drive holding Community and Official is disconnected, full, read-only or using a different drive letter.
• Damaged package index: an interrupted update has left Content.xml or SceneryIndexes inconsistent with the installed packages.
• Add-on conflict: an outdated Community or third-party Marketplace package is blocking the package scan.
• Network filtering: a VPN, proxy, firewall, DNS problem or incorrect system clock is preventing a secure connection.

How do I fix MSFS 2020 stuck on Checking for updates?

We recommend the following order because it rules out external causes before touching downloaded simulator content.

1. Check for a service or account problem. Confirm that the Xbox app can sign in and that your platform client can start another download. If Microsoft-connected services fail together, close MSFS and wait rather than deleting package files.
2. End the session completely. On PC, close MSFS and its platform client, using Task Manager if either remains in the background. On Xbox, highlight the game tile and choose Quit instead of resuming through Quick Resume. Restart the PC or console and, if connection problems affect other devices, the router.
3. Install the launcher update in the correct client. Microsoft Store and Game Pass installations must be updated through Microsoft Store or the Xbox app. Steam installations must finish their update in Steam Library or Downloads. Xbox Series X|S users should check both the game update and pending console system updates.
4. Refresh the account session. Store and Game Pass users should sign out of Microsoft Store and the Xbox app, restart Windows, then sign back into the account with the required purchase or subscription entitlement. Steam owns the Steam edition's licence, but MSFS still needs a valid Microsoft or Xbox profile in the simulator.
5. Test without network filtering. Temporarily disconnect VPNs and proxies, set the system date and time automatically, and confirm that MSFS and its platform client are allowed through the firewall. A phone hotspot can be used briefly as a diagnostic. If that works, investigate the original router, DNS service or local filtering, but avoid downloading a large update over a metered connection.
6. Test a clean Community folder. Rename Community temporarily, or choose Safe Mode if MSFS offers it after an abnormal shutdown. If the simulator opens, return add-ons in small groups until the conflicting package is found.
7. Check storage before clearing anything. Keep free space on both the Windows system drive and the drive containing the simulator packages. Confirm that an external package drive is connected, writable and using its expected drive letter.

Platform-specific update checks

Use the subsection matching the platform that owns your MSFS 2020 licence; installing an update in the wrong client will not repair the launcher.

Microsoft Store or Game Pass on PC

Store and Game Pass users need working Microsoft Store, Xbox app and Gaming Services components as well as a valid game entitlement.

• Open the Microsoft Store Library and check for updates to MSFS, the Xbox app and Gaming Services.
• Confirm that Microsoft Store holds the purchasing or subscription account and that the Xbox app is using the intended simulator profile.
• Check that the configured package drive is connected before starting MSFS.
• If the Xbox app or Store displays 0x87e00022, stop here and use the installation-manager procedure in the next section.

Steam on PC

Steam users should complete the small Steam launcher update before allowing MSFS to check its much larger Official package library.

• Inspect Steam's Downloads section for a paused, scheduled or failed MSFS update.
• Restart Steam and launch MSFS from the Steam Library rather than an old shortcut.
• Confirm that the Microsoft or Xbox profile requested by MSFS can sign in.
• Use Steam file verification only after recording the existing package path. Verification can cause package rediscovery and, if the path is wrong, a substantial download.

Xbox Series X|S

Xbox users should fully quit MSFS, install console and game updates, and confirm that the active profile has an entitlement to run it.

• Restart the console instead of relying on Quick Resume.
• Check available internal storage; installation needs working space beyond the compressed download size.
• Try another network if possible. If that succeeds, restart the original router and review its filtering.
• Do not clear reserved space as an early fix. It can remove simulator content and require a large download.

PC: MSFS installation manager error 0x87e00022

Error 0x87e00022 is a Microsoft Store or Xbox installation failure, not the normal in-simulator Checking for updates content-manifest hang.

Follow these steps when the code appears in Microsoft Store, the Xbox app or its installation manager, or when the PC installation cannot start or resume. Do not begin by resetting Content.xml or SceneryIndexes; those files are relevant only after MSFS can launch and read its package library.

1. Confirm storage and drive availability. Check free space on the Windows system drive and the selected installation or package drive. Reconnect external drives, verify their drive letters and make sure Windows can create files there.
2. Restart the installation clients. Close the Xbox app and Microsoft Store completely, end any remaining processes, restart Windows, then reopen both and confirm the correct account is signed in.
3. Use Repair before Reset. In Windows Installed apps controls, run Repair for Gaming Services, the Xbox app and Microsoft Flight Simulator. Restart Windows after repairing them.
4. Retry the original installation. Start it from the same Store or Xbox account without deleting Official\OneStore, moving packages or selecting Reset. Existing packages may be recognised once the installation service works again.

If the code is accompanied by a missing package drive, failed download or account mismatch, our MSFS installation and package-path checks cover those related failures without assuming that a full reinstall is required.

What if MSFS is still stuck after I ran it as administrator?

Running MSFS as administrator does not repair a stale licence, missing launcher update, unavailable package drive, Gaming Services failure or service outage.

If administrator mode did not help, return to a normal launch and verify InstalledPackagesPath before rebuilding package data. A mistake we see often is clearing indexes or redirecting the package path before confirming where the existing Official library is stored.

Check InstalledPackagesPath first

The final InstalledPackagesPath entry in UserCfg.opt must point to the folder containing the existing Community and Official directories.

1. Close every related program. Exit MSFS, Steam, the Xbox app and Microsoft Store.
2. Locate UserCfg.opt. Store and Game Pass installations normally keep it under %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache. Steam installations normally use %APPDATA%\Microsoft Flight Simulator.
3. Read the final package-path entry. If it points to a disconnected drive or an old drive letter, restore that drive or correct the path carefully.
4. Do not choose an empty folder. Redirecting the path to an empty location makes MSFS treat the official package library as missing and can trigger a complete download.

Rebuild the PC package indexes

Rebuild these indexes only when MSFS reaches the update check, the package path is correct and the earlier account, launcher and network checks have failed.

1. Make backups rather than deleting files. In the relevant configuration folder, rename Content.xml to Content.xml.old if it exists. Rename the SceneryIndexes folder in the same way.
2. Start MSFS normally. The simulator will rebuild the indexes, so the first launch can take longer than usual.
3. Confirm that content is recognised. Keep the backups until the simulator opens and the installed aircraft and scenery appear correctly.

Do not delete Official\OneStore or Official\Steam. Resetting ROLLINGCACHE.CCC is not a first-line fix either; the rolling cache stores streamed scenery and does not control the launcher version or account check.

Why does MSFS download the same update every time?

A repeated update means that MSFS can obtain files but cannot finish, save or locate the completed package during the next launch.

• Allow decompression to finish even if network activity falls to zero; that phase can be limited by disk performance.
• Maintain free space on both the system drive and package drive.
• Check that InstalledPackagesPath still points to the folder containing the populated Official directory.
• Permit MSFS and its platform client to write to the package drive rather than leaving security protection disabled.
• Do not move individual Official packages manually. An incomplete or incorrectly moved package can restart the download.

Do tutorial flights or World Updates need updating first?

Optional tutorial content and World Updates do not need to be installed before MSFS can pass the mandatory update check and reach the main menu.

Install the core launcher and mandatory packages first. Once the simulator opens, use Content Manager to update optional training, aircraft and regional packages; our guide explains how optional World Updates differ from core simulator updates.

When should I reset or reinstall MSFS 2020?

Reset or reinstall only after platform repair, account, storage, package-path and service checks have failed because either action can require the entire Official library to be downloaded again.

For persistent Microsoft Store or Game Pass failures, record the exact error code and the InstalledPackagesPath value before making further changes. Use Windows Repair for Gaming Services, the Xbox app and MSFS before selecting Reset.

If Repair fails and the Store or Xbox installation still produces an error, contact Microsoft or Xbox support with the recorded code, account entitlement details and package location. Resetting the app, clearing console reserved space or reinstalling MSFS can remove package registration or downloaded content, so proceed only when you are prepared for a full official-package download.