Revit 2014 Product GUIDs and GUID Algorithm

Every year anew, people ask for the Revit product GUIDs used to identify the Revit installation and stored in the Windows registry under

• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

I already answered several queries from developers lately wishing to update their installers for the new version.

I discussed this topic on a yearly basis in the past for Revit 2010 and previous versions, Revit 2011, Revit 2012, when the 'perpetual GUID algorithm' was introduced, and Revit 2013.

The install path is less of an issue since the introduction of the add-in manifest to inform Revit how to load your add-in, and the add-in manifest path is well known.

It is actually recommended to install .NET add-ins for both AutoCAD and Revit in or under the same directory as acad.exe and revit.exe, respectively: "It's safest to place assemblies at a location beneath the calling executable."

The best way to determine the Revit install location is to use the RevitAddInUtility, which provides an API for an installer to query that and also to generate an add-in manifest file from the relevant properties you specify. The same RevitAddInUtility assembly DLL works transparently on both 32 and 64 bits.

Revit 2014 and Previous Product GUIDs

In spite of all this, the product GUID is still important, so here is a list of the Revit GUIDs up to and including Revit 2014:

Perpetual Revit Product GUID Algorithm

As you can see above, all the Revit GUIDs from Revit 2012 onwards have a strong similarity.

They are actually generated according to the following pattern:

    {7346B4At-uuvv-wwxy-zzzz-705C0D862004}

The alphabetical characters above stand for:

20. [0/1]: ProductCode/UpgradeCode
21. [12, 13, 14, ...]: Major release version [12, 13, 14]
22. [00, 01, ...]: Release subversion
23. [01/02/03/04/05/06/07]: RAC/RST/RME/LT/One-Box/Server/Vasari
24. [0/1]: Win32/x64
25. [0/1]: Global/Language Pack
26. [0409...]: Language

The 'ww' item corresponds to the ProductType enumeration provided by the Revit API, with the following members:

• Architecture
• Structure
• MEP
• Revit
• LT
• Unknown

The last item, represented by 'z', identifies the language. It uses the hexadecimal LCID or language code identifier. The ones supported by Revit are listed in the following table:

Applying this algorithm to the different flavours of Revit from Revit 2012 onwards produces the values listed in the table above.

Windows Registry Keys

The installer creates the following registry keys:

  HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Revit
  \[RELEASEYEAR]\REVIT-[PRODID]:[LANGID]

  HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Revit
  \Autodesk Revit [RELEASEYEAR]
  \ServicePack[SERVICEPACK#]

RELEASEYEAR is the major version number, i.e. 2013, 2014, etc., PRODID specifies the flavour, listed as 'ww' above, and LANGID the locale, 'zzzz' above, SERVICEPACK# would be 1 for Update Release 1, etc.

For Revit 2014, the Windows registry key is

  HKEY_LOCAL_MACHINE\SOFTWARE
  \Autodesk\Revit\2014\REVIT-05:0409

MUI: Multiple Language Interface Update

Addendum: Revit 2014 is using a new Multiple Language Interface, MUI.

Therefore, you may encounter all-zero language codes besides the ones listed above.

For instance, the following GUID refers to the global MSI which is used for the base product in all locales:

• 7346B4A0-1400-0110-0000-705C0D862004

The corresponding ENU Language Pack MSI would be installed by either an ENU base install or installing the ENU Language Pack on top of a non-ENU base install and create this GUID instead:

• 7346B4A0-1400-0110-0409-705C0D862004

Appropriate keys are added as each additional language pack is installed.