Skip to main content
S
stephen_4662
Participant
May 23, 2025
Question

Adobe Acrobat Reader 32-Bit (Continuous) - Update Error Code 1642

  • May 23, 2025
  • 2 replies
  • 1261 views

Hi I am trying to deploy Adobe Acrobat Reader via Group Policy and despite it installing, it will not update on any machines, It just produces the error -

 

ERROR 1642

The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing,or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.

I followed the following list - 

 

  1. Downloaded the latest Enterprise version, (AcroRdrDC2500120467_en_US.exe) from here - Adobe - Adobe Acrobat Reader Distribution.
  2. Extracted the msi using the Powewrshell command - .\AcroRdrDC2500120467_en_US.exe -sfx_o"C:\AdobeReaderExtracted" -sfx_ne
  3.  Create Adobe Reader DC Admin installation - msiexec /a c:\AdobeReaderExtracted\AcroRead.msi TARGETDIR="c:\AcrobatReaderDC_AIP"
  4.  Patched the installation msi file with the MSP file that came with the MSI - msiexec /a C:\AcrobatReaderDC_AIP\AcroRead.msi /p C:\AdobeReaderExtracted\AcroRdrDCUpd2500120467.msp
    5. Added a setup.ini file - 

[Startup]
RequireMSI=3.0
CmdLine=/sall /rs

[Product]
msi=AcroRead.msi

6. Created a basic MST file

7. Copied the folder to a network share 

8. Created the Group Policy and linked the test laptop which then installed Adobe Reader

 

Once it is installed, it will not update no matter what I try, I am only streaming the MSP that came with the download, what am I doing wrong please?

 

Best Regards

 

Ste

 

 

 

2 replies

AnandSri
Community Manager
AnandSriCommunity Manager
Community Manager
May 26, 2025

Hello @stephen_4662!

 

I hope you are doing well, and thanks for reaching out.

 

++ adding to what has been shared, Error 1642 means “the upgrade cannot be installed… because the program to be upgraded may be missing, or the upgrade may update a different version of the program. In practice, this usually indicates a track or version mismatch between the installed Reader and the patch (MSP) being applied. For example, applying a Continuous-track MSP to a Classic installation – or vice versa – will trigger 1642, as will using an MSP whose version/build doesn’t match the installed MSI.

 

Before applying updates, validate the installed Reader version and track:

  • Help → About: Open Acrobat Reader on a target machine and click Menu > Help> About Adobe Acrobat Reader. The dialog will indicate “Adobe Acrobat Reader (Continuous)” or “…(Classic)” and show the full version string.

  • Version string: In the About dialog, note the version/build string. The first digit reveals the track: versions starting with “2.” are Continuous, while “3.” indicates Classic.

 

Use the full enterprise installer first: Many admins found it most reliable to run the full Reader DC (32‑bit) installer (the Enterprise .exe or .msi for Continuous track) on target machines instead of just the MSP. This ensures the base version is correct and removes old versions. For example, one engineer noted that running the full Reader DC installer to uninstall old versions before applying the patch allowed the update to proceed normally.

Apply patches to the correct base: If you must use MSP files, be sure you have downloaded the exact matching update for that build and track. Adobe provides Continuous-track MSPs and Classic MSPs separately. If an MSP “does not apply or is not installed,” the workaround is to use the full package installer first.

Validate after install: After running the full installer, re-open Reader and confirm the version (Menu > Help > About). It should now show the updated version (Continuous track). You can then deploy future MSPs successfully.

 

Download the patch/MSI from here: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/index.html

 

Verify track alignment: Confirm whether your GPO-deployed Reader is continuous or classic. Deploy updates that match that track only. (See Adobe’s documentation on DC tracks.)

Use full installer for upgrades: Prefer deploying the full .exe/.msi for new versions via GPO (or use a management tool) rather than only applying MSPs. This avoids the “product missing” issue and automatically installs the correct version.

Fallback to clean install: If you still hit 1642, consider cleaning the old install (using the Acrobat Cleaner tool if necessary) and then doing a fresh install of the latest Reader DC MSI. This resets the product code so patches can apply normally. 

See this article for detailed information on the deployment: https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/index.html

 

I hope this helps.

Thanks,

Anand Sri.

S
stephen_4662Author
Participant
May 27, 2025

Thank you Leo and Anand for your responses, but I am still stuck.

I have already been using AcroRdrDC2500120467_en_US.exe from here Enterprise downloads as suggested, (it is the only option under Windows 11/English UK , I do not get offered 32-bit or 64-bit) and I have only applied the MSP file that came with that download.

I have to extract the MSI and the MSP as I use an MST file. I have tried pushing out the install without the MST file and get the same error so I know it is not the MST causing the problem.

So I still do not know why the 2 files that are downloaded under the same bundle are causing a problem as surely this is the correct MSP file?

 

Best Regards

 

Ste

 

 

AnandSri
Community Manager
AnandSriCommunity Manager
Community Manager
May 27, 2025

Hello Stephen!

 

Thank you for sharing the detailed information. Could you please share the current version of the OS installed on the user machines, if possible, a screen recording depicting the issue, and logs from the affected machine? Download the log collector tool, run it, ensure all the log options are selected, try to reproduce the issue for the error code, save the logs, and share them with us. It may generate a log ID as well. Share the details with us for further investigation.

 

Regards,

Anand Sri.

L
LeoUpdaterX
Participating Frequently
May 23, 2025

When you patch AIP, you are essentially creating new product version instead of base version, which is the target for later patches.

Lets say base version is version A, you patched AIP with version B. Now you deployed it and there is version B on the system.

Adobe released patch version C. This patch is a difference between A and C, and MSI will search the system for version A while applying this patch.

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