Fix MSFS 2020 Content Manager when it stays blank or spins. Follow the correct update, add-on, storage, account and file-repair checks in order.
In Microsoft Flight Simulator 2020, Content Manager usually fails to load because the simulator shell is outdated, package scanning is blocked by a faulty Community add-on, the packages drive is unavailable, or the Xbox account session has stalled. Update the launcher first, isolate Community content, then repair files only if those checks fail.
What causes Content Manager to stay blank or keep spinning?
A blank list, endless spinner and complete simulator freeze point to different causes, so match the symptom before changing any files.
| Symptom | Likely cause | First action |
|---|---|---|
| The panel opens but shows no packages | Search, filters or the wrong Xbox profile | Clear the search, reset filters and confirm the signed-in gamertag |
| Content Manager spins after installing an add-on | A faulty or incompatible Community package | Test with an empty Community folder |
| The problem began after an MSFS update | The platform client and simulator installation are out of step | Complete the Store, Xbox app or Steam update first |
| The package library is on another drive | The drive, path or permissions are unavailable | Reconnect the drive and verify the package path |
| The whole simulator freezes or crashes | A damaged package or broader loading conflict | Use Safe Mode if offered, then repair files if necessary |
How do I fix MSFS 2020 Content Manager not loading?
Work through these checks in order and stop when Content Manager loads normally; deleting packages or reinstalling too early often creates a much larger download without fixing the cause.
- Confirm that it is genuinely stuck. Open Content Manager from the Profile area. If the controls remain responsive but no content appears, remove any search term and return the filters to a broad all-content view. After a large update or library change, allow the initial package scan to finish rather than repeatedly force-closing the simulator.
- Perform a clean restart. On PC, close MSFS 2020 and its Xbox app, Microsoft Store or Steam client, then restart Windows. On Xbox, use Quit instead of leaving the simulator in Quick Resume, then restart the console. This clears stale account and service sessions.
- Finish the external platform update. The Microsoft Store or Xbox app build must be updated through the Store library; the Steam build must complete its client download through Steam. Only then should the simulator install its own data and Content Manager packages. Our explanation of the separate MSFS 2020 update stages covers the correct order.
- Refresh the account and connection. Confirm that MSFS displays the Xbox gamertag which owns the content. Steam users also sign in to a Microsoft/Xbox profile inside the simulator. Sign out and back in at the Xbox layer, check that Windows date and time are automatic, and test without a VPN or proxy. If installed packages appear but owned Marketplace content does not, treat that as an account or online-service problem rather than damaged local files.
- Test without Community add-ons on PC. Close the simulator and move everything from the active
Communityfolder to a temporary folder outside the MSFS package directory. Do not move or deleteOfficial. If Content Manager then works, restore add-ons in small batches until the failing package is identified; our Community-folder conflict checks explain that isolation process. - Check the package drive and installation path. If packages live on an external or secondary drive, reconnect it with the same drive letter before launching MSFS. On PC, the
InstalledPackagesPathentry inUserCfg.optshould point to the package root containing theCommunityandOfficialfolders. Do not casually change it to a new empty folder, because the installer may interpret that as a missing installation and request a full download. Also confirm that the drive has free space and permits writes. - Repair the least destructive component first. If the simulator is updated, the package path is valid and Content Manager still fails with an empty Community folder, use Windows app Repair for the Microsoft Store/Xbox app build or file verification for Steam. Avoid Reset and a full reinstall until safer checks have failed. Follow our edition-specific MSFS file-repair procedure to protect an existing package library.
Xbox consoles have no user-accessible Community folder or Windows file-verification option. There, the useful sequence is a full Quit, console restart, base-game update, profile check and storage check; reinstalling the simulator is the final step.
What if Content Manager opens but packages are missing?
If Content Manager itself opens, missing packages are usually hidden by filters, associated with another Xbox profile or marked as not installed rather than lost from the drive.
Clear the search and filters, confirm the intended gamertag, and compare the Installed, Not Installed and Update Available views. Edition upgrades and Marketplace aircraft may also depend on separate base packages. If ownership is recognised but an item is absent, the missing-content recovery checks cover licences, dependencies, storage and package status.
Should I delete folders or reinstall MSFS 2020?
Do not delete the Official folder or reinstall MSFS 2020 until the updated launcher, clean Community test, account session and package path have all been checked.
Content Manager working in Safe Mode or with an empty Community folder proves that the core installation is usable; find the conflicting add-on instead. Reinstall only when the clean simulator still fails, the package drive is accessible and file repair cannot restore it. Record the existing package location first so the installer is not accidentally pointed at an empty directory.