Adobe Readrer IDAC76BA86-7AD7-0000-2550-7A8C40000000

ENABLE TO PRINT uNABLE TO DELETE ADOBE READER RECEIVE ABOVE SUPPORT CODE ERROR. HOW CAN WE REMOVE AND REINSTALL?

Mike, Apologies for caps, did not change caps key from entering error code.
Our operating system is Windows XP, the Adobe Reader states 8.1.1.
We are unable to print. We have attempted to delete programme from add and remove programs however we received the following message, unable to remove, patch fix not installed. I tried the Tech Support link and received the Update ID to quote AC7BBA86-7AD7-0000-2550-7A8C40000000. I hope this assists, we are not very computer literate and find it hard to understand some of the terminology, however learning all the time. Regards Carole

Similar Messages

Adobe Reader XI - Deutsch - Update {AC76BA86-7AD7-0000-2550-7A8C40011004} could not be installed....

Hi, I want to install BlueStacks on my comuter. At the end of the installing process I get this message:
which means:
Adobe Reader XI - Deutsch - Update {AC76BA86-7AD7-0000-2550-7A8C40011004} could not be installed.... Errorcode 1625.
What to do now?

Hi, Pat, thanks for your reply. Actually I want to install BlueStacks, 'cause it enables me to use "What'sApp" on my PC.
Anyways, my current Reader version of Adobe Reader is 11.0.4, and I've tried several times to install BlueStacks.... no success!

I HAD ADOBE READR 10 AND IT WAS WORKING FINE. I TRIED TO INSTALL 11 AND MY COMPUTER GOT JAMMED. I DI

I HAD ADOBE READR 10 AND IT WAS WORKING FINE. I TRIED TO INSTALL 11 AND MY COMPUTER GOT JAMMED. I DID A SYSTEM RETORE AND GOT BACK TO 10, BUT WHEN I TRY TO USE IT NOW I GET 2 MESSAGES. " THIS APPLICATION HAS REQUESTED THE RUNTIME TO TERMINATE IN AN UNUSUAL WAY" AND ADOBE READER STOPPED WORKING.

What is your operating system? What means "JAMMED"?
P.S. please do not post in all-caps; it is very difficult to read!

Problems with Adobe Readrer v9.2

I have Adobe Reader 9.2 installed on my Dell Inspiron 9300 and Adobe Reader comes up with an error "Adobe Reader has encountered a problem and needs to close".
Why is this? Should I try to reinstal the original version coming with the Dell?
Can you help please. Thanks,
Alan

At least it worked for me. I found the solution at c/net from a guy who had a similar problem with Adobe
Reader 9.1. Here is what he suggested (by the way, he places the blame on
Adobe for the problem). Here is what he wrote onc/net:
It seems the only way to fix this problem is to disable the Adobe PDF Link Helper Browser Helper Object in Internet Explorer. This can be done by choosing Tools -->Internet Options-->Programs tab-->Manage add-ons button-->Click on Adobe PDF Link Helper-->Disable--> Close
I did this and I was able to open a PDF document without a problem. As I wrote earlier, I use a Sony desktop running Windows XP
I just found where this guy frustratedtechdude posted the fix to his propblem with 9.1: http://download.cnet.com/Adobe-Reader/9241-10743_4-11011850.html?messageID=10423052
My hearty thanks to frustratedtechdude for his wonderful solution!

Adobe Readre x can't open web pdf

Hello
We are ruuning Windows Server 2008 Terminal serves. We have have 3 clients running HP Thin Clinets. I have download adobe rteader x taken all the updates for the terminal servers. When a user from a website trying to open a PDF it download the pdf but does not display the page? I need to manully hit the refrash button to open up the document? is that correct?
Cheers

Hello
Have you try this
Edit->Preferences->General->uncheck "Enable Protected Mode At Startup"
I try this with no luck
Cheers

Adobe readr x toolbar will not saveing settings

Every time I customize my toolbar it does not appear the next time I open adobe reader. Any way to fix ?
Thank you.

Hi Adam Baranek,
I am looking into this issue and will get back to you soon.
Regards,
Rahul Tyagi

I can not get adobe readre to work. I though when adobe was installed and I receaved an e-mail with

I can not get adobe to work

