Why won't the FlyByWire A32NX load in MSFS?

The FlyByWire A32NX usually will not load in Microsoft Flight Simulator because the PC package is in the wrong Community folder, nested too deeply, duplicated, incomplete or conflicting with another add-on. Confirm the simulator and platform, remove every old copy, install one compatible build, then test it alone at a default airport.

Is the A32NX missing, hanging or merely unpowered?

The symptom tells you whether MSFS failed to discover the package, failed while loading it or loaded an aircraft that simply has no electrical power.

Does FBW work on PC (на ПК), Xbox or PlayStation?

The normal FlyByWire Installer and manually extracted Community package are for Windows PC and cannot be copied into the console versions of Microsoft Flight Simulator.

Installing the aircraft into MSFS 2020 does not install it into MSFS 2024, even when both simulators are on the same PC. Each simulator has its own package location.

FBW geht nicht, не появился, нету or “can’t find it”: how to restore a missing aircraft

When these phrases mean that the aircraft did not appear in the selector — “нет, не появился” — MSFS has almost always failed to discover the package rather than failed to fly it.

1. Check the aircraft selector. Clear manufacturer, aircraft-type and other filters, then search for FlyByWire or A32NX. The FlyByWire aircraft is a separate entry from the stock Airbus A320neo; selecting the stock aircraft does not test the installation.
2. Close MSFS completely. Do not move, merge or replace package files while the simulator is open. Close the FlyByWire Installer as well before manually removing an old package.
3. Identify the active Community folder. Multiple folders named Community are common after moving the simulator, changing drives or installing both simulator generations. For MSFS 2020, the InstalledPackagesPath recorded in UserCfg.opt identifies the package library being used; its Community subfolder is the relevant destination. Our MSFS 2020 installation and package-path walkthrough covers the different PC installations. For the newer simulator, use the separate MSFS 2024 installation checks.
4. Inspect the folder depth. The package folder should directly contain manifest.json and layout.json. A typical structure resembles Community/flybywire-aircraft-a320-neo/manifest.json. If those files are inside a second identically named folder, move the inner package up one level. A ZIP or other compressed archive left in Community will not load.
5. Remove every duplicate. Move old A32NX folders out of all active add-on locations, including copies exposed through an add-on linker. Temporarily remove A32NX liveries and older modifications for the stock A320neo. Do not merge files from Stable and another Installer branch into one package.
6. Install one clean build. Prefer the FlyByWire Installer and select the simulator and branch it identifies as supported. For fault-finding, use Stable when it is offered for that simulator. If the Installer reports a missing path, fails part-way through or repeatedly loses files, follow our checks for Installer paths, permissions, storage and stale packages.
7. Run an isolated test. Leave only the clean A32NX package in Community, use its supplied livery, choose a default airport and start a new flight rather than a saved one. If it loads, restore other add-ons in batches until the conflict returns.

What if there’s no path or no such a thing as the expected Community folder?

A missing path usually means the simulator’s package library was moved, the recorded drive is disconnected or the Installer is looking at a different MSFS installation.

Do not create a random Community folder beside the simulator executable and do not put the A32NX under Official. A folder with the right name is useless unless it belongs to the package location MSFS is actually reading. Hidden Windows directories can also make a valid path difficult to find without proving that it is absent.

If the package structure looks correct but no add-ons appear, use our Community-folder detection checklist to check compressed files, nesting, inactive folders and package conflicts.

Should I install both — «давай оба» — to be safe?

No: install one A32NX branch into one active Community folder for the simulator you intend to run.

If a second guessed location is “auch nicht” working, copying the package into both folders only makes diagnosis harder and can leave duplicate packages active through links or moved libraries. Verify the simulator’s real package path instead of installing Stable and Development together or copying one package into both MSFS 2020 and MSFS 2024.

Why does the A32NX load with black screens?

If the 3D cockpit appears, the aircraft has loaded; black displays usually indicate an unpowered cold-and-dark aircraft rather than a missing installation.

1. Switch on both batteries. The overhead electrical panel must be powered before the main systems can start.
2. Establish an electrical source. Connect available external power or start the APU and place its generator online. A runway start can help confirm whether the problem is merely the chosen aircraft state.
3. Check display brightness. Turn up the relevant cockpit display controls rather than assuming every dark screen is a software failure.
4. Check the flyPad separately. The tablet has its own power control and may remain dark while other cockpit systems are operating.

If the displays stay blank in a powered runway-start state, remove custom liveries, panel modifications and avionics-related add-ons before replacing the A32NX package again.

Does SimBridge need to be running for FBW to load?

No, SimBridge is not required for the A32NX to appear in the aircraft selector, load into a basic flight or power its normal cockpit displays.

SimBridge supports particular external and remote functions. Troubleshoot it only after the aircraft itself loads correctly.

What if the A32NX loading bar still hangs?

A repeatable loading hang after a clean installation usually points to a damaged package, a saved-flight reference, an add-on conflict or a wider simulator problem.

• Allow extra time for the first load after a simulator or aircraft update, but do not treat repeated freezes or desktop crashes as normal.
• Start a new flight with the supplied FlyByWire livery. An old saved flight may reference a removed branch, aircraft state or livery.
• Install directly into the active Community folder for the test. External drives, symbolic links and add-on managers can point to an unavailable target.
• Check free storage and security-software quarantine if the same files disappear after each installation.
• Remove airport, toolbar, avionics, traffic and livery packages as well as other aircraft. Restore half at a time after the A32NX works; this finds a conflicting package faster than adding them back individually.
• If MSFS offers Safe Mode after a crash, remember that third-party Community packages are disabled there, so the A32NX may be absent by design. Use Safe Mode to confirm the base simulator starts, then return to normal mode after cleaning up the add-ons.
• Test a stock aircraft with Community completely empty. If that also hangs, repair the simulator installation or its platform services rather than repeatedly reinstalling FlyByWire.