To install the FlyByWire A32NX in Microsoft Flight Simulator 2020, use the project installer on the PC version of MSFS, point it at your Community folder if needed, then let it place the aircraft package there. Remove any older A32NX copy first to avoid conflicts.
What you need before you install
- A PC copy of Microsoft Flight Simulator 2020. The A32NX is a community add-on, so this install method is for PC. Xbox consoles do not use the Community folder in the same way.
- Microsoft Flight Simulator fully closed. Do not install or update the aircraft while the sim is running.
- Your Community folder location. This sits inside the main MSFS packages location, but the exact path depends on your PC edition and any custom install location you chose.
- No old A32NX leftovers. Duplicate folders are one of the most common reasons the aircraft fails to load properly.
How to install the FlyByWire A32NX in MSFS 2020
- Close MSFS completely
Exit the simulator before you do anything else. If you have just updated the sim, let that finish first.
- Use the FlyByWire installer
We recommend the dedicated installer rather than a manual drag-and-drop install. It usually handles the correct package structure, updates and clean removal better than doing it by hand.
- Choose the A32NX version you want
Most users should install the stable branch if the installer offers more than one channel. Development builds can add features sooner, but they can also expose bugs after sim or aircraft updates.
- Check the Community folder path
If the installer asks where your Community folder is, point it to the exact folder MSFS reads at start-up. This matters. A perfectly good install in the wrong Community folder will not appear in the sim.
- Install the package
Start the install and let the tool finish without moving files around manually. The A32NX should end up as a single package folder inside Community, not spread across multiple locations.
- Launch MSFS and load the aircraft
Open Microsoft Flight Simulator 2020 and look for the FlyByWire A32NX entry in the aircraft selection list. Depending on the package version, it may appear alongside the Airbus A320neo family rather than as a completely separate aircraft type.
Which A32NX version should you install?
The installer often offers more than one branch. If you just want a dependable airliner for normal flying, we would start with the most stable option.
| Branch | Best for | What to expect |
|---|---|---|
| Stable | Most users | Fewer changes, lower chance of surprises, usually the safest choice after MSFS updates. |
| Development | Experienced users | New features arrive sooner, but occasional regressions and compatibility issues are more likely. |
| Testing or experimental | Troubleshooting or preview use | Only use this if you specifically want to test newer code and accept the risk of breakage. |
Can I install the A32NX manually in the Community folder?
Yes, but we usually advise against it unless you have a specific reason. Manual installs are more prone to wrong folder depth, duplicate files and update problems.
| Method | Pros | Cons |
|---|---|---|
| Installer | Cleaner updates, easier removal, less chance of folder mistakes | You still need to confirm the correct Community folder |
| Manual install | Useful if you already have the package archive | Higher risk of nested folders, stale files and broken updates |
If you do install manually, the process is simple but unforgiving.
- Remove any existing A32NX folder
Do this first so you do not end up with two versions in Community.
- Extract the package fully
Do not copy the ZIP file itself into Community. Extract it first.
- Place the single aircraft package folder in Community
The aircraft folder should sit directly inside Community. Avoid an extra layer such as
Community\A32NX\A32NX. - Start MSFS and verify the aircraft appears
If it does not, the usual cause is still the wrong Community folder or an incorrect folder structure.
How do I know the A32NX installed correctly?
A correct install usually shows up in the aircraft selector and loads with FlyByWire-specific systems and cockpit behaviour rather than the plain default A320neo experience. If the cockpit looks partly default, the electronic flight bag is missing, or the aircraft behaves like the stock Airbus, we would suspect an incomplete or conflicting install.
It is also normal for aircraft and avionics to take a little time to initialise after loading at the gate. That is different from a broken install.
Why is the A32NX not showing up in MSFS 2020?
- You used the wrong Community folder
MSFS only reads one active Community folder from your chosen packages location. Installing to an old or unused path is the most common problem.
- You have two A32NX copies
An older manual install plus a newer installer version can cause missing aircraft, odd behaviour or black screens.
- The folder is nested incorrectly
If the actual package folder is buried inside another folder, MSFS may ignore it completely.
- You updated while the sim was open
Close MSFS, remove the package, reinstall it cleanly, then restart the sim.
- An old A320 mod or livery is conflicting
Outdated liveries and cockpit mods made for the default Airbus can interfere with the A32NX. If in doubt, test with only the A32NX installed.
- You are on Xbox
The A32NX is not installed through the PC Community folder workflow on Xbox consoles.
What if the A32NX loads but the cockpit is broken?
If the aircraft appears but key systems are missing, the most likely cause is a conflict rather than a failed install. We would check these first:
- Remove old A320 liveries and test again.
- Delete the current A32NX package completely, then reinstall it cleanly.
- Use the stable branch if you were on a development or testing build.
- Temporarily empty the Community folder except for the A32NX to rule out another add-on.
How to update or remove the FlyByWire A32NX
The cleanest way to update or remove the aircraft is with the same installer you used to add it. That keeps the package consistent and avoids stale files. If you previously installed it manually, remove the old manual folder before switching to installer-managed updates.
If you keep your Community folder tidy and avoid duplicate Airbus mods, the A32NX is usually straightforward to maintain. Most install problems come down to the wrong folder, an extra nested folder, or two versions sitting in Community at the same time.