You might try the Reader forum http://forums.adobe.com/community/adobe_reader_forums since I don't think Reader is really a "Cloud" product

Adobe Reader will not update from 11.0.0.6 to 11.0.0.7

I have tried installing the update to my Windows 8.1 machine, but it fails every time. When I right click and run as administrator from the download, it extracts, then pops up with:
"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade 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."
From the Adobe ARM.log, there is an ERROR_SUCCESS that tells me it stayed at version 11.0.0.6.
From the AdobeSFX.log, there is a "Program finished with exit code:1642". (Which just tells me the same thing as the error pop up box.)
From the MSI Installation log there is this:
: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40011007} - C:\ProgramData\Adobe\Setup\{AC76BA86-7AD7-1033-7B44-AB0000000001}\RDC\AdbeRdrUpd11007.msp
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.
C:\Windows\Installer\2f8d0.msi
: Product: Adobe Reader XI (11.0.06) - Update '{AC76BA86-7AD7-0000-2550-7A8C40011007}' could not be installed. Error code 1642. Additional information is available in the log file C:\Users\ADMINK~1\AppData\Local\Temp\MSIcd3b7.LOG.
: Windows Installer installed an update. Product Name: Adobe Reader XI (11.0.06). Product Version: 11.0.06. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Update Name: {AC76BA86-7AD7-0000-2550-7A8C40011007}. Installation success or error status: 1642.
: Note: 1: 1708
: Product: Adobe Reader XI (11.0.06) -- Installation failed.
: Windows Installer installed the product. Product Name: Adobe Reader XI (11.0.06). Product Version: 11.0.06. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1642.
: MainEngineThread is returning 1642
I am testing the update before doing an enterprise rollout to Win8 and Win7 machines. I have tried the standalone update on other computers (Win7 and Win8) and I cannot get it to update.
I downloaded from here: Adobe - Adobe Reader Distribution Selecting Windows 8, English, and 11.0.0.7
From Administrative Command Line:
AdbeRdr11007_en_US.exe -nos_oC:\Users\$$$$$$$\Desktop\Reader -nos_ne
msiexec /a C:\Users\$$$$$$$\Desktop\Reader\Acroread.msi network location: \\$$$$$$$\apps\adobe\reader11_0_0_7\
msiexec /a \\$$$$$$$\apps\adobe\reader11_0_0_7\AcroRead.msi /p C:\Users\$$$$$$$\Desktop\Reader\AdbeRdrUpd11007.msp
This is not working either - which is not surprising considering that the update itself will not run. I can only guess that somehow the 11.0.0.6 update was incorrect somehow, but I have been using the same process to update the machines for more than 5 update cycles, so I am not sure what might have changed.
The point is, I do not want to do a complete uninstall and clean install on all of the machines in the company. Can anyone give direction with this?

I disagree about corrupted install. Every 11.0.6 pc in my enterprise also cannot upgrade to 11.0.7. We make AIPs following the same process for each patch. Something is not right with 11.0.7 MUI. I can create the AIP for 11.0.7 but cannot get the GPO to upgrade previous installations. I think something is seriously wrong with the 11.0.7 MUI msp
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 am using the 11.0 MUI installer to create the AIP and then I patch the AIP with 11.0.7 MUI .msp file per normal practice like I always do. I am able to sucessfully create the 11.0.7 AIP without errors but none of my 11.0.6 MUI clients will upgrade successfully and are left at 11.0.6.
Something is broken with the 11.0.7 MUI .msp file.
Like I said, we do this the same way each time depending on quarterly update or security update and it ALWAYS works fine. This is well documented. We are following the exact same steps and something is seriously wrong with the new 11.0.7 MUI .msp file. It will not properly upgrade 11.0.6 MUI installations.
We are using the 11.0 MUI as the base for slipstreaming the new 11.0.7 MUI patch.
STEPS:
1. Download AdbeRdr11000_mui_std.zip and extract to temp directory.
2. Run: msiexec /a c:\aip\temp\acroread.msi TARGETDIR="c:\aip\11.0.7"
3. Copy the AdbeRdrUpd11007_MUI.msp patch to c:\aip\11.0.7\
4. Run: msiexec /a c:\aip\11.0.7\acroread.msi /p c:\aip\11.0.7\AdbeRdrUpd11007_MUI.msp
5. Choose c:\aip\11.0.7 as the installation folder
6. When completed Copy c:\aip\11.0.7 to \\servername\AIP\
7. Configure GPO to upgrade over the top of existing installation of previous GPO 11.0.6 MUI using the correct UNC folder
This has worked every time other than this 11.0.7 MUI msp file. It will not upgrade 11.0.6 installations.

