Skip to content
FSX & FSX: Steam Edition 8 min read 260 views

Why won't FSX save my controller settings?

Ian Stephens
In short

Learn why FSX will not save controller settings and how to rebuild Standard.xml, fix permissions, USB identity changes and duplicate assignments.

FSX and FSX: Steam Edition usually will not save controller settings when active per-user Standard.xml is corrupt, read-only or blocked from writing. Back up and rebuild the file, test one controller at a time, keep devices on consistent USB ports, then close FSX normally and confirm the assignment survives a restart.

Reinstalling FSX is rarely the right first step. Native control assignments live in your Windows user profile, outside the main simulator installation, so an installation repair can leave the damaged or unwritable controls file untouched.

Is FSX failing to save, or is the controller not responding?

An assignment that disappears after restarting FSX indicates a saving problem; an assignment that remains listed but produces no response indicates an input, conflict or aircraft problem.

What happensLikely causeNext action
New bindings vanish after restarting FSXStandard.xml is corrupt, read-only or unwritableBack up and rebuild the active file
Bindings remain listed but do nothingControllers are disabled, the wrong device is selected, or another control system has priorityCheck detection and test a default aircraft
Assignments reset after changing a USB portWindows has identified the controller as a new deviceUse a consistent connection and map the new device entry
Axes jump, drift or fight each otherThe same axis is assigned to multiple devicesRemove duplicate assignments and calibrate the intended device
Only one add-on aircraft is affectedThe aircraft or separate controller software handles input differentlyCheck that system and remove overlapping FSX assignments
Graphics, realism settings and saved flights also resetThe wider FSX user profile cannot be writtenRepair the profile rather than only the controls file

If the assignment remains visible but the joystick or throttle does not work, use our controller detection, axis and duplicate-input checks. Rebuilding Standard.xml repeatedly will not repair a device that Windows cannot detect.

Where does FSX save controller settings?

FSX normally stores native controller and keyboard assignments in Standard.xml inside the active Windows user's roaming profile.

  • 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, particularly where boxed FSX has also been installed or the installation history has changed. If both folders exist, inspect both rather than assuming that the folder name proves which one is active.

Paste %APPDATA%\Microsoft into File Explorer's address bar to open the correct roaming-profile area, even when AppData is hidden. Do not search only under the FSX installation in Program Files; per-user assignments are not normally stored there.

Compare the folders' contents and modification dates after closing FSX normally. The active Standard.xml should receive a newer timestamp when a control change is successfully written. If neither copy changes, FSX may be using another Windows account or may be blocked from writing to the profile.

How do I rebuild FSX Standard.xml safely?

The safest repair is to move the active controls file out of its folder and allow FSX to generate a clean replacement. This resets custom controller and keyboard assignments, which is why a backup comes first.

  1. Close FSX completely. Do not move or edit the file while the simulator is running, because FSX may overwrite it when the session ends.
  2. Open the possible profile folders. Check both %APPDATA%\Microsoft\FSX\Controls and %APPDATA%\Microsoft\FSX-SE\Controls if they exist.
  3. Back up Standard.xml. Copy it to a safe location outside the Controls folder, then move the original out of that folder. Do not delete your only copy.
  4. Confirm that the folder is writable. Create and delete a temporary text file in the Controls folder. If Windows refuses, correct the permissions for the account that runs FSX. A folder's read-only box is not a dependable test, but the read-only attribute must be cleared from Standard.xml itself.
  5. Test the hardware in Windows. Run joy.cpl and verify that the device appears and its buttons and axes move. If it fails here, resolve the connection, power or driver problem before changing FSX files.
  6. Start FSX with one flight controller connected. Confirm that controllers are enabled, select the intended device in the Controls settings and make one obvious button assignment plus one axis assignment.
  7. Leave the Controls screen and exit normally. Do not end FSX through Task Manager or use a crashed session as the save test.
  8. Restart FSX and inspect the same device. If both test assignments remain, the new file is saving correctly.
  9. Reconnect the remaining hardware gradually. Examine every device because FSX may automatically assign aileron, elevator, rudder and throttle axes to each suitable controller it discovers.

A regenerated Standard.xml can contain default assignments before you add anything manually. That is normal. A common mistake is to leave rudder mapped to both twist input and pedals, or throttle mapped to both a yoke lever and a separate quadrant.

Do not copy the complete old XML file back after proving that the replacement works; doing so can restore the original corruption. Rebuild assignments gradually, referring to the backup only as a record.

How can I prove that FSX saved the new assignment?

The setting is saved when it remains under the same controller after a complete FSX restart and the active Standard.xml has a newer modification time.

  • Select the correct controller from the device list; two entries can have similar names.
  • Test in normal flight with a default aircraft, not only in Slew mode or a complex add-on aircraft.
  • Make one change at a time so that a new default or duplicate assignment is easy to identify.

If the assignment remains listed but the aircraft ignores it, saving is working. Concentrate instead on device detection, disabled controllers, an incorrect axis, duplicate inputs or separate controller software intercepting the command.

Why do controller settings reset after a USB change?

FSX associates assignments with the device identity supplied by Windows, so another USB port, hub or device reinstallation can make the same physical controller appear to be new hardware.

Connect the joystick, yoke, throttle and pedals before starting FSX, and use the same ports where practical. During diagnosis, connect the affected device directly to the computer because an unstable or underpowered hub can disconnect and rediscover it during a flight.

When Windows supplies a new identity, FSX may create fresh default mappings while retaining assignments associated with the previous identity. Configure the controller entry now shown by FSX and remove unwanted defaults. Manually transplanting device identifiers inside the XML is more error-prone than creating a clean mapping.

Why does a saved POV hat assignment still behave incorrectly?

A POV hat can be saved correctly yet appear broken when it is assigned under the wrong controller, mapped to a conflicting view command or overridden by another view-control system.

Check the device selector and command category before rebuilding Standard.xml. Our hat-switch assignment and conflict checks cover the view-specific setup without repeating the entire controller reset.

Why will FSX still not save after rebuilding Standard.xml?

If a clean file still does not retain changes, identify whether FSX failed to create the file, failed to update it or saved the assignment but cannot use it.

  • No replacement file appears: you are probably inspecting the inactive profile folder, running FSX under another Windows account, or facing a folder-permission or security-software block.
  • The file appears but its timestamp never changes: test whether the folder accepts a temporary file, clear the file's read-only attribute and close FSX normally after making a simple assignment.
  • The timestamp changes but the binding is absent: confirm that you are viewing the same controller entry used during assignment. A USB identity change can create a second, similarly named device.
  • The binding remains but nothing responds: stop treating it as a save failure. Enable controllers, test with joy.cpl, remove duplicates and try a default aircraft.
  • Changes survive a normal exit but not a crash: the simulator is not completing its normal write process. Diagnose the crash separately rather than rebuilding the controls file again.

Running FSX as administrator can be used as a one-off diagnostic. If that alone permits saving, the underlying problem is access to the user-profile folder or interference from security software; permanent elevation conceals rather than fixes it.

What if all FSX settings reset, not only controls?

If graphics options, realism settings or saved flights also fail to persist, the problem affects more than Standard.xml.

That pattern points to a blocked or corrupt FSX profile, another Windows account, redirected folders or wider configuration-file damage. Follow our steps to repair the wider FSX profile and saved-flight problem instead of repeatedly resetting only the controller assignments.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members