How do I fix access denied when editing FSX files?

FSX access denied errors usually occur because Windows protects files under Program Files, the editor is not elevated, the file is read-only, or its permissions are damaged. Close FSX, back up the target, run the editor as administrator, then edit or replace only that file; never disable UAC or weaken system-wide permissions.

This applies to Microsoft Flight Simulator X (FSX) and FSX: Steam Edition on Windows 10 and Windows 11. These instructions cover errors from File Explorer, editors, installers and FSX utilities. If “Access denied — you don’t have permission to access” appears in a web browser, changing Windows folder permissions will not fix that separate server-access problem.

Why does Windows say folder access denied for FSX?

Windows usually denies permission because the FSX installation is under a protected Program Files directory and the application attempting the change is running without elevation.

Being signed in with an administrator account is not enough. User Account Control normally starts editors and add-on tools with standard permissions until Windows explicitly approves an elevated action.

Which FSX file are you actually editing?

The correct fix depends on whether the file belongs to the protected FSX installation, your Windows profile or the shared ProgramData configuration.

A common boxed FSX path is C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X. A default Steam path is C:\Program Files (x86)\Steam\steamapps\common\FSX, although Steam can use another library. Do not grant broad permissions to C:\Program Files (x86)\Steam\steamapps\common\ merely to change one aircraft.

Steam Edition may use an FSX or FSX-SE profile name, depending on installation history and whether boxed FSX has also been installed. Do not assume the folder with “SE” in its name is always active.

How do I edit protected FSX files safely?

The safest method is to elevate the editor for that specific change while leaving Windows security and the parent Program Files folders intact.

1. Close FSX and related utilities. FSX can overwrite configuration changes when it exits. Also close add-on managers or installers that may have the target open.
2. Confirm the active file. Check its full path rather than relying on a shortcut or search result. This matters when boxed FSX and Steam Edition coexist or an aircraft has similarly named variants.
3. Back up the original. Copy the file to a user-owned folder and give the backup a clear name. Do not depend on an editor’s undo history.
4. Open the editor as administrator. Close every existing editor window, then use Run as administrator and open the file from within that elevated editor. Double-clicking the file first usually launches a non-elevated process.
5. Use copy, edit and replace when preferred. Copy the file to a writable folder, edit it there, then copy it back over the original. Approve the Windows administrator prompt for the replacement.
6. Check the individual file’s Read-only attribute. Clear it only if it is set on the file. The filled or grey Read-only box shown for a folder is not a reliable test of write permission.
7. Preserve the name and extension. If file extensions are hidden, an editor may create aircraft.cfg.txt instead of replacing aircraft.cfg. Keep the original text format unless the add-on’s instructions explicitly require another one.
8. Grant only the access actually needed. If repeat editing is necessary, give your account Modify permission on the smallest relevant aircraft or add-on folder. Modify is often required because editors save a temporary file and replace the original; basic Write permission may not allow that replacement.
9. Verify the result. Reopen the file after saving and confirm its modification time and changed value before starting FSX.

How do I fix “save data path is not a writable directory”?

This message means the FSX utility or add-on cannot create a test file in the folder configured as its save, data, cache or output path.

1. Check that the path exists and is a directory. It must not point to a ZIP archive, missing drive, file name or disconnected network location.
2. Choose a user-owned folder for generated data. When the application permits it, create a dedicated local folder such as C:\Users\<account>\FSX Add-on Data. Do not use the FSX installation root merely because the utility is related to FSX.
3. Test the destination. In File Explorer, create and delete a temporary text file there. If that fails, the folder itself is unwritable; if it succeeds, the utility may be blocked or running under another account.
4. Elevate only when the destination must be inside FSX. An installer writing an aircraft into SimObjects\Airplanes may require administrator approval. Run that trusted installer or utility as administrator rather than making all of Steam’s common folder writable.
5. Check Windows security protection. Controlled folder access or antivirus software can block an application even when your account owns the destination. Review protection history and allow only the specific trusted editor or utility instead of disabling protection globally.

Cloud-synchronised folders, removable media and network shares add another permission layer. Make sure the location is available offline and not write-protected. On a network share, both the share permission and the folder’s file-system permission must allow writing.

How do I fix “Access to the compressed folder is denied” in Windows 11?

Windows 11 compressed-folder access is usually denied because the ZIP is blocked or inaccessible, or because the selected extraction destination is protected.