Adobe Reader 11 Update via SCUP

Hi all,
i'm updating Adobe Reaer via SCCM and SCUP and the published catalogs from Adobe.
When importing the updates i do not see the MUI Update for Version 11.0.5, but the not MUI Version is available.
is this update published later what do i wrong?
Thanks a lot

I'm a bit sorry, I've used the non MUI version for deployment, it was the German 11.0.04 Package.
11.0.05 Deployment via SCUP was done without any problems.
I tried "msiexec /update AdbeRdrUpd11006.msp" with Logging Option and this is the output (It's a bit in german I hope its not a problem):
=== Verbose logging started: 24.01.2014 09:53:11 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (CC:14) [09:53:11:008]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (CC:14) [09:53:11:008]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (CC:5C) [09:53:11:018]: Resetting cached policy values
MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'Debug' is 0
MSI (c) (CC:5C) [09:53:11:018]: ******* RunEngine:
           ******* Product: {AC76BA86-7AD7-1031-7B44-AB0000000001}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (CC:5C) [09:53:11:047]: Cloaking enabled.
MSI (c) (CC:5C) [09:53:11:047]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (CC:5C) [09:53:11:050]: End dialog not enabled
MSI (c) (CC:5C) [09:53:11:051]: Original package ==> C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:11:051]: Package we're running from ==> C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall Flags override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall VersionNT override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1031-7B44-AB0000000001}'.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (CC:5C) [09:53:11:060]: MSCOREE not loaded loading copy from system32
MSI (c) (CC:5C) [09:53:11:062]: Opening existing patch 'C:\WINDOWS\Installer\1e65cb.msp'.
MSI (c) (CC:5C) [09:53:11:063]: Original patch ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
MSI (c) (CC:5C) [09:53:11:063]: Patch we're running from ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp' against software restriction policy
MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp has a digital signature
MSI (c) (CC:5C) [09:53:15:798]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (CC:5C) [09:53:15:798]: SequencePatches starts. Product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, Product version: 11.0.04, Upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}, Product language 1031
MSI (c) (CC:5C) [09:53:15:798]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} is applicable.
MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
MSI (c) (CC:5C) [09:53:15:800]: PATCH SEQUENCER: minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is not applicable.
MSI (c) (CC:5C) [09:53:15:801]: SequencePatches returns success.
MSI (c) (CC:5C) [09:53:15:801]: Final Patch Application Order:
MSI (c) (CC:5C) [09:53:15:801]: {AC76BA86-7AD7-0000-2550-7A8C40011005} -
MSI (c) (CC:5C) [09:53:15:801]: Other Patches:
MSI (c) (CC:5C) [09:53:15:801]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40011006} - C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
Das Upgrade kann nicht vom Windows-Installationsdienst installiert werden, da das zu aktualisierende Programm nicht vorhanden ist oder eine andere Version des Programms mit dem Upgrade aktualisiert wird. Überprüfen Sie, ob das zu aktualisierende Programm vorhanden ist und das richtige Upgrade verwendet wird.
C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:15:802]: Produkt: Adobe Reader XI (11.0.04) - Deutsch - Update "{AC76BA86-7AD7-0000-2550-7A8C40011006}" konnte nicht installiert werden. Fehlercode 1642. Weitere Informationen sind in der Protokolldatei C:\temp\msi2.log enthalten.
MSI (c) (CC:5C) [09:53:15:803]: Ein Update wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Updatename: {AC76BA86-7AD7-0000-2550-7A8C40011006}. Erfolg- bzw. Fehlerstatus der Installation: 1642.
MSI (c) (CC:5C) [09:53:15:803]: Note: 1: 1708
MSI (c) (CC:5C) [09:53:15:803]: Produkt: Adobe Reader XI (11.0.04) - Deutsch -- Installation fehlgeschlagen.
MSI (c) (CC:5C) [09:53:15:804]: Das Produkt wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Erfolg- bzw. Fehlerstatus der Installation: 1642.
MSI (c) (CC:5C) [09:53:15:806]: MainEngineThread is returning 1642
=== Verbose logging stopped: 24.01.2014 09:53:15 ===
Do you have any hints what could be the problem?

