Fix FSX controller settings that reset on restart by rebuilding Standard.xml, checking permissions, USB identity and duplicate bindings.
FSX usually fails to save controller settings because its per-user Standard.xml controls file is corrupt, read-only or unwritable, or because Windows has re-identified the joystick after a USB change. Back up and rebuild that file, bind one device at a time, then close FSX normally and retest.
In both Microsoft Flight Simulator X (FSX) and FSX: Steam Edition, reinstalling the simulator is rarely the right first step. Controller assignments live in your Windows user profile, so damaged or unwritable settings may survive an installation repair.
What causes FSX controller assignments to reset?
The pattern of the failure usually identifies the cause.
| Symptom | Likely cause | Best action |
|---|---|---|
| Every new assignment disappears after restarting FSX | Standard.xml is corrupt or cannot be written | Check permissions, then rebuild the file |
| Bindings disappear after moving a USB cable or changing a hub | Windows has presented the controller as a different device | Reconnect it consistently and assign the new device entry |
| Bindings remain, but axes or buttons behave incorrectly | Duplicate assignments exist on another controller | Remove overlapping axes and buttons |
| Only one complex add-on aircraft is affected | The aircraft or an add-on utility uses its own control system | Configure that system and remove conflicting FSX bindings |
If the joystick does not register at all, rather than merely losing saved bindings, work through our FSX joystick and throttle detection checks first.
Where does FSX store controller settings?
Native FSX controller assignments are normally stored in a per-user file named Standard.xml.
- Boxed FSX commonly uses
%APPDATA%\Microsoft\FSX\Controls\Standard.xml. - FSX: Steam Edition commonly uses
%APPDATA%\Microsoft\FSX-SE\Controls\Standard.xml.
Steam Edition can use the FSX folder instead of FSX-SE, depending on installation history and whether boxed FSX was present. Check both folders and compare the modification dates after closing the simulator. Do not confuse this user file with anything inside the main FSX installation directory.
How do I rebuild FSX Standard.xml safely?
The safest repair is to rename the existing file and let FSX generate a clean replacement.
- Close FSX completely. Also allow Steam Edition to finish shutting down before changing its files.
- Open the active Controls folder. Enter
%APPDATA%\Microsoft\in File Explorer and inspect theFSX\ControlsandFSX-SE\Controlsfolders. - Back up the controls file. Copy
Standard.xmlsomewhere safe, then rename the original toStandard.old.xml. This preserves your old assignments for reference. - Check that the folder is writable. Try creating and deleting a temporary text file there. If Windows refuses, give your account permission to modify the folder. If
Standard.xmlitself is marked read-only, clear that attribute. - Launch FSX and enable controllers. Open the Controls settings page, select the correct device and assign one obvious button plus one axis as a test.
- Remove duplicate axis assignments. Throttle, aileron, elevator and rudder axes are often assigned automatically to several connected devices. Keep each flight axis on only the intended controller.
- Close FSX normally and reopen it. If the test bindings remain, rebuild the rest of the profile gradually rather than copying the damaged XML file back.
If FSX does not create a fresh Standard.xml, the active Windows profile cannot write to that folder or you repaired the inactive FSX configuration folder. Correct the permissions rather than relying permanently on “Run as administrator”, which can hide the underlying profile problem.
Why do FSX controls disappear after changing USB ports?
FSX associates assignments with the device identity supplied by Windows, so a controller that is re-enumerated may be treated as a new device even though its name looks unchanged.
Connect the joystick, throttle and pedals before starting FSX, use the same USB ports where practical, and avoid unplugging them while the simulator is running. If Windows creates a new device entry, select it in FSX and reassign the controls; editing the old XML entry by hand is more error-prone than rebuilding the mapping.
Manufacturer utilities and control add-ons may store assignments separately. FSX mappings will not replace those profiles, and duplicate assignments between the two systems can produce unwanted movement that looks like a saving failure.
What if every FSX setting resets?
If graphics options, realism settings or saved flights also disappear, the fault is broader than the controller file and usually involves profile permissions, configuration corruption or security software blocking writes.
Use our guide to repairing FSX settings and saved-flight storage rather than repeatedly rebuilding Standard.xml. Controller-only resets point to the controls file or USB device identity; simulator-wide resets point to the wider FSX user configuration.