Why is the EFB not working in MSFS 2024?
In Microsoft Flight Simulator 2024, the EFB usually fails because the panel has lost input focus, its control binding conflicts with another device, the cockpit tablet is unpowered, or the selected aircraft does not support route transfer. Restart the panel, test a stock aircraft, then isolate controls, power, online data and add-ons.
Which EFB problem do you have?
Match the symptom before changing settings, because the simulator’s Electronic Flight Bag and an aircraft developer’s custom tablet are separate systems.
| Symptom | Likely cause | First check |
|---|---|---|
| EFB will not open | Missing or conflicting binding, hidden panel or frozen interface | Search the controls for EFB or tablet commands and reopen the panel |
| Tablet is black | Tablet switched off, brightness at minimum or aircraft electrical power unavailable | Use its power and brightness controls, then energise the aircraft |
| EFB opens but cannot be clicked | Mouse, controller cursor or cockpit focus problem | Exit freelook, restore the cockpit cursor and test without duplicate bindings |
| Map or online data is blank | Online functionality, account authentication or service problem | Check the simulator’s data options and restart the signed-in session |
| Route will not enter the GPS or FMS | Route not sent, avionics unpowered or unsupported aircraft integration | Power the avionics and use the EFB’s route-to-avionics command |
| Only one aircraft is affected | Aircraft-specific tablet, package fault or incompatible add-on | Test a default aircraft using the standard MSFS 2024 EFB |
How do I fix an unresponsive EFB in MSFS 2024?
- Close and reopen the EFB. If that does not restore it, return to the main menu and reload the flight. Fully quit MSFS 2024 rather than resuming a suspended Xbox or PlayStation session.
- Test a default aircraft. Load a stock aircraft that provides the simulator EFB at a simple default airport. If it works there, the core EFB is healthy and the problem belongs to the original aircraft, livery or package.
- Restore input focus. Exit freelook or any active camera interaction, click back into the cockpit, and reopen the tablet. On a console, make sure controller cursor mode is active; on PC, temporarily disconnect extra mice, controllers or touch devices.
- Check EFB bindings. Search the controls assigned to every connected device for EFB, tablet and cursor actions. Remove duplicate assignments that make one button open the tablet while another command immediately closes it or captures the cursor. Our explanation of opening the EFB, restoring focus and using its planning controls covers the normal workflow.
- Check online functionality. If buttons work but maps, weather or cloud-synchronised plans are blank, confirm that online data is enabled and the simulator account is connected. Reinstalling the simulator will not fix a service-side interruption.
- Isolate add-ons. On PC, temporarily move third-party packages out of the
Communityfolder without deleting them, then restart the simulator. On Xbox or PlayStation, update or temporarily remove the affected aircraft or add-on package through the simulator’s content library.
A mistake we see constantly is changing graphics, rolling-cache and controller settings at the same time. Change one category, restart the flight and retest; otherwise, you cannot identify what actually fixed the EFB.
Why is the cockpit EFB black or powered off?
A cockpit-mounted tablet may depend on its own power button, brightness control or the aircraft’s electrical system, even when the simulator’s separate EFB panel remains available.
In a cold-and-dark aircraft, switch on the battery or approved ground power source and energise the avionics before testing the tablet. Check for a power button around the tablet bezel and raise its brightness. Aircraft-specific procedures differ, so do not assume every black tablet is a broken MSFS interface.
If the standard EFB is black in every default aircraft, the fault is more likely to be damaged simulator content, an interface add-on or a failed update rather than aircraft power.
Why will the EFB flight plan not transfer to avionics?
Creating or importing a route in the EFB does not always load it into the aircraft automatically; the avionics must be powered, and the aircraft must support the simulator’s route-transfer function.
- Finish the route and use the EFB command that sends it to the aircraft’s avionics. Filing it with ATC is a separate action.
- Wait until the GPS or FMS has completed its start-up before sending the route.
- Check the active flight plan page rather than judging the transfer only from the moving map.
- For an aircraft with custom avionics, use that aircraft’s own import method if the standard EFB transfer is unsupported.
If the route arrives but GPS fields, knobs or softkeys remain inactive, follow our checks for dead G1000 and FMS controls, power and input conflicts.
Can an external flight-planning tool cause the EFB problem?
External companion tools can fail to communicate with MSFS 2024, but they cannot normally prevent the built-in EFB from opening.
If the internal EFB works while an external tool reports that the simulator is disconnected, treat that as a SimConnect problem. Use our steps for checking and repairing SimConnect for MSFS tools rather than reinstalling the EFB or deleting your controller profile.
When should I repair or reinstall MSFS 2024?
Repair the installation only when the EFB fails in multiple default aircraft after a clean restart, input checks and add-on isolation.
Install pending simulator and content-package updates first. PC users can then use their platform’s file verification or repair facility; console users should remove and reinstall only the affected aircraft or content package before considering the entire simulator.
If opening the EFB freezes or closes MSFS 2024, diagnose it as a broader stability problem. Our guide to isolating MSFS crashes, incompatible add-ons and damaged package data covers that case. Avoid deleting cloud saves or control profiles unless there is clear evidence they are corrupted, because doing so can erase unrelated settings without repairing the EFB.