Have adobe reader 8.3.1 windows xp sp3 reader not working right and it wont let me remove or update

I have adobe reader 8.3.1 on system windows XP SP-3. Reader not working correctly but it wont let me remove or change. I down loded Reader XI (11.0.2) but it will not open because of reader 8.3.1. How do I deactivate 8.3.1 and remove it? Reader 8.3.1 installed 9/14/2011. update ID (AC765BA86-7AD7-0000-2550-7ABC-40000831)

You can try using this tool to remove all traces of previous version(s) of Reader:
http://labs.adobe.com/downloads/acrobatcleaner.html
Then, you may download the offline Reader installer from
http://get.adobe.com/reader/enterprise/
After downloading, restart your computer and run the installer before doing anything else.

Adobe Reader 9.5.1

When I tried to unistal Adobe Reader 9.5.1 - CPSID_83708,a message came saying this update cannot be removed. The update ID: {AC76BA86-7AD7-0000-2550-TA8C40000951}. WHY?

Try the cleaner tool: http://labs.adobe.com/downloads/acrobatcleaner.html
Then install Reader 9.5.1 or 10.1.3

Update 8.1.0 will not finish install

Hello all! I'm running Acrobat 8.1.0 Std on a Win 2003 Server Terminal Server. I am getting errors Event ID 1000 that says:
Faulting application ds4.exe, version 4.99.1.0, faulting module msvcrt.dll, version 7.0.3790.3959
So I open Acrobat > Help > check for updates and it starts a 6 MB download of V8.1.3 Standard Update.
This seems to unpack and copy files then pops up "Adobe Acrobat 8.1.3 Standard Update failed to install."
This generates an EventID 11708 that says:
Product: Adobe Acrobat 8 Standard - English, Français, Deutsch -- Installation failed.
And an EventID 1023 that says:
Product: Adobe Acrobat 8 Standard - English, Français, Deutsch - Update '{AC76BA86-A660-0000-2550-7A8C40000000}' could not be installed. Error code 1624. Additional information is available in the log file C:\DOCUME~1\richm\LOCALS~1\Temp\21\MSI418d6.LOG.
That log file tells me:
MSI (s) (90:A0) [16:27:27:755]: SOURCEDIR ==> D:\data\installs\adobe_standard_8\Adobe Acrobat 8 Standard\
MSI (s) (90:A0) [16:27:27:755]: SOURCEDIR product ==> {AC76BA86-1033-F400-BA7E-000000000003}
MSI (s) (90:A0) [16:27:27:755]: Looking for file transform: W:\WINDOWS\Installer\107bcb.mst
MSI (s) (90:A0) [16:27:27:755]: Unable to create a temp copy of transform 'W:\WINDOWS\Installer\107bcb.mst'.
MSI (s) (90:A0) [16:27:27:755]: Note: 1: 2203 2: W:\WINDOWS\Installer\107bcb.mst 3: -2147287037
MSI (s) (90:A0) [16:27:27:755]: Couldn't find cached transform W:\WINDOWS\Installer\107bcb.mst. Looking for it at the source.
MSI (s) (90:A0) [16:27:27:755]: Looking for file transform: D:\data\installs\adobe_standard_8\Adobe Acrobat 8 Standard\107bcb.mst
MSI (s) (90:A0) [16:27:27:755]: Unable to create a temp copy of transform 'D:\data\installs\adobe_standard_8\Adobe Acrobat 8 Standard\107bcb.mst'.
MSI (s) (90:A0) [16:27:27:755]: Note: 1: 2203 2: D:\data\installs\adobe_standard_8\Adobe Acrobat 8 Standard\107bcb.mst 3: -2147287038
DEBUG: Error 2203: Database: D:\data\installs\adobe_standard_8\Adobe Acrobat 8 Standard\107bcb.mst. Cannot open database file. System error -2147287038
Some other posts in this forum suggested downloading the stand-alone version of the 8.1.3 update, which I did. When I run AcrobatUpd813_all_incr.msp is pops up "The upgrade patch connot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program."
When I try to get support it tells me the Product Key is invalid, yet under Acrobat Help > Activation both the "Activate" and "Deactivate" options are greyed out. When I tried Adobe Tech Support Chat they told me to call support 800-642-3623 and could not offer any help at all.
I'm thinking of trying to uninstall and reinstall late-night when nobody is on the server and then try the updates again. But I'm afraid my key will be bad and my users won't have the Acrobat to use the next morning and I certainly don't want to buy a another version if I already have a registered version!
Anybody have any ideas on the .exe error or the .dll error or how to work around these install/upgrade issues? Or how to resolve the activation error?
I'm all ears! Only thing is I have a small time window late-night if I need to reboot.
Thanks in advance :-)
FilthyStinkinRich the Admin in CLE OH

