FlyByWire A32NX not loading or appearing in MSFS? Fix the Community path, nested files, duplicate builds, livery conflicts and black screens.
The FlyByWire A32NX usually will not load in Microsoft Flight Simulator because MSFS is reading the wrong Community folder, the package is nested or incomplete, or an old livery or duplicate is conflicting with it. Confirm the simulator and platform, install one clean compatible build, then test it alone in a new flight.
Is the A32NX missing, hanging or loaded but unpowered?
The exact symptom shows whether MSFS failed to detect the package, encountered a loading conflict or successfully loaded an aircraft without electrical power.
| Symptom | Likely cause | Check first |
|---|---|---|
| No FlyByWire aircraft in the selector | Wrong Community folder, compressed archive, nested package or incompatible build | Find the active package path and locate manifest.json |
| Only the stock A320neo appears | The A32NX was not detected or an aircraft filter is hiding it | Clear all selector filters and search for FlyByWire or A32NX |
| The loading bar stops or MSFS closes | Corrupt files, duplicate packages, a saved-flight reference or an add-on conflict | Start a new flight with only the A32NX installed |
| The cockpit loads with black displays | Cold-and-dark state, no electrical source, low brightness or a panel conflict | Power the aircraft before reinstalling it |
| Pink textures or missing aircraft sections | Incomplete package files or an incompatible livery | Remove custom liveries and reinstall the aircraft |
| Stock aircraft also fail to load | A simulator, platform-service, storage or base-content problem | Test MSFS with the entire Community folder empty |
Can the A32NX load on PC, Xbox or PlayStation?
The standard FlyByWire Installer and manually extracted Community package work through the Windows PC add-on system; they cannot be copied into console editions of Microsoft Flight Simulator.
| Simulator and platform | What applies |
|---|---|
| MSFS 2020 on Windows PC | Install a compatible A32NX build into the active MSFS 2020 package location. |
| MSFS 2020 on Xbox | The Windows Installer and manual Community package cannot be sideloaded. |
| MSFS 2020 on PlayStation | MSFS 2020 was never released for PlayStation. |
| MSFS 2024 on Windows PC | Select the MSFS 2024 target and use only a build identified as compatible with that simulator. |
| MSFS 2024 on Xbox, PS5 or PS5 Pro | The standard Windows Installer and manually copied package cannot be used. |
Installing the A32NX for MSFS 2020 does not install it for MSFS 2024, even when both simulators are on the same computer. Each simulator reads its own package location.
Why does the FlyByWire A32NX not appear in the aircraft list?
When the A32NX is not there at all, MSFS has usually failed to discover the package rather than failed to operate the aircraft.
- Confirm the simulator and platform. A Windows package placed in an MSFS 2020 location will not appear in MSFS 2024, and PC files cannot be transferred to Xbox or PlayStation.
- Clear the aircraft-selector filters. Remove manufacturer, aircraft-type, favourites and other filters, then search for
FlyByWireandA32NX. The FlyByWire aircraft is a separate entry from the stock Airbus A320neo. - Close MSFS completely. Do not move, merge or replace packages while the simulator is running. Close the FlyByWire Installer before manually deleting an old installation.
- Find the active Community folder. Multiple folders with that name are common after moving the package library, changing drives or installing both simulator generations. Follow our MSFS 2020 A32NX installation and active-folder checks, or use the separate MSFS 2024 path and compatibility procedure.
- Inspect the package structure. The A32NX package folder must directly contain
manifest.jsonandlayout.json. A typical path resemblesCommunity/flybywire-aircraft-a320-neo/manifest.json. If those files sit inside another identically named folder, move the inner package up one level. MSFS will not load a ZIP or another compressed archive left in Community. - Remove duplicates. Move every old A32NX copy outside all active add-on locations, including copies exposed through an add-on linker. Do not retain a manual installation alongside an Installer-managed one, and never merge Stable, Development or Experimental files into one folder.
- Remove custom liveries temporarily. An outdated, duplicated or deeply nested livery can cause missing textures or loading failures. Our A32NX livery structure and conflict checks explain what should remain after the aircraft itself works.
- Install one clean supported build. Prefer the FlyByWire Installer, select the intended simulator and choose a branch the Installer identifies as supported. If using a manual package, extract it fully rather than copying the archive.
- Run an isolated test. Leave only the clean A32NX package in Community, select its supplied livery, use a default airport and create a new flight. If it works, restore other add-ons in batches until the conflict returns.
What if there is no Community folder or the Installer shows no path?
A missing path normally means the package library was moved, its drive is unavailable or the Installer is targeting a different Microsoft Flight Simulator installation.
For MSFS 2020, the InstalledPackagesPath entry inside UserCfg.opt identifies the package library MSFS is using. Its Community subfolder is the correct destination. The location of UserCfg.opt varies with the PC installation, so verify the recorded path rather than relying on a folder found through a generic search.
Do not create a random Community folder beside the simulator executable, and never place the A32NX under Official. If the recorded drive is disconnected or the package library has moved, correct that underlying path first. Hidden Windows directories can also make a valid folder appear absent.
Why does the A32NX load with black screens?
If the 3D cockpit appears, the aircraft package has loaded; black displays usually mean the aircraft has no electrical power or the displays are dimmed.
- Switch on both batteries. Use the overhead electrical panel before expecting the cockpit systems to start.
- Connect an electrical source. Use available external power or start the APU and bring its generator online. A runway start is a quick way to test whether the cold-and-dark state is the only problem.
- Raise the display brightness. Check the relevant panel and instrument brightness controls instead of assuming every dark screen is a failed installation.
- Check the flyPad separately. The tablet has its own power control and can remain dark while the main cockpit displays are operating.
If every display remains blank during a powered runway start, remove panel, avionics and toolbar modifications before reinstalling the aircraft. SimBridge is not required for the A32NX to appear, load into a basic flight or power its normal cockpit displays.
What if the A32NX loading bar still hangs?
A repeatable loading hang after a clean installation usually indicates damaged files, an old saved-flight reference, an unavailable linked folder or another add-on conflict.
- Allow additional time for the first load after an aircraft or simulator update, but do not treat repeated freezes or desktop crashes as normal.
- Create a new flight with the supplied A32NX livery. An old save may reference a removed branch, aircraft state or livery.
- For the test, install directly into the active Community folder. External drives, symbolic links and add-on managers can point to a target that is no longer available.
- Check free storage space and security-software quarantine if files disappear or the Installer repeatedly downloads the same content.
- Remove airport, traffic, toolbar, avionics, livery and other aircraft packages. Restore half at a time after the A32NX works; this isolates a conflicting add-on faster than testing everything individually.
- If MSFS offers Safe Mode after a crash, remember that Community add-ons are disabled there. The A32NX being absent in Safe Mode is expected, not proof that another installation has failed.
What should I test if the A32NX still does not appear?
If there is still nothing in the selector after the obvious fix was not it, change one variable at a time and use the result to identify which layer is failing.
| Test result | What it means | Next action |
|---|---|---|
| A stock aircraft fails with Community empty | The problem is not specific to FlyByWire | Repair the simulator, base content or platform services before reinstalling A32NX again |
| Stock aircraft work, but A32NX is not listed when installed alone | MSFS is not detecting that package | Recheck the active path, folder depth, simulator compatibility and missing files |
| A32NX is listed but hangs when installed alone | The package may be incomplete, damaged or referenced by an old save | Remove it fully, install one clean supported build and start a new flight |
| A32NX works alone but fails after other add-ons return | Another Community package conflicts with it | Restore add-ons in progressively smaller batches until the culprit is identified |
| Files vanish after every reinstall | Storage, synchronisation or security software is interfering | Check the destination drive, available space and quarantine history |
If the aircraft appears but then freezes, crashes, loses controls or develops wider cockpit faults, use our broader A32NX failure and clean-reinstallation checks rather than repeating the same folder move.