How do I fix access denied when editing FSX files?

FSX access denied errors usually mean Windows is protecting a file under Program Files, the editor lacks administrator rights, or the file belongs to another account. Close FSX, back up the file, open your editor as administrator, and change only the affected file or FSX folder permissions—not system-wide security.

Why does Windows block edits to FSX files?

Windows normally blocks these edits because Microsoft Flight Simulator X (FSX) and FSX: Steam Edition are often installed inside a protected Program Files folder. Being signed into an administrator account is not enough: User Account Control still starts most applications without elevated permission.

The required fix depends on the file's location:

A boxed installation is commonly under C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X. A default Steam installation is commonly under C:\Program Files (x86)\Steam\steamapps\common\FSX, although another Steam library may place it elsewhere.

How do I edit protected FSX files safely?

The safest fix is to elevate the editor first, rather than weakening security across the computer.

1. Close FSX and related utilities. Also close any add-on manager using the file. If Windows says the file is in use, check Task Manager for an FSX or helper process that did not close properly.
2. Back up the original. Copy it to a writable folder before changing anything. Our guide to backing up active FSX settings and add-on files identifies the configuration locations that are easy to miss.
3. Confirm that it is the active file. Boxed and Steam installations can coexist, and an add-on may point at the wrong FSX directory. For aircraft files, use our boxed and Steam Edition aircraft folder guidance to verify the destination.
4. Run the editor as administrator. Close all existing editor windows, right-click the editor and choose Run as administrator. Open the FSX file from inside that elevated editor. Merely double-clicking the file usually opens a non-elevated process and produces the same access denied message.
5. Use copy, edit and replace if preferred. Copy the file to the Desktop, edit it there, then copy it back. Accept the Windows administrator prompt when replacing the original.
6. Check the individual file. In its properties, clear Read-only if that attribute is genuinely set. A folder's filled or grey Read-only box is not a reliable permissions test and repeatedly clearing it does not repair access-control entries.
7. Grant only the permission required. In the folder's Security properties, give your own account Modify access to the smallest relevant FSX or add-on folder. Do not grant Everyone full control, disable UAC, or change permissions across the whole system drive.
8. Save and verify. Reopen the file and confirm the intended edit remains. Preserve its original extension and encoding; a file accidentally saved as aircraft.cfg.txt will not be read as aircraft.cfg.

Persistent permission failures

An elevated editor that still cannot save usually points to a damaged access-control list, an explicit Deny rule, security software or a file owned by an obsolete Windows account.

• Old or transferred installation: Files copied from another computer or restored from a previous Windows installation may retain an unknown account as owner. Change ownership only on the affected FSX folder, then give your account Modify permission.
• Broken FSX folder permissions: Before changing entries manually, read how FSX's ResetXDirectorySecurity utility repairs installation-folder permissions and when it is appropriate.
• Security software: Check Windows Security or antivirus protection history for a blocked editor or add-on installer. Allow a trusted application specifically instead of disabling protection globally.
• Compressed package: Extract an add-on fully before editing it. A file displayed inside a ZIP archive is not the installed, writable FSX copy.
• Explicit Deny permission: A Deny entry overrides an Allow entry, including administrator access. Remove it only if it applies to the affected FSX folder and you know why it is present.

Why does FSX ignore changes after the file saves?

FSX usually ignores a successful edit because the wrong installation, profile folder or VirtualStore copy was changed.

Steam Edition may use an FSX or FSX-SE profile name depending on the installation history and whether boxed FSX was also present. To identify the active FSX.cfg, change a harmless setting inside FSX, exit normally, then compare the modification times in both folders under %APPDATA%\Microsoft.

Older add-on installers and utilities may also have redirected attempted writes from Program Files into %LOCALAPPDATA%\VirtualStore. Search there for the same relative FSX path if an aircraft or scenery edit appears correct on disk but FSX continues to use an older value. Back up both copies, compare them, and move the stale redirected copy out of VirtualStore rather than deleting it immediately.

Should I take ownership or always run FSX as administrator?

Do not take ownership of broad Windows folders or run FSX elevated permanently just to edit configuration files. Elevate the editor or installer for a specific protected write, and keep applications that communicate with FSX at the same privilege level to avoid permission mismatches.

If you modify add-ons frequently, a separate FSX installation or Steam library outside Program Files is cleaner than repeatedly changing permissions. Reinstall or use Steam's library-management facility; do not drag the installed FSX directory elsewhere in File Explorer, because registered paths and add-on installers may still target the old location. For related account, configuration and protected-folder problems, see our Windows 10 and 11 FSX troubleshooting checks.