How does the MEPlinx installer (previously Cylink) detect the Revit installation?

By Simon Brown

There have been a few recent enquiries to our support service regarding the installation of the MEPlinx software, where the installation insists the correct version of Revit is not present. An example message is:

“This version of MEPlinx requires Revit 2024.  Installation cannot proceed”

This message means that the installer cannot detect the required version of Revit, even though it may be installed.  The installer needs Revit to have been run at least once, to have written the registry setting that the MEPlinx installer looks for.

Revit uses the HKEY_CURRENT_USER part of the registry, which is only visible to the currently logged in user.  Some organisations use a different account to install software, and the Revit registry key would not be visible to this account. 

To get around this, either:

1. Run Revit using the same account you will use to install MEPlinx, so the registry settings are written.  or
2. Manually create the keys and values shown above for the required version of Revit, whilst logged into the account to be used for the install.

MEPlinx/Cylink for Revit 2019 and later

Autodesk moved the registry setting to a different location, so we now check for the setting here.

HKEY_CURRENT_USER\SOFTWARE\Autodesk\Revit\Autodesk Revit 2024\App (See screenshot above)

Adjusted for the version obviously e.g. Autodesk Revit 2024:

Cylink 2019 for Revit 2019 Specifically

HKEY_CURRENT_USER\SOFTWARE\Autodesk\Revit\Autodesk Revit 2019\App

It is found if there is a REG_SZ value called windowPlacement.

Cylink for Revit 2018 and earlier

HKEY_CURRENT_USER\Software\Autodesk\Revit\Autodesk Revit 2018\Workspace

It is found if there is a DWORD value called Version.

• 11150634892061200 KB