Skip to main content
Melodic_Glimmer869f
Participant
August 21, 2026
Answered

Reader 64-bit shows as "Adobe Acrobat (64-bit)" in Control Panel, breaks patching

  • August 21, 2026
  • 5 replies
  • 107 views

Hi everyone,

 

I’m facing an issue while installing older versions of Adobe Acrobat Reader / Adobe Acrobat Reader DC.

 

Whenever I install an older version of Acrobat Reader, the installed application appears in Control Panel → Programs and Features as: Adobe Acrobat (64-bit)

I was expecting it to be identified as Adobe Acrobat Reader or Adobe Acrobat Reader DC.

This is causing problems with our patching process for Adobe Acrobat Reader, because the installed product is being detected/identified as Adobe Acrobat (64-bit) instead of Reader.

My questions are:

  1. Is it expected behavior for an older version of Adobe Acrobat Reader/Reader DC to appear as Adobe Acrobat (64-bit) in Control Panel?
  2. What determines the product name displayed in Programs and Features—MSI product code, registry entries, or something else?
  3. Does the 64-bit installation use the same product identification as Adobe Acrobat, even when the package is specifically Adobe Acrobat Reader?
  4. Is there a recommended way to install an older Reader version so that it is correctly identified as Adobe Acrobat Reader for patching purposes?
  5. Any explanation regarding how Adobe identifies Acrobat vs. Acrobat Reader, particularly for the 64-bit versions, would be greatly appreciated.
    Correct answer Anand Sri Bhattacharya

    Hello ​@Melodic_Glimmer869f 

     

    Thanks for sharing the details:

    Happy to clear all of this up; it ties directly back to your original "shows as Adobe Acrobat (64-bit)" question.

    There are only two products; the rest are older names for the same things.

    • Free viewer: Adobe Reader = Adobe Reader DC = Adobe Acrobat Reader DC = Adobe Acrobat Reader. All the same free product across naming eras. "DC" (Document Cloud) was added in 2015 and removed from the branding in the October 2022 release, so the current name is just Adobe Acrobat Reader.
    • Paid editor: Adobe Acrobat = Adobe Acrobat Pro / Adobe Acrobat Standard (formerly Acrobat DC / Acrobat Pro DC / Acrobat Standard DC). "Adobe Acrobat" on its own usually means the paid product.

    So of your six names, the current ones are Adobe Acrobat Reader (free) and Adobe Acrobat / Acrobat Pro / Acrobat Standard (paid); the others (Adobe Reader, Adobe Reader DC, Adobe Acrobat Reader DC) are legacy names for the free viewer.

     

    Can Acrobat (paid) and Reader (free) coexist?

    For the current 64-bit Windows Continuous-track application, normally not as two separate installations.

    Adobe’s 64-bit unified application uses:

    Therefore:

    1. If 64-bit Reader is installed and a user acquires an Acrobat subscription, that installation can become the full Acrobat application after sign-in.
    2. Installing the 64-bit unified Acrobat application over 64-bit Reader upgrades/replaces the Reader state rather than creating a second separate application.
    3. Separate 64-bit Acrobat and 64-bit Reader installations on the same machine are not supported by the unified-app model.

     

    Distinguishing products for silent patching (your main goal): 

    Since the unified 64-bit app shows the same "Adobe Acrobat (64-bit)" display name whether it is Reader or Acrobat, do not detect by display name. Detect by these instead:

    • Reader vs Acrobat: read HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Installer\SCAPackageLevel. Value 1 = Reader; greater than 1 = Acrobat.
    • Pro vs Standard (if you need it): HKCU\Software\Adobe\Adobe Acrobat\DC\AVEntitlement\iEntitlementLevel, 300 = Pro, 200 = Standard.
    • Bitness: the string "64-bit" appears in the About box, title bar, and Add/Remove Programs entry.
    • Product code (GUID) to pick the right patch family:
      • Reader 64-bit {ac76ba86-1033-1033-7760-bc15014ea700} → AcroRdrDCx64Upd<version>.msp
      • Acrobat 64-bit {ac76ba86-1033-ffff-7760-bc15014ea700} → AcrobatDCx64Upd<version>.msp
      • Reader 32-bit → AcroRdrDCUpd<version>.msp
      • Acrobat 32-bit → AcrobatDCUpd<version>.msp

    The rule: the MSP must match the installed base product and bitness. Apply an Acrobat MSP to a Reader base (or a 32-bit MSP to a 64-bit base) and it fails with Windows Installer error 1642 ("may update a different version of the program"), which is exactly the class of failure you were hitting.

    1. Silent patching workflow
    2. Detect per machine: bitness, Reader-vs-Acrobat via SCAPackageLevel, and the product code, plus the track (Continuous vs Classic).
    3. Select the matching cumulative MSP for that product/bitness/track from Adobe's enterprise release notes.
    4. Apply silently, for example: msiexec /p AcroRdrDCx64Upd<version>.msp /qn (Reader) or the AcrobatDCx64Upd MSP for an Acrobat base.
    5. MSPs are cumulative within a track, so you can go straight from any prior version to the latest without chaining intermediate patches.
    6. 64-bit is current: Adobe ended 32-bit OS support in January 2023 and 32-bit Continuous Reader migrates to the 64-bit unified app, so most of your patching should target the x64 MSPs.

     

    Deployment guide: https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/sccm.html

     

    I hope this helps.

    Regards,

    Anand Sri.

    5 replies

    Anand Sri Bhattacharya
    Community Manager
    Anand Sri BhattacharyaCommunity Manager
    Community Manager
    August 21, 2026

    Hello @Melodic_Glimmer869f


    I hope you are doing well, and thanks for reaching out. Sorry for the trouble you had.


    This is expected behaviour rather than a broken install, and once the naming is clear the patching side has a clean fix. Taking your questions in order.


    Is it expected that older Reader / Reader DC shows as "Adobe Acrobat (64-bit)"?
    Yes. The 64-bit Acrobat Reader and the 64-bit Acrobat (Pro/Standard) share the same install path and the same Control Panel display name, "Adobe Acrobat (64-bit)." Adobe uses that single alias for both applications in the 64-bit line, so Reader appearing as "Adobe Acrobat (64-bit)" is by design, not a sign the wrong product installed. Adobe's own update-troubleshooting documentation even tells users to look for either "Adobe Acrobat Reader DC" or "Adobe Acrobat (64-bit)" in Programs and Features, which reflects this shared label. Check this article for more details: https://adobe.ly/3UqA05J


    Use Adobe’s documented product-identification value rather than the Control Panel name. Adobe’s official method for distinguishing the installed 64-bit product is:

    HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Installer

    Check the SCAPackageLevel value:

    1 = Acrobat Reader

    Greater than 1 = Acrobat

    Check this article for more details: https://adobe.ly/4hMpfo1


    The unified application does not mean Reader and paid Acrobat have identical product states.
    They share the application framework, but Adobe differentiates the available functionality through licensing/activation and through SCAPackageLevel. A Reader user receives Reader functionality; a user with Acrobat rights receives the licensed Acrobat features after sign-in.


    Select patches by product, architecture, language type, and track—not by the Control Panel label.
    Adobe’s release notes publish separate rows for Acrobat 64-bit, Reader 64-bit, and Reader MUI 64-bit, together with the supported “Install over” base. Use the patch listed for the product identified by SCAPackageLevel and confirm that its architecture, MUI/non-MUI type, track, and base version match the installed package. Check this article for more details: https://adobe.ly/3SNTUHo


    For an older Reader installation, use Adobe’s official older-version download workflow.
    Go to Adobe’s Reader download page, then choose the required operating system, language, and version. Adobe does not document a supported installer switch or customization that forces a particular Programs and Features display name, so changing that label should not be used as the patching solution. Check this article for more details: https://adobe.ly/4wHlhkn


    I hope this helps, and please reach out to us if you need any further assistance.


    Regards,

    Anand Sri.

    Melodic_Glimmer869fAuthor
    Participant
    August 24, 2026

    Thanks a lot for the clarification. I had one more question regarding the different Adobe products, as I’m a little confused about their names and how they relate to one another.

    Could you please clarify the following product names?

    • Adobe Acrobat
    • Adobe Acrobat Pro
    • Adobe Acrobat Reader
    • Adobe Acrobat Reader DC
    • Adobe Reader
    • Adobe Reader DC

    Are these all different applications, or are some of them the same application under different names or versions? In particular, I would like to understand which names are the current product names and which are older/legacy names referring to the same products.

    Also, I would like to understand whether Adobe Acrobat and Adobe Acrobat Reader can coexist on the same system.

    For example:

    1. If Adobe Acrobat (paid) is already installed, can Adobe Acrobat Reader also be installed separately on the same system?
    2. If Adobe Acrobat Reader is installed first, can we subsequently install Adobe Acrobat (paid), or will the Acrobat installation replace/upgrade the existing Reader installation?
    3. In either scenario, would both applications remain installed and independently identifiable, or does Adobe's installation process prevent them from coexisting?

    I would appreciate some clarification on the naming, legacy/current versions, and installation/coexistence behavior of these products.

    Thanks again for your help and clarification.

    jane-e
    Community Expert
    jane-eCommunity Expert
    Community Expert
    August 24, 2026

    ​@Melodic_Glimmer869f 

     

    In addition, Acrobat Reader for Mobile is free with an option for Premium (paid) that does some things Acrobat (for desktop) can do. Premium is included if you have Acrobat Pro.

    There is also Acrobat for Web,

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices