© 2015 Adobe Systems, Inc. All rights reserved.

Updated Apr 17, 2015.

Identifying Existing Installs

Licensing identifiers (leid)

Licensing identifiers (LEID) provide a unique way to identify most of Adobe’s licensed products. You will need to know a product’s LEID in the following workflows:

  • Installing a serialized product via a package created with AAMEE (typically CS bundled products).
  • Using the APTEE tool to perform licensing and activation tasks.

Product LEIDs:

  • DC

  • 11

    • V6{}AcrobatStd-AS2-Win-GM
    • V6{}AcrobatPro-AS2-Win-GM
    • V6{}AcrobatPro-AS2-Mac-GM
    • V6{}AcrobatStd-AS2-Mac-GM
  • 10

    • AcrobatPro-AS1-Win-GM
    • AcrobatStd-AS1-Win-GM
    • AcrobatPro-AS1-Mac-GM
    • AcrobatStd-AS1-Mac-GM

Identifying versions by GUID

In enterprise settings, administrators often need to know application what’s already installed prior to deploying or updating new applications. Certainly information such as product version and license type will be part of many update and patch workflows. Adobe provides this data as part of the application’s preferences; for example, in the registry on Windows and in similar locations on other platforms.

This document provides the product identifier information. The methodology for gathering this information via scripted registry queries, server-based client management software, and other 3rd party methods is outside the scope of this document.

The following methodologies are possible:

  • Acrobat 10.0 and later products: Use the GUID or MSI APIs.
  • Acrobat 9.x and earlier: Use both the GUID and VersionMin/VersionMax
  • Adobe Reader 9.x and earlier: Use the GUID.

Decoding product details

Administrators can determine what’s already deployed by using asset management tools or scripts to query for the product’s GUID. The Windows Installer Service initially creates this key automatically when the product is properly installed, but it may also update when the product is patched.

For the Acrobat family of products, the GUID indicates the following:

  • Product family: Acrobat.
  • Version: For example, version 9.
  • Language: For example, English versus English/French/German.
  • Additional languages: Other languages included in the package.
  • Product type: Adobe Reader, Standard, Professional, 3D, etc.
  • License type: Whether the retail or license product is installed.
  • Major version: For example, 8 or 9. For releases every one to two years.
  • Minor version: For example .1 or .2. Typically for quarterly releases.
  • Minor-minor version: For example .1. Typically for patches.

During installation, the product GUID is created as a Value/Data pair in the registry. Each GUID section represents information using a combination of hexadecimal and telephone keypad indicators. Each release and language group receives a unique product code. In the InstallShield project, this code is specified in the Product Configuration panel for the release type. Installers update the GUID though patches do not. Patches (.msp files) target the originating GUID for patch transformation, and thus do not change the GUID.

Note that the value’s actual name is always ENU_GUID even when other languages are also present (for example, FRA, DEU, ESP). As shown in , the GUID for Reader indicates the major, minor, and minor-minor version. However, for 9.x versions of Acrobat and earlier, the GUID does not identify the minor-minor version.


The only time the GUID is updated is when the product is installed with a new MSI installer. The GUID is not updated for patches that don’t use an MSI installer. Thus, VersionMin should also be checked when trying to verify the product version.

GUID construction

The basic formula for constructing and decoding the GUID is as follows:

  • Acrobat: Example: AC76BA86-1033-F400-7760-100000000002
<product family>-<language code>-<additional languages>-<product type>-
<license type><major version><major minor version>
  • Reader: Example: AC76BA86-7AD7-1033-7B44-A70500000002
<product family>-<Reader>-<language code>-<product type>-<license type>
<major version><major minor version><minor minor version>

GUID deconstruction

Using the formula above, the example below translates to: Acrobat 9.0 Professional, English/French/German, volume license.

[HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\<product name>\<version>\Installer]
GUID components
ID Description
product family

The first section of the product code attempts to spell the product family using a combination of hexadecimal and telephone keypad indicators. For example:

  • AC: The first two letters of Acrobat using hexadecimal indicators
  • 76: The letters RO using telephone keypad indicators
  • BA: Two more letters of Acrobat using hexadecimal indicators
  • 8: The letter T using a telephone keypad indicator
  • 6 : The number 6, indicating product version. The last digit is no longer used to determine version. A better indicator of version is noted below.
Reader ID Reader only: 7AD7
language code This second section of the product code contains the four-letter default language code (as defined by Microsoft and used by legacy InstallShield and MSI installers). For Microsoft details, see http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx.
additional languages

