Skip to main content
A
AndyUK2010
Participant
May 17, 2012
Question

Problems Updating Adobe Reader AIP 10.1.2 to 10.1.3

  • May 17, 2012
  • 1 reply
  • 6675 views

Hi, I managed to roll out Adober Reader 10.1.2 a month or so ago via Group Policy (Software Deploy). I've now found that quite a few PCs suffer from the known printer issue. So I'd like to update our software to 10.1.3.

I've tried reading through the admin guide but it's slowly melting my brain! And, from what I've read, it doesn't mention much about upgrading a currently installed Adobe Reader.

What I tried to do was take a copy of our 10.1.2 install folder onto my local PC. I tried copying the 10.1.3 MSP file into this folder and running the msiexec patch command. This just threw up an error about the incorrect version to patch (The upgrade patch cannot be installed...because the program to be upgraded may be missing or the upgrade patch may update a different version). But trying to think back I'm certain this is how I'd patched the original 10.1.0 install with 10.1.2 (this MSP file is still in this folder).

I think when I originally patched to 10.1.2 I downloaded a copy of the 10.1.0 EXE and using the sfx commands extracted the files and then patched with the MSP file. I've just tried doing this same procedure but patching with the 10.1.3 MSP and this works. However when I try to run the installation (msiexec /i AcroRead.msi TRANSFORMS=AcroRead.mst) I get an error relating to a different version already being installed (Another version of this product is already installed...etc) which it is, I currently have 10.1.2 installed, I would've assumed the installer would be able to intelligently either auto uninstall the current version and install the new one or upgrade it.

Anyway, after reading a few posts in here I tried adding the new install to our Software Deployment anyway, selecting that it was an upgrade of 10.1.2 and also selecting the option to uninstall 10.1.2. As I'm guessing the option to upgrade it won't work due to the earlier error message. I then tested this new group policy update on a couple of PCs, most had issues trying to apply it (looking in the event log showed a file cannot be found message - all files are present!), eventually after a couple of reboots some do uninstall the old and install the new one. But I'm not convinced, so I've removed it again!

Have I done something wrong here? I was assuming that the new install would be able to patch the current version installed (so long as it's 10.1.2)

If what I've done is correct, then what exactly is the point in patching? What's stopping me from just downloading the 10.1.3 install, extracting the files and just running that? Rather than patching up?

I hope all this makes sense! I appreciate any help.

Andy

This topic has been closed for replies.

1 reply

A
AndyUK2010Author
Participant
May 17, 2012

Just a small update. I've just tried, as a test, to recreate what I did with the 10.1.2 patching.

I extracted the 10.1.0 MSI to a folder, ran the 10.1.2 MSP on this folder (which works), I then try to run the 10.1.3 MSP and get the same error as I mentioned above. Is this not the correct way to do this?

EnterpriseHelp
EnterpriseHelp
Inspiring
May 17, 2012

The admin guide says in multiple places that quarterlies are cumulative to the last MSI. For example, from the AIP Best Practices section:

"For Adobe Reader 10.x, quarterly updates are cumulative to the latest MSI (e.g. 10.1 replaces the base release of 10.0) and security patches are cumulative to the last quarterly. Thus, 10.0 > 10.1 is valid. 10.0 > 10.0.3 > 10.1 isn’t."

This kb says the same thing: http://helpx.adobe.com/acrobat/kb/update-patch-acrobat-reader-10.html

So, the correct order is 10.1 > 10.1.3 with no 10.1.2 in between.

Ben

A
AndyUK2010Author
Participant
May 17, 2012

Thanks for your reply, that's why I assumed it didn't work and why patching from 10.1.0 to 10.1.3 worked. So I believe I have these files ready correctly, it's just how to implement them into Group Policy? As I would've assumed that it would patch the existing installs of 10.1.2, rather than requiring it to be uninstalled.

If this is correct, it doesn't explain why I'm having a handful of PCs experiencing issues uninstalling 10.1.2 and installing 10.1.3 afterwards.

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