Learn how to install the Fenix A320 in MSFS, select the correct Packages folder, run the desktop app and fix an incomplete installation.
Install the Fenix A320 in Microsoft Flight Simulator (MSFS 2020) on PC with the official Fenix installer, not by extracting files into Community. Close MSFS, sign in with the purchase account, select the correct simulator and Packages location if prompted, install every required component, then run the Fenix desktop app before loading the aircraft.
Why does the Fenix A320 need its own installer?
The Fenix A320 needs its dedicated installer because part of the product runs outside Microsoft Flight Simulator. The installer manages the in-sim aircraft package, desktop components, required supporting files, purchase validation and updates.
This differs from a typical freeware aircraft that can be extracted directly into Community. Our general MSFS aircraft installation guide explains when manual Community-folder installation is appropriate.
How to install the Fenix A320 in MSFS
Use the latest official installer and allow it to manage both the simulator package and the companion software.
- Run MSFS at least once. If Microsoft Flight Simulator has just been installed or moved, launch it once so that it creates and records its active Packages folders. Close the simulator before continuing.
- Download the official installer. Obtain it through the account associated with your Fenix purchase. Avoid copied installers, old backups and manually extracted aircraft folders.
- Sign in to the correct account. The installer must be able to verify the account that owns the aircraft.
- Select the intended simulator. If more than one supported Microsoft Flight Simulator installation is detected, choose the edition in which you want to use the A320.
- Confirm the installation path. When asked for the Packages location, select the folder containing
CommunityandOfficial. If the prompt specifically asks forCommunity, select that folder instead. - Install every requested component. Let the process finish even if an aircraft folder appears before the progress indicator completes. Accept required supporting components offered by the official installer.
- Start the Fenix desktop app. Make sure it is running and signed in if requested. It may start automatically, but do not close it while using the aircraft.
- Launch MSFS and find the aircraft. Search the aircraft selector for Fenix or Airbus and clear filters that exclude third-party aircraft. Depending on the installed product content, more than one A320 variant may be listed.
Which MSFS folder should the Fenix installer use?
The correct Packages root is the folder directly containing Community and Official, not the simulator executable, desktop shortcut or a broad Windows applications folder.
Custom MSFS installations can place this folder on another drive. In MSFS 2020, the InstalledPackagesPath entry inside UserCfg.opt records the active Packages location; its surrounding file path varies between installation types, so do not copy a path from somebody else’s computer.
Do I put the Fenix A320 in Community manually?
No; let the Fenix installer place or link its simulator package where it belongs. Although part of the installation may ultimately appear under Community, that does not make the Fenix A320 a normal drag-and-drop add-on.
A mistake we see constantly is copying another extracted Fenix folder into Community after installation. Duplicate, nested or incomplete packages can hide the aircraft, interfere with updates or produce an aircraft that loads without working systems. Do not move installer-managed folders afterwards unless the official installer provides a supported location option.
Why is the Fenix A320 not showing in MSFS?
A missing Fenix A320 usually means the installer targeted the wrong simulator location, installation did not finish, or the aircraft-selection filters are hiding it.
| Symptom | Likely cause | What to do |
|---|---|---|
| The installer cannot detect MSFS | MSFS has not been run, the Packages folder was moved, or the wrong simulator edition was selected | Launch and close MSFS once, then confirm the active Packages root and selected simulator |
| The installation completes but no aircraft appears | The package went to an unused Community folder or menu filters are active | Check the install path, clear aircraft filters and restart MSFS |
| The aircraft appears but its systems do not work | The Fenix desktop app is closed, signed out, blocked or incompletely installed | Start the app, check its status and use the installer’s repair or reinstall option if available |
| Installation or updating repeatedly fails | Security software, folder permissions, insufficient free space or leftover partial files are preventing completion | Review Windows security notifications, remove only known duplicate manual copies, free space and rerun the official installer |
If security software quarantined a file, verify that it came from the official installer before allowing it. Do not permanently disable Windows security or create broad exclusions simply to force the installation through.
When the aircraft is present but displays, controls or external components still fail, follow our Fenix A320 troubleshooting checks rather than repeatedly copying files into Community.
Does the Fenix desktop app need to stay open?
The Fenix desktop component must be installed and running for the aircraft’s full systems to operate. If it does not start automatically, open it before selecting the aircraft and leave it running during the flight.
A cockpit that loads unpowered is not necessarily broken. The A320 may be using a cold-and-dark panel state; our Fenix A320 cold-and-dark start procedure covers the normal electrical and engine-start sequence.
Can I install the Fenix A320 on Xbox?
No. The Fenix A320 is a PC add-on because it relies on companion software running outside the simulator. An Xbox cannot run that desktop component, and transferring the PC aircraft package manually does not make it compatible.
When should I install Fenix A320 liveries?
Install liveries only after the base aircraft loads and works with a supplied paint scheme. This keeps a malformed, outdated or incorrectly nested livery package from being mistaken for a failed aircraft installation.
Use the livery facility in the official Fenix software where one is provided. For separately packaged liveries, follow their supplied instructions and avoid replacing files inside the installer-managed base aircraft folder.