okay, I will try to help you.... which program from microsoft needs updating? Maybe you need to go to microsoft's website and download from there *making sure you have chosen to save it where-ever, then run it* As for your emails, I don't know. Save your incoming and outgoing email settings, then delete your old user account, set up a new one, typing in needed info where appropriate. I think there is also a spam/junk filter in there somewhere. Perhaps you need to talk to your ISP (internet Service Provider) to see what they can do. I have never heard of someone being hacked into thru email
oh, and one last thing. This is a common mis-understanding. This part of the Apple forum is for Mac Pro's ( the big desktop towers) and you have a macbook Pro, which is portable. If you can please post your question in the appropriate forum, that we may be able to help you better
thank you
John B

Reader 11.0.03 Update?

We use System Center Update Publisher (SCUP) to deploy Adobe Reader updates. We have several machines with Reader 11.0.02 that fail to install the update saying that it is the wrong version:
"Adobe Reader XI (11.0.01) - Update '{AC76BA86-7AD7-0000-2550-7A8C40011003}' could not be installed. Error code 1642." The log shows 11.0.01, but these machines are actually 11.0.02.
I noticed a couple other threads that seemed to suggest that you must uninstall Reader 11.0.02 and 11.0.01 from client computers to then be able to install the 11.0.03 update. I'm pretty sure that I misunderstood because security bulletin released by Adobe says "Adobe has released security updates for Adobe Reader and Acrobat XI (11.0.02) and earlier versions for Windows"
(http://www.adobe.com/support/security/bulletins/apsb13-15.html).
And really that would be totally ridiculous to have to uninstall previous Reader updates just to install a new update.
Also, our software update scans (through SCCM - imported into WSUS via SCUP) are showing that these Reader 11.0.02 machines don't need the 11.0.03 update. Again, based on the bulletin, that doesn't seem right either.
So my question is:
Am I going to have to deploy a separate script to our enterprise that uninstalls Reader 11.0.02 and 11.0.01 from client computers just so the 11.0.03 updates will install?
-Or-
Are our computers with Reader 11.0.02 really OK without 11.0.03?
Mike

I tried something new and it seemed to work for me this time. So now, I think I have some more information that gets me closer to understanding the issue we are seeing.
Our packaging team has recently taken over the packaging of Adobe Reader and I noticed that they have a different AIPs for each version 11.0.x. When I was testing, I previously uninstalled Reader, and reinstalled it from the 11.0.01 slip-streamed AIP that they created (not thinking that it would make a difference) before trying to install 11.0.02 and 11.0.03.
This time, I completely uninstalled Adobe Reader and reinstalled the base install (11.0.0) and then installed all the updates in order, and this time it worked as it should.
So... I believe the reason it failed was that I was trying to apply the update to a client that had a "slip-streamed" installation. If the client started out with the base 11.0.0 installation to begin with, then I'm thinking we shouldn't encounter the issue.
I'm still a little currious as to why the updates won't actually update a computer with a slipstreamed Reader installation (assuming that is the issue).

Applying 9.1.2 to existing admin install point

I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch.
I get the same error on my PC when I double click the msp file
This is the msi log from when I tried to patch the existing admin install of 9.1.1:
MSI (c) (00:58) [16:18:02:876]: Final Patch Application Order:
MSI (c) (00:58) [16:18:02:876]: Other Patches:
MSI (c) (00:58) [16:18:02:876]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000912} - C:\CustomInstalls\AdobeReader\patches\adobe912.msp
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\CustomInstalls\AdobeReader\acroread.msi
MSI (c) (00:58) [16:18:02:876]: Product: Adobe Reader 9.1.1 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000912}' could not be installed. Error code 1642. Additional information is available in the log file c:\adobe.log.
MSI (c) (00:58) [16:18:02:923]: Product: Adobe Reader 9.1.1 -- Installation failed.
Any help is greatly appreciated.