1. Copy the ZIP to a local folder you own. Do not open it directly from a protected FSX directory, temporary browser view, network share or removable device.
2. Inspect the archive’s properties. If Windows displays an Unblock option and you trust the file’s origin, select it and apply the change.
3. Extract the complete archive. Use a new folder under your Windows profile. Do not edit aircraft.cfg or run an installer while it is still displayed inside the compressed folder.
4. Try a short extraction path. Deeply nested add-on folders can exceed what some extraction operations handle cleanly. Extract near the top of a user-owned folder, then move the extracted add-on as required.
5. Separate archive and destination failures. If other ZIP files extract into the same destination, the original archive may be damaged or incomplete. If no ZIP can extract there, repair the destination permission or choose another folder.

If you cannot even copy or open the ZIP, inspect that file’s Security properties. A file encrypted by another Windows account cannot be recovered merely by taking ownership.

What if it still says Access denied?

If the first fixes did not work, identify whether Windows is blocking the whole folder, one file, one application or the replacement operation.

On Spanish-language Windows, Acceso denegado is the same error; if it sigue diciendo “acceso denegado”, use the same checks based on the operation that fails.

• You cannot enter or list the folder: The folder’s access-control list or owner is the likely cause. This is different from an editor being unable to save one file.
• You can enter the folder but cannot create a test file: Your account lacks effective write access, the location is write-protected, or security software is blocking writes.
• You can create a test file but cannot replace one CFG file: Check that file’s Read-only attribute, owner and individual permissions. Also close FSX and any tool holding it open.
• An elevated editor succeeds but an add-on utility fails: Run the trusted utility at the required privilege level or change its data path. Do not run FSX as administrator permanently to compensate.
• Files came from another PC or Windows installation: They may be owned by an obsolete account shown as an unknown security identifier. Change ownership only on the affected FSX or add-on folder.
• There is an explicit Deny entry: Deny overrides Allow, including membership of the Administrators group. Remove it only when you understand why it exists and it applies to the affected FSX folder.
• The Security tab is missing: The location may use a file system without Windows access-control lists. Check removable-media write protection, network-share permissions or the device’s format instead.
• The file is encrypted: Ownership and administrator rights do not decrypt data encrypted by another unavailable account. Restore an unencrypted backup or obtain the original files again.

How should I repair damaged FSX folder permissions?

Repair permissions only on the smallest affected FSX or add-on folder, not on Program Files, the Steam library root or the entire system drive.

1. Open the folder’s advanced Security properties. Review the owner, inherited permissions and any explicit Deny entries before changing anything.
2. Correct an obsolete owner if necessary. Set your account or the local Administrators group as owner of the affected folder only. Apply the change to children only when the whole add-on folder came from the old account.
3. Grant your account Modify permission. Avoid granting Everyone Full control. Do not remove inherited system entries simply because their purpose is unfamiliar.
4. Use the FSX repair tool when appropriate. For a boxed FSX installation with damaged installation-directory permissions, read what ResetXDirectorySecurity.exe changes and when to use it before attempting broad manual edits.

Do not use blanket ownership or permission-reset commands copied for the whole C: drive. They can damage Windows servicing, application security and permissions unrelated to FSX.

Why does FSX ignore changes after the file saves?

FSX usually ignores a successfully saved edit because another installation, profile folder or VirtualStore copy is active.

For FSX.cfg, change a harmless setting inside FSX, exit normally, then compare modification times under %APPDATA%\Microsoft\FSX and %APPDATA%\Microsoft\FSX-SE. The profile updated on exit is normally the active one.

Older, non-elevated installers and utilities may have redirected attempted writes from Program Files into %LOCALAPPDATA%\VirtualStore. Search that location for the same relative FSX path if the visible installation file contains your change but FSX continues using an older value. Back up both copies and compare them before moving a stale redirected copy out of VirtualStore.

Also confirm that FSX was closed during the edit, the file did not gain a hidden .txt extension, and the changed line remains valid for its CFG section. A malformed setting may be ignored even though Windows saved it correctly.

Should I take ownership or always run FSX as administrator?

No; permanent elevation and broad ownership changes are unnecessary for ordinary FSX configuration edits and can create new security or compatibility problems.

Elevate the editor or installer only for a protected write. Applications that interact with FSX should normally run at the same privilege level; permanently elevating FSX can cause mismatches with launchers, add-on tools and drag-and-drop operations.

If you modify installation files frequently, a dedicated FSX installation or Steam library outside Program Files is cleaner than repeatedly changing permissions. Use the installer or Steam’s supported library-management process rather than dragging the installed FSX directory elsewhere in File Explorer, because registered paths and add-on installers may continue targeting the old location.