Product GUIDs for Revit 2012 and Forever More

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

There are different keys for each of the three Revit flavours, and for both 32 and 64 bit operating systems.

The first time around, we discussed the Revit 2010 and previous versions' installation path and product GUIDs, and then updated the list for Revit 2011 last year.

As I mentioned last time, the install path is less of an issue nowadays. There is no longer any need to determine the location of Revit.ini to install an add-in, because you have to use an add-in manifest to inform Revit how to load your add-in instead.

Even though I mostly do not follow this advice myself, 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."

Another way to determine the Revit install location is to use the RevitAddInUtility. It provides an API for an installer to query the Revit installation location, i.e. the path of Revit.exe, and also to generate an add-in manifest file from the relevant properties you specify.

In Revit 2011, there was an issue with using the RevitAddInUtility for 64 bits. That is resolved in Revit 2012, and the same assembly DLL should work transparently on all flavours of Windows now.

Revit Product GUIDs up to Revit 2012

Still, the product GUID may be important for other uses. Here is the updated list including the GUIDs for the initial Revit 2012 versions:

ADN members may also refer to the technical solution TS87598 [How to detect where Revit has been installed?], which has been updated with this new information as well.

Perpetual Revit Product GUIDs

As you may have noted above, the Revit 2012 GUIDs exhibit a strong similarity with each other.

From Revit 2012 onwards, the Revit products codes are generated according to the following pattern:

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

The alphabetical characters above stand for:

20. [0/1]: ProductCode/UpgradeCode
21. [11, 12, ...]: Major release version [11,12]
22. [00, 01, ...]: Release subversion
23. [01/02/03]: RAC/RST/RME
24. [0/1]: Win32/x64
25. [0/1]: Global/Language Pack
26. [0409...]: Language

The last item, represented by 'z', identifies the language. It uses the hexadecimal LCID, which I assume stands for language code identifier or something like that, and is defined in the following table:

Applying this rule to Revit 2012 for the RAC flavour, 64 bit operating system, initial release and US English generates the following value:

    {7346B4A0-1200-0110-0409-705C0D862004}

I checked my 32 bit Windows registry values, and see the following entries beginning with "7346B4A":

{7346B4A0-1200-0100-0409-705C0D862004}

Revit Architecture 2012

{7346B4A0-1200-0101-0409-705C0D862004}

Revit Architecture 2012 Language Pack - English

{7346B4A0-1200-0200-0409-705C0D862004}

Revit Structure 2012

{7346B4A0-1200-0201-0409-705C0D862004}

Revit Structure 2012 Language Pack - English

{7346B4A0-1200-0300-0409-705C0D862004}

Revit MEP 2012

{7346B4A0-1200-0301-0409-705C0D862004}

Revit MEP 2012 Language Pack - English

These Revit product keys and the corresponding 64 bit ones produced the data that I added to the GUID table above.