FSX won't save settings or saved flights? Fix the correct profile folders, read-only files, Windows security, OneDrive and a corrupt FSX.cfg.
FSX normally fails to save settings or saved flights because its user-profile folders are read-only, blocked by Windows security, redirected by OneDrive, or damaged. Check the active FSX.cfg and Documents save folder, restore write access, then test a new flight after closing FSX normally.
Where does FSX store settings and saved flights?
FSX and FSX: Steam Edition store settings and flights separately, so one can work while the other fails.
| Data | Usual location | What it contains |
|---|---|---|
| General settings | %APPDATA%\Microsoft\FSX\fsx.cfg | Graphics, realism, display and many general simulator options |
| Steam Edition profile | %APPDATA%\Microsoft\FSX-SE\fsx_se.cfg when Steam uses a separate profile | The Steam-specific equivalent of FSX.cfg |
| Controller settings | The Controls folder under the active FSX or FSX-SE profile | Assignments and calibration profiles, commonly including Standard.xml |
| Saved flights | The FSX flight-files folder inside the active Windows Documents folder | .FLT files and their companion state and weather files |
A standalone Steam installation may retain the original FSX folder and filename, while a side-by-side boxed and Steam installation can use FSX-SE. Saved flights are normally under Flight Simulator X Files or a Steam Edition-named equivalent. Run shell:Personal from the Windows Run box to open the Documents location FSX is actually using rather than assuming it is under a particular drive or user path.
How do I make FSX save changes again?
- Back up the active profile first. Preserve the configuration, controls and flight files before renaming or changing anything. Our guide to FSX's separate backup locations identifies the relevant boxed and Steam Edition folders.
- Identify the profile FSX is actually using. Close FSX, open
%APPDATA%\Microsoft, and inspect theFSXandFSX-SEfolders. Do not edit both copies blindly; use the one associated with your installation and showing recent activity. - Check write access. Open the properties of the active
fsx.cfgorfsx_se.cfgand clear its Read-only attribute. Then try creating and deleting a small text file in both the profile folder and the saved-flight folder. If Windows refuses, give your Windows account Modify permission rather than granting unrestricted access to Everyone. The filled Read-only box shown on a folder is not a reliable permissions test because Windows also uses it for folder customisation. - Check Windows security software. Controlled folder access can block the older
fsx.exeprogram from writing to Documents. Review its protection history and, if FSX was blocked, permit the genuine executable from your installation. Do not leave ransomware protection disabled as a permanent workaround. - Resolve Documents redirection. If
shell:Personalopens a OneDrive-backed or network folder, confirm that it is available, synchronised and writable. A mistake we see often is checkingC:\Users\name\Documentswhile Windows has redirected the real Documents folder elsewhere. - Rebuild a damaged configuration. With FSX closed, rename the active configuration to a backup name, such as
fsx.cfg.bak, and launch the simulator. FSX should generate a clean file. This resets simulator options and may require add-ons to be trusted again; our safe FSX.cfg reset procedure explains what to preserve. - Run a controlled test. Change one obvious setting, save a flight under a simple unique name, exit FSX through its menu, and wait for it to close fully. Reopen it and check both the setting and flight. Also inspect the files' modified times to see which location was written.
If permissions throughout the installation or user folders have been altered, review what ResetXDirectorySecurity.exe repairs and when it is appropriate. It should not be used as a substitute for identifying the blocked folder.
What does the exact symptom tell me?
The part that fails usually identifies the file or folder at fault.
| Symptom | Most likely cause |
|---|---|
| Settings reset, but flights remain available | The active configuration is read-only, corrupt, or being replaced by a tuning utility |
| Flights disappear, but settings persist | The Documents folder is redirected, unwritable or blocked by Controlled folder access |
| A flight loads manually but will not remain the default flight | The flight files work, but FSX cannot update its startup setting in the configuration |
| Only controller assignments reset | The XML file in the active Controls folder is blocked or damaged |
| Only an add-on aircraft's cockpit state resets | The aircraft uses its own panel-state system or does not store every custom system in an FSX saved flight |
| Nothing persists | A profile-wide permissions problem, security block, wrong Windows account or forced FSX shutdown |
Some older optimisation instructions deliberately mark FSX.cfg as read-only to freeze tweaks. That also prevents legitimate settings changes. Remove the attribute while editing settings and do not restore it unless you specifically need a locked configuration.
Why is an FSX saved flight missing or incomplete?
A saved flight is not the same thing as a saved flight plan. The flight planner's plan file records the route, while Save Flight records the simulator situation, aircraft and associated state.
FSX can create several companion files for one saved flight, including .FLT, .FSSAVE and .WX files. Keep those files together when copying a flight. Complex add-on aircraft may still require their own panel-state or scenario-loading feature because FSX's native format cannot reproduce every custom system.
Will reinstalling FSX fix the saving problem?
Reinstalling FSX rarely fixes this fault because the troublesome configuration and saved-flight folders sit outside the main installation directory. A Steam file verification or boxed-edition repair may leave the same read-only file, redirected Documents path or damaged user profile untouched.
If both locations remain unwritable after correcting permissions, test FSX from a separate Windows user account. A clean account creates a fresh per-user FSX profile and helps distinguish Windows-profile damage from a simulator installation problem.