FlightGear won't install? Diagnose blocked, corrupt, incompatible or mismatched packages and apply the right fix on Windows, macOS or Linux.
FlightGear usually will not install because the package is incomplete, made for a different operating system or processor, blocked by security controls, or unable to write to its destination. Download the correct package again, remove the failed copy, use a local writable folder, and keep the FlightGear program and data versions matched.
What causes a FlightGear installation failure?
The failure point usually reveals the cause more accurately than the final error message.
| Symptom | Likely cause | What to do |
|---|---|---|
| The installer never opens | Wrong package, damaged download or operating-system security block | Check the platform and processor type, download a fresh copy and inspect the security warning |
| Installation stops while extracting | Insufficient temporary space, corrupt archive, anti-virus quarantine or an unwritable path | Free space on both the system and destination drives, then retry in a local folder |
| Permission denied or access denied | The account cannot write to the destination or temporary directory | Use a folder owned by your account, or approve elevation only when the operating system requests it |
Installation finishes, but FlightGear cannot find defaults.xml | FGData is missing, mismatched or being overridden by an old data path | Match the program and data releases and remove an obsolete FG_ROOT override |
| A launcher appears, but the simulator closes | This is normally a launch, graphics, configuration or aircraft problem rather than installation failure | Test a clean launch before reinstalling |
How do I fix FlightGear not installing?
A clean, verified installation fixes most failures, but only if the incomplete package and its leftover files are removed first.
- Identify the exact failure stage. Record the complete error message and whether it appeared during download, package opening, extraction, installation or first launch. These are separate problems and require different fixes.
- Confirm the package matches the computer. Check the operating system and processor architecture. A Windows installer will not work on macOS or Linux, and an incompatible processor build may be rejected before installation starts.
- Download the package again. Delete the partial installer first rather than resuming it. If a checksum is supplied with the package, compare it before opening the file.
- Remove the failed installation. Use the operating system's uninstall facility if FlightGear is registered there, then rename or remove the incomplete destination folder. Back up custom aircraft, liveries and scenery before deleting anything.
- Check free space in both locations. Installation may require space in the temporary directory as well as the final FlightGear folder. A nearly full system drive can stop extraction even when the destination drive has ample room.
- Choose a simple local destination. Avoid installing into a cloud-synchronised folder, network share, read-only directory or removable drive while troubleshooting. These locations commonly introduce permissions and file-locking problems.
- Handle security warnings safely. Verify that the package came from the official project distribution before allowing it. Do not disable anti-virus or operating-system protection permanently; if package integrity cannot be established, do not bypass the warning.
- Install with normal account permissions first. Approve administrator access only if the installer requests it. On Linux, let the package manager handle elevation rather than running the entire graphical application as root.
- Make the first launch completely standard. Do not add aircraft, scenery, custom command-line arguments or old data paths until the included aircraft loads successfully.
Which installation method should I use?
Use the native installation method for your operating system and avoid mixing files from different distribution methods.
- Windows: Use the matching Windows package and follow our verified PC installation sequence. Do not copy a new release over an older installation directory.
- macOS: Use the appropriate application package and install it from the disk image as described in our macOS installation and Gatekeeper guidance.
- Linux: Choose either a distribution package or Flatpak and keep its program and data dependencies together. Our Linux package and Flatpak instructions cover repository, dependency and permissions failures.
A mistake we see constantly is combining an executable from one release with FGData from another. Package-managed installations should remain under package-manager control; manually replacing individual files can create a setup that appears installed but cannot start.
What if FlightGear installs but will not start?
If the FlightGear launcher opens, the installation has normally completed and the next fault lies in its data path, configuration, graphics support or selected aircraft.
An error mentioning defaults.xml, FGData or missing aircraft files points to an absent or mismatched data directory. Follow our FGData and missing-file repair steps rather than repeatedly running the installer.
Graphics drivers rarely prevent the package itself from installing, but they can cause a blank window or immediate exit at first launch. Test the bundled aircraft with default settings and no add-ons before changing graphics options or importing an old configuration.
Do I need to reinstall FlightGear completely?
Reinstall only when the download is damaged, core files are missing, or the program and FGData releases do not match.
A reinstall is unlikely to fix a bad aircraft, scenery path, controller assignment or graphics setting unless the old configuration is also isolated. Preserve custom content, rename the existing user configuration instead of deleting it, and test the clean installation before restoring files one group at a time.