Can't Slipstream Arobat 8.1.6 Update because 8.1.3 Update failed.

hi guys,

i'm curious: How did you able to slipstream (AIP) Acrobat 8 Pro to 8.1.3?

I'm getting a weird error when slipstreaming 8.1.3 Update.

Here's what I got:

0) Setup on XP Pro SP3/Vista/Win7. AIP is in C:\ local drive.
1) Create AIP for Acrobat 8.0.0 Pro.
2) Slipstream 8.1.0 Update (MD5: 37baea6694b15c354b0769b80c500711)
3) Slipstream 8.1.1 Update (MD5: e6faf402bd7a7e864dbe0870a80d04c5)
4) Slipstream 8.1.2 Update (MD5: 69f725c77a879f542af89c6a5bdab839)
5) Ignored 8.1.2 SU1 Update (negligible; and it's in MSI anyway so no point slipstreaming to AIP)
6) When I tried to slipstream 8.1.3 Update (MD5: c3e0ea9741f84246cf281acb33e22c86), i get an error msg:


Error 1335. The cabinet file 'PCW_CAB_ACRO' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

7) There's no way to continue. Pressing Ignore button generate a simple error dialog:


Internal Error 2350.

8) Now, i can't slipstream 8.1.4 or 8.1.5 or 8.1.6 because 8.1.3 won't install at all.

Any ideas?


0 Comments   [ + ] Show comments

Answers (4)

Posted by: davidlimcg23 13 years ago
Senior Yellow Belt
ok plz ignore my post above.

i redownload the update again and it gave me a different MD5 (059eb0386e28495ec6e4194facece48d).

slipstreaming works now.


p/s: don't know why but when i downloaded it last month, it gave a different MD5 hash. Filesize is the identical with the previous download.
Posted by: anonymous_9363 13 years ago
Red Belt
The hash could use anything as its key, not just the filesize. It may use the date/time, version number, whatever.
Posted by: joedown 13 years ago
Third Degree Brown Belt
In case anyone else has a similar issue with patching an Admin Install point here is some important info from Adobe. http://kb2.adobe.com/cps/498/cpsid_49880.html Unlike most patches apparently Adobe only allows you to apply specific patches to your admin install point but they do not point that out in the patches when you download them. But should we really expect anything different considering their track record?
Posted by: PackageExpert 13 years ago
Blue Belt
ORIGINAL: joedown

But should we really expect anything different considering their track record?

Its a known 'issue' -> or maybe by design? Now im being an ass...lol
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