Fix FlyByWire Installer errors in MSFS by correcting the Community path, clearing stale packages, and solving download or permission failures.
To fix FlyByWire Installer errors in Microsoft Flight Simulator, close the sim, select the correct simulator version, point the Installer to the active Community folder, remove stale FlyByWire copies, then retry a clean install. Download failures usually need free disk space, an updated Installer, or a firewall or antivirus permission.
The quickest reliable FlyByWire clean-install procedure
A clean reinstall works only after the wrong path, locked files and duplicate packages have been ruled out.
- Close Microsoft Flight Simulator and the FlyByWire Installer. Check Task Manager if Windows still has either program running in the background.
- Confirm the selected simulator. MSFS 2020 and MSFS 2024 use different package locations. Do not install a 2020 package into the 2024 Community folder or copy an Installer-managed package between them.
- Verify the active Community folder. Do not rely on the first folder returned by Windows search. Our guide to identifying the Community folder used by the running simulator covers Microsoft Store, Steam and custom package locations.
- Uninstall the aircraft through the Installer. Afterwards, inspect the active Community folder and remove only a clearly identified, stale FlyByWire aircraft package left behind by that uninstall. Do not delete unrelated liveries, profiles or simulator files.
- Restart Windows if files were locked. This releases package folders that the simulator, an antivirus scanner or another utility may still be holding open.
- Update and reopen the Installer. Select the correct simulator and use the Stable branch for the first test. Let the download and extraction finish before launching MSFS.
- Test without other add-ons. Temporarily move unrelated Community packages elsewhere. Once the aircraft loads, restore them in groups to find any conflict.
For the normal package-selection sequence, follow our complete A32NX setup steps for MSFS 2020. MSFS 2024 users should instead use the MSFS 2024-specific package and installation checks.
Why can't the Installer find my Community folder?
The Installer usually cannot find MSFS because the wrong simulator profile is selected or the package location was moved after installation.
In MSFS 2020, the final InstalledPackagesPath entry in UserCfg.opt identifies the package root. The active Community folder sits inside that location alongside Official. Never point the Installer at Official.
If you have both simulator generations installed, each has its own active location. A common mistake we see is correcting the path for MSFS 2020 while the Installer is configured for MSFS 2024, or vice versa. Custom drives and previous installations can also leave unused Community folders that look valid but are never read by the sim.
What does each FlyByWire Installer error usually mean?
The wording of the error usually identifies whether the failure is caused by the path, network connection or Windows file permissions.
| Error or symptom | Likely cause | What to do |
|---|---|---|
| Simulator not detected or path not found | Wrong simulator selected, moved package directory or obsolete Community path | Select the correct MSFS version and enter its active Community location. |
| Download failed, network error or checksum failure | Interrupted transfer, blocked connection or damaged partial download | Update and restart the Installer, retry on a stable connection, and allow the trusted Installer through any firewall or security filter. |
| Access denied, extraction failed or files cannot be written | Locked files, restrictive folder permissions, Controlled Folder Access or insufficient space | Close the sim, check permissions and free space, then retry. Allow the specific Installer rather than disabling antivirus protection globally. |
| Link, junction or symbolic-link error | Unsupported drive format, network or synchronised folder, or inadequate permissions | Use an ordinary writable folder on a local NTFS drive and remove any broken link left by the failed installation. |
| Update or removal remains stuck | A simulator process is using the package, or two branch copies conflict | Close all related processes, restart Windows, uninstall through the Installer and remove only the confirmed stale package. |
Keep free space on both the destination drive and the Windows temporary-files drive. Downloading and unpacking can require substantially more working space than the final installed package.
Why is the A32NX missing after a successful installation?
A successful Installer message confirms that files were written, not that Microsoft Flight Simulator loaded the same folder.
- Wrong Community folder: verify the active path again, especially after moving MSFS to another drive.
- Safe Mode: third-party Community packages are disabled when MSFS starts in Safe Mode.
- Nested package folder: the package's
manifest.jsonmust not be buried inside an extra duplicate folder level. - Duplicate branch or old manual copy: retain only the package managed by the Installer.
- Disabled package: check that the aircraft has not been disabled in the simulator's package or library manager.
- Add-on conflict: test with every unrelated Community package temporarily removed.
Do not start MSFS while the Installer is still extracting or updating the aircraft. The simulator may scan an incomplete package and then omit it from the aircraft selector.
Should I run the FlyByWire Installer as administrator?
Running as administrator may diagnose a permission problem, but it should not be the permanent fix for an ordinary installation.
Correct the destination folder's permissions instead. Mixing administrator-owned files with a standard Windows account can make the next update or removal fail. If Windows Controlled Folder Access blocked the Installer, permit that trusted application specifically rather than switching off the protection for every program.
Can the FlyByWire Installer work on Xbox or PlayStation?
The FlyByWire Installer is a PC desktop tool and cannot place packages into the Xbox or PlayStation versions of Microsoft Flight Simulator.
Console storage is not exposed as a PC-style Community folder, so changing paths or reinstalling the desktop Installer cannot solve that limitation. This troubleshooting process applies to the Windows versions of MSFS 2020 and MSFS 2024.