I don't even know why I continue to use adobe products. Adobe software development is a joke. So are their UIs.
First, this forum crashed my FireFox 3.0.10 browser, twice. The second time, I figured out it was Adobe's fault. Why doesn't Adobe learn to script AJAX properly so it doesn't crash browsers? So here I am in IE8 typing a reply.
All of you guys were beating around the bush in regards to the "solution" to this problem. I have found a way to apply the patch and use an MST generated by the Adobe Customization Wizard. Granted, it would be much better if Adobe would just generate their patches correctly to begin with.
As you all have found out, you cannot create an MST using the ACW (Adobe Customization Wizard) and then use the following command
msiexec /i AcroRead.msi /p AdbeRdrUpd912_all_incr.msp /t
This will cause the aforementioned problem. Below is the proper sequence of events:
Make a backup copy of the 9.1.0 AcroRead.msi (just in case).
Run the following command: msiexec /a AcroRead.msi /p AdbeRdrUpd912_all_incr.msp This command will create an Administrative Install Point (AIP) in the directory you choose. I will place it in a directory called Patched The AcroRead.msi file will be rewritten and will be version 9.1.2 (check the Property table with ORCA and look at the value ProductVersion). In addition, the files that were in Data1.cab will be expanded and patched and are in the Patched folder I specified above. At this point, we no longer need the Data1.cab file. If you know how, you could compress all the files back into a cab and insert them back into the media table, but that is overly complicated and I forget how to do it successfully. In any event, the major benefit would be some space savings. If you had a lot of apps like this, it would be beneficial; but for one, not so much so.
Open AcroRead.msi with ACW. Make any changes you want for your installation. However, the following changes must be made or browser integration will be broken (per an earlier post in this thread):
Go to the Registry item in the left-hand menu.
Under the Destination Computer section, navigate to the following key: HKEY_CLASSES_ROOT\acrobat\DefaultIcon.
Modify the (Default) value to the following: [READER]AcroRd32.exe. NOTE: This only applies if you are installing Adobe Reader. If you are installing Acrobat, this may not apply, but I am not sure. YMMV.
This step was updated 10 July 2009 11:30:00 EST (GMT-05:00). If your are performing application virtualization, you will want to make te following changes to the MSI (via ORCA or ACW). I'm making these changes from ACW. The installer will fail during application sequencing during the installation of the Adobe Updater Manager (AUM). For virtualized applications, this component is unnecessary and should not be installed. Other sites lead you through a lengthy, risky process to eliminate the installation of the AUM. This step will eliminate the installation of AUM with two simple changes to the MSI.
In ACW, select the Direct Editor node from the left hand side.
Select the Feature table.
On the right side, locate the features named AUM and Updater. Note that the Level field for both features are 1. Change the Level field for both fields to be 200. Actually, any number greater than 100 will do, but 200 is a nice round number. Since the installer defaults to INSTALLLEVEL=100 (see the Property table), any feature with a Level value of 100 or less will be installed. Since we have now given these features an install level of 200, these features will not be installed. Generally, this tactic can be used on any component you wish not to have installed (for Adobe Reader and some other applcations with simple installers), such as AIR and Acrobat.com. Those are the only two changes that need to be made to not have AUM installed.
To make sure your users don't encounter an error while running Adobe Reader, make sure, in ACW, to uncheck the box Disable all updates under the Online and Acrobat.com Features section.
Save the package (in ACW, File->Save Package). This modifies the setup.ini file so that it will use the changes you just made (saved by default in AcroRead.mst).
I left my original instructions below, but marked as deleted. Please see step 5 below these deleted instructions. This is a new step. If you are performing application virtualization, you want to make the following changes to the MSI (via ORCA or ACW). I'm making these changes via ACW. The installer will fail during application squencing due to not being able to create to two certain registry keys. This is the easiest way that I can think of to get this to work.
Start your sequencing machine (in my case, a VM).
Install Adobe Reader 9.1.x (do not sequence, simply install).
Once installation completes, open the Registry Editor (assuming Windows Vista; if using WinXP or below, try RegEdt32.exe).
Browse to HKEY_CLASSES_ROOT\Installer\Win32Assemblies\Global
Double click the following entry (make sure you get the right one, there are two similar entries!): Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name Microsoft.VC80.CRT.txt
Back in the registry editor, double-click the following entry: policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name policy.8.0.Microsoft.VC80.CRT.txt
Close the registry editor.
Reset your VM so it is clean for the sequencing (i.e. revert to a snapshot).
Back in the ACW, at the Registry portion, navigate to HKEY_CLASSES_ROOT.
Right-click HKEY_CLASSES_ROOT and selet New->Key. Name the new key Installer.
Right-click the Installer key and select New->Key again. Name the key Win32Assemblies.
Create a new key in Win32Assemblies called Global.
Select the Global key you just created.
On the right-side of the editor, right-click and choose New->Multi-String Value. Name the new value: Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Right-click the new value and select Modify
Open the text file Microsoft.VC80.CRT.txt you created aboe.
Press CTRL+A or Edit->Select All (in Notepad) and then press CTRL+C (or Edit->Copy).
Back in ACW, paste the value from the clipboard and click OK.
Now right-click the editor and choose New->Multi-String Value again. Name it policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Open the policy.8.0.Microsoft.VC80.CRT.txt file created above.
Copy the file contents as the value of the new entry in the ACW.
Save the package. You should now be ready to install Adobe Reader via Setup.exe for sequencing.
Updated 10 July 2009 12:00:00 EST (GMT-05:00). We have one more step to perform just to clean things up bit. I'm going to create another AIP using the patched MSI and our newly created MST. However, this does not work quite as one would expect.
Run the following command: msiexec /a AcroRead.msi /t <Your_transform.mst>. I created this AIP in a folder called PatchedTransformed.
The above step created another AIP in the PatchedTransformed folder. What's different about this AIP compared to the one made at the beginning of this procedure is that the MSI file was copied to the PatchedTransformed folder as well. However, the MSI is not merged with the changes from the MST as I expected. There are two things you can do:
Modify the setup.ini file and add the following line to the [Product] section: CmdLine=TRANSFORMS="<Your_Transform.mst>", or
Use ORCA. Open your patched MSI in ORCA. Choose Transform->Apply Transform... and select the transform generated by the ACW. Then choose File->Save Transformed As... and give the transformed MSI a new name, e.g. Custom-AdobeReader-9.1.2.msi.
That's it. You now have a fully patched and modified Adobe Reader installer ready for installation or application virtualization.
At this point, you should have an MSI and MST. If you want, you can use ORCA to merge the MST into the MSI. If you're using Setup.exe, you're going to have to change th Setup.ini file.
To test that everything works, you can copy the files to a test directory and perform the following command: msiexec /a <AdobeReader.msi> [/t <Your_transform.mst>] Replace with the name of your MSI file and optionally, pass in your transform (definitely do this if you made a separate MST!). If all goes well, the installation should go well, too. During sequencing, you will still get an MSI installer error (actually, 2), number 1406, about not being able to write to two registry keys. These were the registry keys we added in the steps above. This does not happen on normal installatons.
Please also note that I don't know whether the roaming user profile problem menioned in http://kb2.adobe.com/cps/404/kb404597.html is fixed in version 9.1.2. It was not fixed as of 9.1.0.163. This is all posted AS-IS. YMMV.
UPDATE:
In case you don't know, I will share a bit of enlightenment I had with my procedure above. This specifically relates to application virtualization and sequencing Adobe Reader for MS App-V.
In step 4, I had you install Adobe Reader on a clean machine and obtain some registry information because otherwise, the installation may not be successful for virtualization. These steps are unneccessary. Here's why: you cannot "patch/upgrade" vitualized applications within the application itself. To patch/upgrade a virtual application, you have to use (in the case of MS App-V) the Application Virtualization Sequencing MMC to load the virtualized app, then run the upgrade/patch so that MS App-V can detect the changes and properly update the package. So what does this mean? Two things. First, whenever I use the ACW, under the Online and Acrobat.com Features section I always uncheck <b>Disable all updates</b>. However, checking this does not necessarily mean Adobe Reader does not install the Adobe Update Manager (AUM); in fact, it does install AUM, which is the feature that contains the component that attempts to write those registry entries and therefore, which is causing the error.
Therefore, the solution (and what should be step 4) is to disable the installation of AUM. Now some have posted at various sites how to disable the installation of AUM by deleting a whole bunch of stuff in the MSI. This is not necessary. The steps are outlined in the new step 4 above. This should resolve sequencing issues.
UPDATE 10 July 2009 12:00:00 EST (GMT-05:00) - Pertains to virtualizing Adobe Reader only.
This doesn't work for virtualizing the application. When importing the application into MS App-V Server Management Console, the application version is still 9.1.0.163 even though the splash screen says 9.1.2. I think that my assessment is correct because of two reasons: 1) I still got the MS VC++ Runtime error when using a normal user with a roaming profile which Adobe said the latest 9.1.1 release fixed (and hence 9.1.2) (the AppData folder included) and for which Adobe's solution is a joke; 2) When I installed my "patched" Reader (as a normal install) with AUM and proceeded to go to Help->Check for Updates, the 9.1.2 update appeared in the list of updates (again, even though the splash screen said it was version 9.1.2). Adobe has got to get their patchng correct!!!
For application virtualization, I'm going to recommend that you sequence the 9.1.0 version through to completion. Then, save the sequence and close it. Then re-open the sequence project for upgrade and applythe 9.1.2 patch. Whether you can use an ACW transform on the 9.1.0 installation and then patch, that's debatable. I sure hope so. If not, perhaps there's a way I can fudge it, namely, create an MST via ACW. Then, manually create an MST with the pertinent settings via ORCA and see if that works, instead.
Having said all that, I seriously doubt this works at all even for GPSI deployment. Sorry all. Will post again when I finally get this application to sequence. Hopefully, the same principles will apply to GPSI deployment.
Message was edited by: TTEConline on 10 July 2009 12:00:00 EST (GMT-05:00)

