How do I transfer FsPassengers to a new FSX computer?

To transfer FsPassengers to a new FSX computer, back up its entire FsPassengers folder, install FSX and the correct FsPassengers edition afresh on the new PC, then restore the old Database folder and any custom content. Keep the new installation’s executable files, and reactivate with your legitimate licence details.

Which FsPassengers files must I back up?

The indispensable item is the Database folder inside the old FSX installation’s FsPassengers folder. It contains the linked records for pilots, companies, flights and economic progress, so copy the whole folder rather than selecting individual files.

For FSX and FSX: Steam Edition, the add-on is often called FsPassengersX, although its main folder is normally named FsPassengers. It sits beneath the FSX installation folder; the exact path depends on whether FSX is boxed, installed through Steam or located in a custom library.

• Back up the complete FsPassengers folder as your untouched safety copy.
• Preserve Database as a complete unit; do not merge its individual files with a newly created database.
• Save custom content, including any payload models, airline logos, crew sound packs and configuration changes you added.
• Keep the installer and licence details separately. The database does not transfer the programme’s activation.

FsPassengers does not include the aircraft it refers to. Back up or retain the installers and licences for any add-on aircraft used by your company as well. Our FSX backup checklist explains the other settings, saved flights and add-on folders worth preserving.

What is the safe FsPassengers transfer order?

The reliable order is FSX first, FsPassengers second and the saved database last. Copying the old add-on directly into an unprepared FSX installation can leave its module registration, dependencies or installation path incorrect.

1. Close FSX on the old computer. Copy the entire FsPassengers folder to two safe locations if possible. Confirm that the copied Database folder contains files with dates matching your latest flights.
2. Install FSX on the new computer. Start it once, load a basic flight and close it. If the whole simulator is being moved, follow the safe FSX reinstall and selective-restore sequence rather than copying the old FSX directory wholesale.
3. Install the correct FsPassengers build. Use the legitimate installer intended for the target FSX edition. Prefer the same build used on the old PC or a later build documented as able to read its database; never open a newer database with an older release.
4. Test the clean installation. Start FSX and confirm that FsPassengers appears and opens. Fix an installation or compatibility problem before restoring any career data.
5. Close FSX and preserve the clean database. Rename the newly created Database folder to something such as Database.clean.
6. Restore the old database. Copy the backed-up Database folder into the new FsPassengers folder. Copy custom payload models, logos and sound packs separately, but retain the executable and module files installed on the new PC.
7. Reactivate and verify. Enter the original registration details through the add-on’s normal unlock procedure, then check the company list, pilots, flight history, money and fleet before flying.

Configuration files are best restored selectively, particularly when the Windows version, FSX edition or FsPassengers build has changed. An old option file can contain paths or settings that are wrong for the new installation.

Can I move FsPassengers from boxed FSX to Steam Edition?

The saved career database may be transferable, but the boxed-FSX programme files should not be copied into FSX: Steam Edition. Install a FsPassengers build and licence that support Steam Edition, then restore only the database and compatible custom content.

Installers, modules and activation can differ between editions. Check what changes when moving FSX add-ons to Steam Edition before attempting a cross-edition migration.

Why are my FsPassengers pilots or companies missing?

Missing pilots or companies usually mean that FsPassengers is reading a different Database folder from the one you restored. Check these common causes:

• Nested folders: the copied path has accidentally become FsPassengers\FsPassengers\Database instead of FsPassengers\Database.
• Wrong FSX installation: boxed FSX and Steam Edition are both installed, but the database was copied into the inactive installation.
• Windows VirtualStore: an older installation under a protected Program Files folder may have written its live data beneath %LOCALAPPDATA%\VirtualStore. Search there for another FsPassengers\Database folder and compare its file dates.
• Partial database copy: individual files were merged or omitted. Restore the complete original Database folder as one unit.
• Version mismatch: an older FsPassengers build cannot understand data last opened by a newer one. Stop and restore the untouched backup before trying a compatible build.

Why does FsPassengers not appear in FSX?

If FsPassengers is absent from FSX, the base installation has failed independently of the saved database. Re-run the appropriate installer against the active FSX folder and check whether security software quarantined an installed module; repeatedly copying old DLLs rarely fixes the underlying path or compatibility problem.

Why are company aircraft unavailable after the move?

Company records do not reinstall the aircraft themselves. Reinstall the required aircraft through their proper installers and restore any matching custom payload models; a changed aircraft configuration or title can also prevent the expected payload model from being selected.

Keep the untouched old database until several flights have saved correctly on the new computer. Avoid alternating between elevated and normal FSX launches, because Windows can then maintain separate real and VirtualStore copies of the same FsPassengers data.