How do I fix MSFS 2020 stuck checking for updates?

Microsoft Flight Simulator 2020 usually hangs on “Checking for updates” because the installed launcher and mandatory packages are out of sync, Xbox authentication has stalled, the network cannot reach Microsoft’s services, or cached package data is damaged. Restart first, then update the launcher, re-authenticate, test a clean Community folder and reset only the relevant caches.

Why does MSFS 2020 get stuck on Checking for updates?

The screen is a gateway that verifies your licence, launcher version and mandatory content manifest before the main menu opens. It can therefore stall even when the internet otherwise appears to work.

• Service or authentication failure: Xbox Network sign-in or Microsoft’s update service is unavailable or has retained an expired login.
• Version mismatch: the platform client has not installed the small launcher update required before MSFS can download its larger content packages.
• Damaged package data: an interrupted update has left an invalid content index or incomplete package.
• Add-on conflict: an outdated Community or third-party Marketplace package is blocking the package scan after a simulator update.
• Network filtering: a VPN, proxy, firewall, DNS problem or incorrect system clock prevents secure contact with the update service.
• Unavailable package drive: the configured content folder is on a disconnected drive, has changed drive letter or cannot be written to.

The mandatory update check is separate from optional regional content. Our explanation of core simulator patches and optional World Updates covers what should be installed before and after reaching the main menu.

How do I fix the Checking for updates loop?

Use the following order so that you do not trigger an unnecessary full download.

1. Rule out a service problem. Check whether the Xbox app can sign in and whether Store or Steam downloads work. If several Microsoft-connected services fail at once, do not delete simulator files; close MSFS and retry after the service recovers.
2. End the session completely. On PC, close MSFS and its platform client, using Task Manager if either remains in the background. On Xbox, select the game tile and choose Quit rather than resuming a suspended session. Restart the computer or console and the router.
3. Update the correct launcher. Use the route in the table above, then start MSFS from that platform client. The in-simulator package installer cannot correct an outdated Store, Steam or Xbox launcher by itself.
4. Refresh your account sign-in. Store and Game Pass users should sign out of the Xbox app and Microsoft Store, restart Windows, then sign back into the account that owns the licence or subscription. Steam owns the Steam edition’s licence, but MSFS still needs a valid Microsoft/Xbox profile.
5. Test the connection without filtering. Temporarily disconnect VPNs and proxies, confirm that Windows date and time are automatic, and allow MSFS plus its platform client through the firewall. A phone hotspot is useful as a short diagnostic: if the check succeeds there, the likely fault is the router, DNS service or local network filtering. Avoid downloading the full update over a metered connection.
6. Remove third-party packages. Rename the Community folder temporarily, or select Safe Mode if MSFS offers it after an abnormal shutdown. If the simulator opens, restore add-ons in small groups until the faulty package is identified. Our Community-folder installation and removal instructions explain how to locate the folder when a custom package path is in use.

Resetting package data on PC

A damaged package index can be rebuilt without deleting downloaded aircraft or scenery. Close MSFS, Steam, the Xbox app and Microsoft Store before making these changes.

1. Open the configuration folder. Store and Game Pass installations normally use %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache. Steam installations normally use %APPDATA%\Microsoft Flight Simulator.
2. Back up the indexes. If present, rename Content.xml to Content.xml.old and rename the SceneryIndexes folder rather than deleting either one.
3. Start MSFS again. The simulator rebuilds these indexes, so the first launch may take longer. If it opens, retain the backups until you have confirmed that installed content is recognised.

Do not delete the Official\OneStore or Official\Steam package folder. Resetting ROLLINGCACHE.CCC is also not a first-line fix here: the rolling cache controls streamed scenery, not the launcher’s version check.

If the Microsoft Store edition still fails, use Windows’ Installed apps controls to run Repair on Gaming Services, the Xbox app and MSFS before considering Reset. Steam users can verify launcher files, but should record the existing package location first because file verification can lead to package rediscovery or a large download. If MSFS stops reaching the update screen altogether, move to our wider PC launch troubleshooting checks.

Xbox-specific fixes

On Xbox Series X|S, fully quitting the game and installing both console and game updates fixes many stale update sessions.

• Restart the console rather than relying on Quick Resume.
• Confirm that the signed-in profile owns MSFS 2020 or has an active entitlement to use it.
• Check available internal storage; package installation needs working space beyond the compressed download size.
• Test a different network if possible. If that works, restart the original router and review its filtering settings.
• Do not clear reserved space as an early fix. It can remove downloaded simulator content and require a substantial re-download.

Why does MSFS download the same update every time?

A repeated update usually means that MSFS can download the files but cannot finish, save or find the completed package on the next launch.

• Allow the installer to complete its decompression stage even when network activity drops; this stage can be limited by disk performance.
• Keep adequate free space on both the Windows system drive and the drive holding the MSFS packages.
• Check the final InstalledPackagesPath entry in UserCfg.opt. It should point to the existing folder containing Community and Official. If an external drive letter changed, restore that drive or correct the path carefully.
• Do not redirect InstalledPackagesPath to an empty folder unless you intend to download all official content again.
• If security software blocks writes to the package drive, permit MSFS and its platform client rather than leaving protection disabled.

Reinstall only as a last resort

A full reinstall does not fix a service outage, account mismatch or blocked connection, and it can force the entire official package library to download again. Repair the platform client, rebuild only the package indexes and confirm the configured package path first. Reinstall MSFS only when launcher files remain damaged after those checks or the platform’s own repair process fails.