(There's no need for the WUAgent to cache and evaluate an Acrobat patch if Acrobat v10 is not installed!) I would also suggest adding a test for the presence of Adobe Acrobat v10. I would suggest synchronizing the Adobe Acrobat 10 catalog, and then duplicating the Acrobat 10.1.10 package and adding back this missing pair of Processor Architecture rules. They made the same mistake in the Acrobat 10.1.9 package, but they properly defined the ruleset in the Acrobat 10.1.8 package. (It certainly doesn't work *efficiently*, even if it does work correctly.) it seems that Adobe forgot to define PreRequisite Rules in their package definition for the Acrobat 10.1.10 update. STOP! Why are you *creating* a package? Adobe provides a catalog of Adobe Acrobat update packages ready to use!įurthermore, Patch Manager is fully capable of synchronizing that catalog. Packages and create the Adobe 10.1.10 package Okay, so that's an ADOBE-produced package, and you probably should be having this conversation with Adobe.Īs noted, they have an established history of screwing up their packages. I am using Adobe MSP file with the Adobe Systems, Inc.

Adobe acrobat 10 standard