A hexadecimal representation of extra languages (ex. “DF60” == DFN == Danish Finnish Norwegian). Use the first letter of the language’s country code if it is between A-F. (D = Danish); Otherwise, use a telephone keypad indicator to represent the language. (ex. 6 = Norwegian). For example:

  • F: French, using a hexadecimal indicator
  • 4: German, using a telephone keypad indicator
  • 00: No other languages
product type

The product using hexadecimal and telephone keypad indicators as follows:

  • 7760: Acrobat Pro (PRO using telephone Keypad indicators, followed by a zero)
  • BA7E: Acrobat Standard
  • 7B44: ReaderBig
  • 7761: 3D
license type Acrobat only: The first digit in the last number series indicates volume or retail use. For example, in 100000000002, the leading1 indicates volume licensing. 0 indicates retail licensing. This series is always preceded by an “A” for Reader.
Acrobat major version

In the last number series, the last digit indicates the major version as follows:

  • 1: version 6
  • 2: version 7
  • 3: version 8
  • 4: version 9
  • 5: version 10
Reader major version

The last number series is always preceded by an A and the actual Major.MajorMinor version number. The last digit indicates the minor version. Thus, the formula is: {A}+{Major #}+{MajorMinor # if any}+{zeros}+{MinorMinor version if any}. For example:

  • Reader 9.2 = A920000000001 (1 = 0)
  • Acrobat 10.1 = {AC76BA86-1033-F400-7760-000000000005}

GUID registry location

The GUID is written to a variety of locations. However, Adobe recommends you use the following:

  • 32 bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\{application}\{version}\Installer\
  • 64 bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\{application}\{version}\Installer\

GUID installer package location

Administrators interested in dissecting installer packages prior to deployment can find the GUID in the installer msi package. To find the GUID in an installer, go to Property > ProductCode, and look in the Value column.


The only time the GUID is updated is when the product is installed with a new MSI installer. The GUID is not updated for patches that don’t use an MSI installer. Thus, VersionMin should also be checked when trying to verify the product version.

Installer MSI: GUID

Example GUIDs
Product GUID
Acrobat 11.0 (each installer supports all languages) {AC76BA86-1033-FFFF-7760-000000000006}
Reader 10.0.0 en_US {AC76BA86-7AD7-1033-7B44-AA0000000001}
Reader 10.0.0 MUI {AC76BA86-7AD7-FFFF-7B44-AA0000000001}
Reader 10.1.0 en_US {AC76BA86-7AD7-1033-7B44-AA1000000001}
Acrobat 10.1 {AC76BA86-1033-F400-7760-000000000005}
Acrobat Std 10.0.0 en_US {AC76BA86-1033-0000-BA7E-000000000005}
Acrobat Pro 10.0.0 en_US {AC76BA86-1033-0000-7760-000000000005}
Adobe Reader 9.2 AC76BA86-7AD7-1033-7B44-A70500000002
Acrobat Professional 8.0 {AC76BA86-1033-0000-7760-000000000003}
Acrobat Standard 8.0 {AC76BA86-1033-0000-BA7E-000000000003}
Reader 8.0 {AC76BA86-7AD7-1033-7B44-A80000000002}
Acrobat Professional 7.0 retail edition {AC76BA86-1033-0000-7760-000000000002}
Acrobat Professional 7.0 volume license edition {AC76BA86-1033-0000-7760-100000000002}
Acrobat Standard 7.0 retail {AC76BA86-1033-0000-BA7E-000000000002}
Acrobat Standard 7.0 volume license edition {AC76BA86-1033-0000-BA7E-100000000002}
Acrobat 3D retail {AC76BA86-1033-F400-7760–000003D0002}
Acrobat 3D volume license edition {AC76BA86-1033-F400-7760-1000003D0002}
Reader 7.0 {AC76BA86-7AD7-1033-7B44-A70000000000}
Reader 7.0.5 {AC76BA86-7AD7-1033-7B44-A70500000002}
Acrobat 7.0.1 and Reader 7.0.1 Update {AC76BA86-0000-7EC8-7489-000000000702}
Acrobat 7.0.2 and Reader 7.0.2 Update {AC76BA86-0000-7EC8-7489-000000000703}
Acrobat 7.0.3 and Reader 7.0.3 Update {AC76BA86-0000-7EC8-7489-000000000704}
Acrobat 7.0.5 and Reader 7.0.5 Update Use the product ID 7.0 listed above
Adobe Acrobat 7.0.7 and Reader 7.0.7 update {AC76BA86-1033-F400-7760-100000000002}
Adobe Acrobat 7.0.8 and Reader 7.0.8 update {AC76BA86-1033-0000-7760-100000000002}

VersionMax-VersionMin (9.x and earlier)

This method is deprecated and is not used for X products.

The installer creates keys during installation which identifies the product version. Administrators can use those keys to automatically query which version of the application is installed and therefore ensure patch status.

  • VersionMax: Identifies the major version and any major dot release. For example, 9.3 would be 90003. Thus, VersionMax is a 4 digit representation of major version (first number before the dot) with an appended integer value indicating the major dot release, if any.
  • VersionMin: Identifies the minor dot release which is appended to VersionMax, if any. For example, 9.3.0 would be 0 and 9.3.1 would be 1). Thus, VersionMin is the integer value of the number after the second dot.