Error updating Reader to 8.1.6

Is anyone else getting a version not found error while upgrading Adobe Reader 8.1.5 to 8.1.6? I've also tried updating 8.1.4 from an administrative installation point but I get the same error.
Below is the log from msiexec:
MSI (c) (B8:14) [17:27:42:550]: Final Patch Application Order:
MSI (c) (B8:14) [17:27:42:550]: Other Patches:
MSI (c) (B8:14) [17:27:42:550]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000816} - C:\Temp\AdbeRdrUpd816_all_incr.msp
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\WINDOWS\Installer\dc83.msi
MSI (c) (B8:14) [17:27:42:550]: Product: Adobe Reader 8.1.5 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000816}' could not be installed. Error code 1642. Additional information is available in the log file C:\adobe.log.
MSI (c) (B8:14) [17:27:42:566]: Product: Adobe Reader 8.1.5 -- Installation failed.

Option 3:
     1) Installed from an 8.1.3 patched incrementally to 8.1.5 and an 8.1.5 AIP created with Adobe source files, and customized with the adobe tuner.
     2) attempted to patch via SMS (using DFS links, not Distribution Points,) verified patch failure by running with the classic double-click method on a few test machines
     3) Cried in defeat
Curiously, I've discovered that the patch works if it's run locally, but does not work if it runs from a network share. I think my solution is probably going to be to write a script that copies it to each machine before running the SMS program with elevated privileges.
EDIT: looks like I was mistaken about the deployment scenario, our current production machines were actually reinstalled with an 8.1.4 AIP, and that seems to be the breaking point. A new installation from the 8.1.3 AIP can be patched up to 8.1.6, no matter what incremental patch level it's currently at. Seems to be a mismatched product code issue?

Adobe Readrer IDAC76BA86-7AD7-0000-2550-7A8C40000000

Similar Messages

Maybe you are looking for