Member Avatar for HaroldSJS

I am running Acrobat 9 Pro Extended with Windoes 7 Pro, SP 1.

I have been using this program for a long time, and I would like to update it. I downloaded all of the uodates frim Adobe's website along tiem ago. As I understand it, the updates must be installed in sequental increments. From 9.11 to 9.45. Thre is also a 3D update.

I installed the 3D update without a problem. However, when I try to install the first update, from version 9.1 to version 9.11, I get a message which says;

"The upgrade patch cannot be installed by the Windows Intstaller service because the program to be upgraded may be missing or the upograde patch 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 patch."

The Adobe upgrade files are all .msp files. The 3D update is a .msi file.

The Acrobat 9 Pro Extended software worls fine and I use it multiple times each day with an issue.

Why can't I upgrade my Acrobat 9 Pro Extended? Can anyone help me with this issue?

Thanks!

  • 2 Contributors
  • 1 Reply
  • 312 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by cunnijo

Dani AI

Generated

A compact, practical troubleshooting note for the Windows‑Installer/MSP failure reported by (and the good suggestions by ). The error you see is usually not a bad Acrobat binary — it’s the Windows Installer refusing to apply an MSP because the patch’s target (product GUID / SKU / build) or installer cache doesn’t match. Adobe’s Acrobat/Reader patches are MSPs and require the correct patch sequence and target. (adobe.com)

Common causes to check

  • Patch targets a different SKU or build (Standard/Pro/Extended and quarterly vs out‑of‑cycle patches matter). (community.adobe.com)
  • The Installer cached MSI or registry product metadata is missing/corrupt so the patch can’t find its target. (stackoverflow.com)

Diagnosis and first steps

  1. Enable verbose Windows Installer logging and retry the MSP to capture the real reason. Example command (creates a verbose log): 
msiexec /p "C:\path\YourPatch.msp" REINSTALL=ALL REINSTALLMODE=omus /l*v "C:\temp\acro_patch.log"

Inspect the log for "Patch not applicable", "Final Patch Application Order", or missing LocalPackage lines. Microsoft documents PATCH/patch behavior and logging options. (learn.microsoft.com)

If patching an Administrative Install Point (recommended for slipstreaming), apply the MSP to the AIP, then install from that AIP:

msiexec /a "C:\source\AcroPro.msi" TARGETDIR="C:\AIP"
msiexec /a "C:\AIP\AcroPro.msi" /p "C:\patches\AcrobatUpdXXX.msp"
msiexec /i "C:\AIP\AcroPro.msi" REINSTALL=ALL REINSTALLMODE=omus

Adobe’s enterprise guidance shows this flow and why order matters. (community.adobe.com)

If logs show missing cached MSI or a SKU mismatch, repair or reinstall the product to restore the installer cache, then reapply patches in strict order (quarterlies then security/out‑of‑cycle per Adobe guidance). If slipstreaming into an AIP, patch the AIP one MSP at a time in the supported sequence. (learn.microsoft.com)

Notes: verbose logs are the single most useful artifact to decide next steps; collect and read the log before doing full reinstalls.

Member Avatar for cunnijo

It may be an idea to uninstall the 3D update if possible and then try to install the other updates. Another alternative includes trying to install the updates in safe mode.

If all else fails then it may well be a case of uninstalling and reinstalling Acrobat 9 and then running the updates leaving the 3D one to last.

Edited by cunnijo
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.