How do I restore FS2004 registry keys for add-ons?

To restore missing FS2004 registry keys, first confirm the folder containing fs9.exe, then use a registry-repair utility or FS2004's installer to recreate the installation-path entry. On 64-bit Windows, FS2004 is a 32-bit application, so add-on installers normally read the redirected Wow6432Node branch. Back up the registry before making manual edits.

Which FS2004 registry key do add-on installers use?

Most legacy FS2004 add-on installers look for the simulator's machine-wide 9.0 key and an EXE Path string containing the folder where fs9.exe is installed. A key holding an old or incorrect path behaves much like a missing key.

The EXE Path value should point to the directory containing fs9.exe, not to the executable itself. Do not assume FS2004 uses its original default directory: many installations have been moved to a custom folder or another drive.

How do I restore the FS2004 registry entry safely?

Automatic repair is safer than creating keys by hand because it reduces the risk of using the wrong Windows registry view.

1. Find the actual FS2004 folder. Locate fs9.exe and launch it to confirm that this is a working installation. Do not select a shortcut, the Aircraft folder or Addon Scenery.
2. Back up the existing registry branch. In Registry Editor, export the relevant Flight Simulator branch before changing it. Close FS2004 and the add-on installer first.
3. Repair the path automatically. Use the TweakFS simulator registry utility to check and restore the FS2004 installation path. Give it the folder containing fs9.exe; if Windows prevents it from saving the entry, run the utility with administrator privileges.
4. Restart the add-on installer. Close it completely and open it again so it reads the repaired path. Use its Browse option if one is provided.
5. Use the original FS2004 setup only if necessary. If the installation is incomplete or the whole registration data is gone, use the original setup's repair option if offered, or reinstall after backing up modified aircraft, scenery and configuration files. Our FS2004 installation guidance for modern Windows explains the protected-folder and moved-installation problems that often cause this fault.

How can I recreate the EXE Path value manually?

Create the standard EXE Path value manually only when the automatic repair cannot write it and you have verified the correct FS2004 directory.

1. Open Registry Editor as an administrator. Search Windows for regedit and approve the elevation prompt.
2. Open the appropriate branch. Use the Wow6432Node location on 64-bit Windows and the non-redirected location on 32-bit Windows.
3. Create the missing 9.0 key if required. If it already exists, edit it rather than creating a duplicate elsewhere.
4. Create or edit EXE Path. Add a String Value of type REG_SZ named EXE Path. Set its data to the full folder containing fs9.exe, such as D:\FS2004. Do not append fs9.exe or surround the path with quotation marks.
5. Close and reopen the installer. A Windows restart is not normally necessary because a newly launched installer reads the updated registry entry.

Do not copy extra registry values from an unrelated computer. Some official updates and specialist add-ons validate more than EXE Path; if one of those still rejects the installation, follow our FS2004 patch and installer-detection checks rather than inventing additional keys.

Why does the add-on installer still say FS2004 is missing?

If detection still fails, either the saved path is wrong or that particular installer is checking something beyond the standard FS2004 entry.

• Wrong registry view: placing the value in the non-redirected branch on 64-bit Windows may leave a 32-bit installer unable to see it.
• Incorrect path data: the value must identify the folder containing the working fs9.exe, without quotation marks or an extra nested folder.
• Insufficient permissions: after checking the path, run the legacy add-on installer as an administrator if it needs to write under HKEY_LOCAL_MACHINE or the FS2004 directory.
• Incomplete moved installation: copying the FS2004 directory from another computer does not restore every installation record or dependency.
• Installer-specific detection: an old installer may expect additional setup information, a particular FS2004 update or its own previous product records.

If the download exposes ordinary Aircraft, Gauges, Effects or scenery files, use our manual FS2004 add-on installation procedure as a fallback. Do not bypass the installer for packages that register modules, licences or other dependencies.

Does restoring the registry key recover installed add-ons?

No. Restoring the FS2004 installation-path key only helps software locate FS9; it does not recover deleted files, Scenery Library entries, gauge dependencies or product activations. Once detection works, verify that the installer targets the existing FS2004 folder and does not create a second nested Flight Simulator 9 directory.