How do I update the Aerosoft CRJ in MSFS?

Update the Aerosoft CRJ through the same sales channel used to buy it: Aerosoft One for a direct Aerosoft licence, Microsoft Flight Simulator’s package manager for a Marketplace licence, or the original retailer’s app. Close MSFS first, install the offered build, and make sure no older CRJ package remains active.

Which updater should I use for the Aerosoft CRJ?

The updater is determined by where the licence was purchased, not by where the aircraft folder happens to be installed.

The build may reach each distribution channel at a different time. If Aerosoft One offers an update but the Marketplace does not, wait for the Marketplace package rather than trying to install the direct-store build over it. Console users must update through the in-sim library; external installers and Community-folder fixes are PC-only.

How do I install the CRJ update safely?

With MSFS closed, update through the launcher that owns the licence or perform a clean reinstall if that launcher cannot detect the existing build.

1. Confirm the simulator edition and purchase channel. Install only a CRJ package explicitly listed for the Microsoft Flight Simulator edition you use. An aircraft update does not automatically convert an MSFS 2020 package into a supported MSFS 2024 package.
2. Close the simulator. Also close utilities that link, move or monitor add-on folders before opening the updater.
3. Back up genuine customisations. Save any files you edited yourself, but put the backup outside every folder scanned by MSFS.
4. Run the correct update method.
   • For Aerosoft One, sign in with the account that owns the CRJ, open its library entry and install the offered update.
   • For a Marketplace copy, start MSFS, open its content library or package manager, filter for available updates and update the CRJ there.
   • For a legacy or retailer-managed copy, download or run the latest installer attached to that purchase. If it requests a package location, select the path belonging to the correct simulator installation; our aircraft installation and package-path guide explains how to identify it without creating a second active copy.
5. Remove duplicate core packages. Keep one active CRJ installation. Move an obsolete manual copy completely outside Community and any linked add-on directory; merely renaming a folder inside Community may not stop MSFS scanning it.
6. Verify the result. Compare the installed version shown by the owning launcher or MSFS package manager with the version it offers, then start a fresh flight using a default CRJ livery rather than resuming an old session.

Why does the CRJ still show the old version?

An unchanged CRJ version usually means the wrong account, package path or duplicate aircraft copy is being used.

• No update button: confirm that the updater is signed into the purchasing account and that you are checking the correct sales channel. The absence of an update can also mean that channel has not received the new build yet.
• Installer cannot find MSFS: verify the simulator’s active package path instead of selecting its executable directory or a Community folder left behind by an older installation.
• Old version still loads: search Community and any externally linked add-on folders for another CRJ core package. A manual copy can conflict with the Marketplace package stored under Official.
• Aircraft disappears: check for an extra level of folder nesting, the wrong Community folder or a disabled link. Our steps for diagnosing an add-on that MSFS cannot detect cover those cases.
• Download loops or fails: restart the owning launcher, confirm sufficient storage and finish any mandatory simulator update first. If MSFS or its package manager is failing too, use our simulator and package-update error checks.
• Cockpit systems behave incorrectly after updating: test a fresh flight with the default livery and temporarily remove optional CRJ modifications. An older livery, sound pack or cockpit modification may not be compatible with the new aircraft build.

Protecting liveries and settings

Separate livery packages normally remain installed, but anything edited inside the CRJ’s core package can be overwritten by an update or clean reinstall. Saved panel states and preferences may also reset when an update changes their format.

Back up only your custom files and settings, not the complete old aircraft directory. Restoring the whole directory over the new build can reintroduce obsolete gauges, configuration files and manifests—the exact problem a clean update is meant to remove.

Does updating the CRJ also update its navigation data?

The aircraft software and its flight-management navigation database are separate, so a CRJ software update should not be treated as an AIRAC update. If the FMS still reports an old cycle after the aircraft is updated, follow the appropriate method to update MSFS navigation data separately and select a dataset that explicitly supports the CRJ and your simulator edition.