How do I repair or rebuild the FSX registry on Windows?

To repair or rebuild the FSX registry on Windows, find the folder containing fsx.exe, back up the relevant registry key, then correct only the edition-specific path value: SetupPath for boxed Microsoft Flight Simulator X or AppPath for FSX: Steam Edition. The value must name the FSX folder, not fsx.exe itself.

Which FSX registry key and path value should I use?

Use the key for your FSX edition and Windows architecture; boxed FSX and FSX: Steam Edition do not share the same primary path entry.

On 64-bit Windows, boxed FSX is a 32-bit application, so its entry belongs under Wow6432Node. Do not duplicate the key in both registry views in the hope that one will work.

The string data must be the complete folder containing fsx.exe. Examples include C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ or a custom Steam library such as D:\SteamLibrary\steamapps\common\FSX\. These are examples only; use the folder on your computer. Our guide to locating the real FSX installation folder explains how to identify it when a shortcut or old drive letter is misleading.

Do not include quotation marks and do not enter the full path to fsx.exe. Retaining a final backslash is safest because some older add-on installers append their own folder names directly to the stored path.

¿Cómo solucionar este problema?

Para solucionar este problema en FSX o FSX: Steam Edition, localice la carpeta que contiene fsx.exe, exporte una copia de seguridad de la clave correcta y corrija únicamente SetupPath para la edición en DVD o AppPath para FSX:SE. El valor debe ser la ruta de la carpeta, sin comillas, y no debe terminar en fsx.exe.

Should I repair the path or rebuild the key?

Edit an existing value when it points to the wrong folder; rebuild the minimal key only when FSX is installed and working but the edition-specific key or value is genuinely absent.

A minimal rebuild can restore detection for an add-on that checks only the installation folder. It does not recreate installation-state, version, Acceleration or licensing data written by the original FSX installer.

How do I safely repair or rebuild the FSX registry?

The safest procedure changes one path string, preserves a backup and tests the result before an add-on copies any files.

1. Close FSX and every related installer. Add-on installers often read the registry only when they start, so leaving one open can make a successful repair appear to have failed.
2. Confirm the actual FSX root folder. Open it in File Explorer and verify that fsx.exe is physically present. Do not use the parent Microsoft Games, steamapps\common or Steam library folder.
3. Back up the registry entry. Open Registry Editor, select the relevant 10.0 key and use Export. If that key is absent, export its immediate parent before creating anything. Keep boxed and Steam Edition backups separate.
4. Open the correct registry location. Boxed FSX writes beneath HKEY_LOCAL_MACHINE, which normally requires administrator permission to edit. FSX: Steam Edition uses HKEY_CURRENT_USER, so edit it while signed in to the Windows account that runs FSX:SE.
5. Edit or create the path value. Use a String Value of type REG_SZ named exactly SetupPath or AppPath. Enter the folder containing fsx.exe, preferably with a final backslash.
6. Close Registry Editor and restart the installer. Check that its proposed destination is the real FSX folder before allowing it to install anything. A Windows restart is not normally required.

Do not delete the whole Microsoft Games branch, import registry files from another computer or copy product and activation entries. A sweeping registry cleaner is also the wrong tool: the goal is to correct one known path, not remove entries it considers obsolete.

Steam install path value not found in the registry: how do I fix FSX:SE?

For FSX: Steam Edition, verify its installed files, launch it once from the same Windows account, close it, then restore AppPath manually only if the Steam-specific value remains absent.

1. Use Steam's installed-files verification command. This confirms that fsx.exe exists and avoids registering a damaged or incomplete installation.
2. Launch FSX:SE once and close it normally. First launch can establish per-user data that is not present immediately after files are installed or moved.
3. Inspect the per-user key. Open HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 while signed in to the account that uses the simulator.
4. Create AppPath only if it is missing. Make it a REG_SZ String Value and enter the exact folder containing the Steam copy of fsx.exe.
5. Run the add-on installer under the same account. Normal administrator elevation is acceptable, but supplying another user's administrator credentials can make the installer read that user's HKEY_CURRENT_USER instead.

The Steam client and its FSX library may be on different drives, so do not derive AppPath from the Steam programme's own location. Follow the library folder that actually contains fsx.exe.

An older installer may still report that the Steam install path value was not found because it checks only the boxed-FSX SetupPath. Correcting AppPath cannot change that installer logic. Use its custom destination option or a supported manual installation method; our add-on installer path troubleshooting covers those choices without overwriting a real boxed installation.

Will it work for FSX SE and boxed FSX?

Yes, registry repair works for both editions when the problem is limited to a missing or incorrect installation path, but each edition must retain its own key and folder.

On a side-by-side installation, boxed FSX's SetupPath must point to boxed FSX, while the Steam Edition AppPath must point to FSX:SE. Never repoint one edition's genuine entry at the other merely to satisfy an old add-on installer.

This repair does not fix activation or licence messages, damaged simulator files, fsx.cfg settings, scenery configuration, crashes, missing runtime components or a broken Windows installer. It answers one question: where is the installed copy of FSX?

Why does it still not work after the registry repair?

If it still does not work, either the stored path is not exactly correct or the programme is checking something beyond the FSX installation-path value.

• The value points to the folder above FSX, includes fsx.exe, contains quotation marks or uses an old drive letter.
• SetupPath was created outside Wow6432Node on 64-bit Windows.
• AppPath was edited for a different Windows user from the one running FSX:SE or the installer.
• The value was created with the wrong name or data type instead of an exact REG_SZ string.
• The installer remained open and cached the earlier result.
• The installer recognises boxed FSX only, even though its add-on files may otherwise be compatible with FSX:SE.
• The add-on also checks installation-state, service-pack, Acceleration or other version information that a minimal path rebuild does not restore.
• FSX was manually copied rather than installed, leaving files, permissions or other setup records incomplete.

If FSX itself fails to launch or files are absent, stop rewriting the path and follow the checks for repairing missing or corrupted FSX files. Steam can verify its installation; boxed FSX may require repair from its original installation media.

If FSX runs but an add-on still cannot detect it, the remaining fault is usually the add-on installer's edition check or destination logic. If the boxed installer instead refuses to reinstall because it believes FSX is already present, use the procedure for removing stale FSX installation records before reinstalling; recreating SetupPath will not repair Windows Installer records.