Installing Multiple Versions of FileMaker Pro on Windows

If you work with different FileMaker solutions, testing environments, or customer deployments, there may be situations where you need multiple versions of FileMaker Pro installed on the same Windows machine.

Unfortunately, the FileMaker Pro installer is designed to prevent this. When it detects an existing installation, it typically refuses to install another version alongside it.

Fortunately, there is a workaround.

The Installer Check

Windows Installer stores information about installed applications in the registry. One of the registry entries used by FileMaker Pro can cause the installer to believe that a conflicting version is already present.

The following registry key is involved:

HKEY_CLASSES_ROOT\Installer\Products\5506C20B206A6CB4D9F4FDBDE0CED029

By renaming this registry key before starting the installation, you can bypass the installer check and allow another version of FileMaker Pro to be installed. The installer will then recreate this registry entry.

Important: Always back up your registry before making changes. Editing the Windows registry incorrectly can cause system issues.

Installation Steps

1. Close FileMaker Pro if it is running.

2. Open the Windows Registry Editor (regedit).

3. Navigate to:

HKEY_CLASSES_ROOT\Installer\Products\5506C20B206A6CB4D9F4FDBDE0CED029

1. Rename the registry key. For example, append _backup to the end of the name.

2. Start the FileMaker Pro installer.

3. When prompted for the installation location, choose a different program folder, such as:

C:\Program Files\FileMaker Pro 26

1. Complete the installation.

Why Use a Separate Program Folder?

Installing into a unique folder helps keep the application files for each version separate. This reduces the risk of files being overwritten and makes it easier to identify which version you are launching.

Examples:

• C:\Program Files\FileMaker Pro 21

• C:\Program Files\FileMaker Pro 22

• C:\Program Files\FileMaker Pro 26

When Is This Useful?

Running multiple versions side-by-side can be valuable for:

• Compatibility testing

• Development and QA environments

• Supporting customers on different FileMaker releases

• Verifying behavior before upgrading production systems

Final Notes

This is an unofficial workaround and is not part of the standard FileMaker installation process. Test carefully in non-production environments before relying on this approach, and keep backups of your system and registry settings.

If you frequently work across multiple FileMaker versions, this simple registry tweak can save time and make side-by-side testing much easier.