Find why FSX missions are missing and restore default or downloaded missions by fixing folders, filters, permissions or damaged game files.
FSX missions usually disappear because their folders were deleted, installed into the wrong FSX copy, nested one level too deep, blocked by damaged Windows permissions or hidden by a mission-list filter. Check the active installation’s Missions folder first, then fix its layout or repair or verify FSX to restore default files.
What does the missing-mission pattern tell you?
The missions affected usually identify the fault before you change anything.
| Symptom | Likely cause | Best next step |
|---|---|---|
| Every mission is missing | Wrong or empty Missions folder, an active filter or damaged default files | Check the active FSX installation and repair its files |
| Only downloaded missions are missing | Wrong installation path or incorrect extracted folder structure | Move or reinstall the mission under the correct category folder |
| Only certain default missions are missing | Deleted or modified files, or missing expansion content in boxed FSX | Repair the relevant FSX installation or expansion |
| A mission is listed but will not start | Corrupt mission files or a missing aircraft, scenery or other dependency | Reinstall that mission and check its documented requirements |
Where should FSX missions be installed?
Installed missions belong under the Missions directory beside fsx.exe, not in the Documents flight-files folder or SimObjects.
Typical default locations are:
- Boxed FSX:
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Missions - FSX: Steam Edition:
C:\Program Files (x86)\Steam\steamapps\common\FSX\Missions
Those are examples only. A custom Steam library, another drive or a manually selected boxed-FSX directory changes the path. If boxed FSX and Steam Edition are both installed, confirm which folder contains the fsx.exe you actually launch.
The normal hierarchy is FSX\Missions\Category\Mission Name\mission files. A mission folder commonly contains a flight file, weather file, an .SPB or .XML mission definition and supporting images, sounds or briefing files.
How do I restore missing FSX missions?
Restore missions by checking the selector, confirming the active installation and then repairing only the part that is actually missing.
- Reset the mission selection. Open FSX’s Missions screen, select all missions or the appropriate category, and remove any active skill, status or category filter. Restart FSX after changing files because its existing mission screen may not refresh immediately.
- Locate the active FSX folder. For Steam Edition, use Steam’s option to browse the installed files. For boxed FSX, inspect the shortcut target or locate the
fsx.exebeing launched. Do not assume the first FSX directory found is the active one. - Inspect the Missions directory. Check that category folders contain individual mission folders. Correct duplicated levels such as
Missions\Missions\CategoryorMission Name\Mission Name\files. - Restore official files. In Steam, run the installed-files integrity verification. For boxed FSX, use the repair option from the original installation media. If only Acceleration missions are absent from a boxed installation, repair the expansion rather than treating them as base-FSX missions.
- Test one known mission. Restart FSX and open an official mission before reinstalling multiple downloads. If the default mission appears, the catalogue works and the remaining problem is with the add-on packages or their paths.
Back up third-party mission folders before repairing. Steam verification restores recognised official files but will not recreate downloaded missions, while a boxed repair may replace modified default content. Our FSX repair and file-verification guidance for Windows covers the broader recovery process.
Why are downloaded FSX missions not showing?
Downloaded missions usually fail to appear because the archive’s outer wrapper folder was copied instead of the actual mission folder.
Open the extracted package and find the directory containing the mission’s .FLT and .SPB or .XML files. Place that directory inside a suitable category under Missions; do not create Missions\Missions, and do not separate its sounds, images or briefing assets.
Some packages include aircraft, scenery or effects that have separate destinations. Follow the included documentation rather than putting every extracted file under Missions. We explain the layouts and common installer errors in our FSX mission installation instructions.
If an installer reports success but nothing appears, search both FSX installations for the mission name. Installers often follow the boxed or Steam registry entry rather than the copy you launch. Correcting the detected path is safer than repeatedly reinstalling; use our FSX registry-path repair procedure when several installers consistently select the wrong directory.
What if the mission files exist but FSX cannot see them?
If the files are correctly placed yet remain unreadable, check folder permissions and the mission package itself.
- Confirm your Windows account can read the mission folder and its files.
- Check that the files were fully extracted and are not still inside a ZIP archive.
- For one affected download, remove its folder and extract a fresh copy rather than renaming individual mission files.
- If running FSX once as administrator makes the missions appear, treat that as evidence of a permissions fault rather than a permanent fix.
Damaged access control on the FSX directory can also stop installers from writing complete packages. The simulator includes a utility for this specific class of problem; our explanation of ResetXDirectorySecurity.exe and when to use it covers the precautions.
A mission that appears in the list but fails during loading is not a catalogue problem. Reinstall that individual mission, confirm its required aircraft and scenery are present, and preserve the folder and file names supplied by its author.