Why is the FlyByWire A32NX EFB not working in MSFS?

The FlyByWire A32NX EFB usually stops working because the wrong aircraft or package is loaded, the flyPad is switched off, an old duplicate installation is conflicting, or cockpit input has lost focus. In Microsoft Flight Simulator, verify the aircraft first, power-cycle the tablet, then clean-install the correct A32NX package if needed.

Match the EFB symptom to the likely cause

The exact symptom usually identifies whether the fault is power, input, installation or an individual EFB service.

Why is the A32NX flyPad black or missing?

A missing or permanently black flyPad normally means the wrong aircraft is loaded or the A32NX package has not loaded correctly.

1. Verify the aircraft. Select the aircraft whose title explicitly says FlyByWire A32NX. Applying an A32NX-style livery to a stock A320 does not add the FlyByWire cockpit or EFB.
2. Power-cycle the flyPad. Use the power control on the tablet bezel, wait briefly and switch it on again. If the screen is merely very dim, restore its brightness. Establish aircraft battery or external power as well; if every cockpit display is dark, the problem is aircraft power rather than the EFB alone.
3. Restart Microsoft Flight Simulator fully. Returning to the main menu may leave a faulty instrument package in memory. Exit the simulator before changing add-on files.
4. Remove duplicate installations. Use the FlyByWire Installer to remove the installed A32NX, then check Community for an older manually installed copy. Do not merge a fresh package into an existing aircraft folder, and do not keep stable, development or experimental copies installed together.
5. Install the package for the correct simulator. Follow our clean A32NX installation checks for MSFS 2020 or the correct A32NX package procedure for MSFS 2024. Do not assume a package copied from MSFS 2020 is suitable for MSFS 2024.
6. Confirm the active Community folder. Multiple simulator installations can leave an old or unused Community folder behind. Check that the installer is writing to the packages location used by the simulator.
7. Run an isolated test. Leave only the A32NX installed, use its standard livery and start a new flight rather than opening a saved flight. If the EFB works, restore other aircraft, liveries and cockpit mods in batches until the conflict returns.

Clearing the scenery rolling cache rarely repairs an A32NX instrument, and reinstalling the entire simulator should be a last resort. The aircraft package and conflicting Community add-ons are the useful places to investigate first.

Why can I see the flyPad but not click it?

A visible flyPad that ignores clicks has usually loaded correctly; the fault is more likely to be cockpit input focus or a controller binding.

1. Restore mouse focus. Click an empty part of the cockpit, pause and resume the flight, then try the flyPad with a normal short left click.
2. Close competing interfaces. Shut any toolbar panel, pop-out instrument or controller cursor that may be holding focus.
3. Test with other devices disconnected. A held gamepad control, VR pointer or duplicated primary-action binding can prevent mouse interaction. Disconnect optional controllers temporarily rather than changing every binding at once.
4. Try the alternate cockpit interaction mode. Microsoft Flight Simulator offers different cockpit interaction systems, although the menu location differs between MSFS 2020 and MSFS 2024. Change the mode, reload the flight and test again.
5. Check the rest of the cockpit. If switches, MCDU keys and other displays are also unresponsive, repair the input profile or aircraft installation. If only the flyPad fails, power-cycle it and perform the isolated Community-folder test.

Why does SimBrief import fail when the EFB works?

If ordinary flyPad pages respond but SimBrief does not import, the EFB itself is working and reinstalling the aircraft is unlikely to be the first fix.

• Generate a fresh operational flight plan after making route or aircraft changes.
• Enter the identifier requested by the installed flyPad version, commonly the numeric Pilot or User ID. Do not assume that an account display name will be accepted in the same field.
• Confirm that Microsoft Flight Simulator has an internet connection and its online functionality is enabled.
• Remember that importing the operational flight plan into the EFB and requesting the route through the MCDU can be separate actions. An OFP visible on the tablet does not always mean the route has been inserted into the flight-management system.

Once imports work, our flyPad setup and operating walkthrough explains the normal route, performance, fuel and payload workflow.

Why do the fuel and payload controls appear stuck?

Fuel and payload figures often appear frozen because the EFB has accepted a target but the simulated loading process has not started or is progressing at a realistic rate.

• Set the required target and use the page's apply, board or start action where shown.
• Check whether instant, fast or realistic loading is selected. With realistic loading, the displayed total changes gradually.
• Secure the aircraft and stop the engines where the selected ground service requires it.
• Use either the flyPad, the simulator's weight-and-balance interface or a ground-service add-on to control loading—not several at once. Competing systems can repeatedly overwrite the same values.
• If the buttons do not react at all, return to the input-focus checks. If the buttons react but the totals later revert, another loading system or add-on is probably overriding the EFB.