VersionMin must be used in conjunction with the GUID to identify the minor-minor version of Acrobat.

VersionMax-Min location

These preferences reside in the following locations:

  • 32 bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\{application}\{version}\Installer\
  • 64 bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\{application}\{version}\Installer\


For 10.0 and later product versions, you can use the MSI API to determine the product version. To use the MSI API, use the MsiEnumRelatedProducts() and MsiGetProductInfo(). For more information about these APIs, see http://msdn.microsoft.com/en-us/library/aa370130(VS.85).aspx.

Product version via MSI API

//UpgradeCode is a family of ProductCodes
//ProductCode property is what you need to get installed Product Info
void GetProductInfo()
    CString    sUpgrdCode = _T("{A6EADE66-0000-0000-484E-7E8A45000000}");//All Reader installers (any version) have the same UpgradeCode

    //UpgradeCodes for Acrobat - these values do not change
    //APEX {AC76BA86-0000-0000-7761-7E8A45000000};
    //Pro  {AC76BA86-0000-0000-7760-7E8A45000000};
    //Std  {AC76BA86-0000-0000-BA7E-7E8A45000000};

    CString sProdCode;
    for(int index = 0; dw == ERROR_SUCCESS; index++)
        dw = MsiEnumRelatedProducts(sUpgrdCode, 0, index, sProdCode.GetBuffer(MAX_PATH));

        if(dw == ERROR_SUCCESS)
            UINT ret;
            TCHAR sVersionString[MAX_PATH] = {0}, sVerMajor[MAX_PATH] = {0};
            DWORD dwSize = 10;

            ret = MsiGetProductInfo(sProdCode, INSTALLPROPERTY_VERSIONMAJOR, sVerMajor, &amp;dwSize);
            //ret = MsiGetProductInfo(sProdCode, INSTALLPROPERTY_VERSIONSTRING, sVersionString, &amp;dwSize);

Identifying the license

Software identification tags (SWIDs) help IT organizations manage software assets by providing the ability to identify the license state of installed software. SWIDs also provide a method for distinguishing between subscription (cloud) and boxed installs. For an overview of Adobe’s usage of ISO/IEC 19770-2:2009 software identification tags in Acrobat and CS products, see the Software Tag document.

SWID files are located under ProgramData. For example:


Identifying your install

The following examples show you how to identify your current install type.





Volume (Activated)


Volume (Unactivated)

In this example, the product is serialized, an offline exception has been used, and the product is still not activated.

In Enterprise volume scenarios, admins often use the Type 2 exception to license the software. This involves the generation of the exception file (prov.xml either via AAMEE/CCP/APTEE) and processing it on the target machines. At the point when the exception has just been applied, the product is in “serialized” state. If the machine is online and the product is launched, the licensing component attempts an activation. If it goes through successfully the product moves to an “activated” state. These are not subscription licenses.


Example SWID file

<?xml version="1.0" encoding="utf-8"?>
<swid:software_identification_tag xsi:schemaLocation="http://standards.iso.org/iso/19770/-2/2008/schema.xsd software_identification_tag.xsd"
  xmlns:swid="http://standards.iso.org/iso/19770/-2/2008/schema.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<!--Mandatory Identity elements -->
<swid:product_title>Acrobat X Pro</swid:product_title>
 <swid:name>Adobe Systems Incorporated</swid:name>
 <swid:name>Adobe Systems Incorporated</swid:name>

 <swid:name>Adobe Systems Incorporated</swid:name>
<!--Optional Identity elements -->