Skip navigation

Adobe Updater hangs, never finishes installing

Nov 15, 2007 3:40 PM

  Latest reply: jimmydtx, Apr 8, 2011 11:27 AM
Replies 1 2 3 4 3 Previous Next
  • wkathym
    Currently Being Moderated
    100. wkathym,
    Sep 29, 2008 1:29 PM   in reply to (Mike_Shanholtz)
    Report
    Hi, I had posted this on another thread, but wanted to add my 2 cents here. This is quite annoying.

    G5, 10.4.11
    Over the past few months, I've tried to use the updater and it always hangs at Start Meeting. Runs all night but doesn't get past about a third of the way. There must be a solution to this.
     
    |
    Mark as:
  • Currently Being Moderated
    101. (Benjamin_Rossen),
    Oct 15, 2008 12:54 AM   in reply to (Mike_Shanholtz)
    Report
    I have been having the same problem with CS3 Updater. It hangs, but worse than just hanging, it freezes all other applications on my system: MacPro OS X. The computer will remain hung for hours unless I force a cold boot (remove power and start up again) after which none of the Adobe CS3 Suite works correctly.

    In order to re-start any CS3 application I must uninstall the entire CS3 suite, and reinstall the CS3 suite. But within hours or days the Updater reappears and the same thing happens.

    After discussions with Adobe support I have been directed to use a utility called 'Clean' that ensures a completely clean start before reinstalling the CS3 suite. I have used this twice at each of the levels of cleaning, and on both occasions re-installed the entire CS3 suite. But each time I have the same problem again.

    Today this has happened for the 5th time. Adobe support had me on music hold on the phone for over 10 minutes, even though I have a case number to type in after listening to their excessively long telephone voice menu, and then Adobe hung up the line on me. Apparently it is not possible to raise Adobe support.

    Each time this happens I lose half a day of work. This has now become a economic problem for me. If this cannot be solved I may put this matter into the hands of a solicitor. Unfortunately, Adobe has become too big, a monopoly, and no longer cares about the havoc that the failures in its products are causing other people. Perhaps a court case will wake them up. contact me if you are interested to start a class action suite.

    b.rossen(at)mac.com
     
    |
    Mark as:
  • Currently Being Moderated
    102. (Benjamin_Rossen),
    Oct 15, 2008 2:46 AM   in reply to (Mike_Shanholtz)
    Report
    And this too (ook dat nog!)

    I phoned Adobe support, and after listening to the excessively long voice menu (asking which product and listing everything under the sun except the CS3 suite) I selected 'other' and entered my case number. I was then kept waiting for 40 minutes before Adobe hung up on me. 40 minutes of listening to ghastly music, and finally getting nowhere. This is not acceptable.
     
    |
    Mark as:
  • Currently Being Moderated
    103. (Kurt_Tappe),
    Oct 15, 2008 6:28 AM   in reply to (Mike_Shanholtz)
    Report
    Adobe Updater continues to cause us headaches as well. I do NOT want it running for any of my users to whom I deploy, and yet it does. If anyone knows how to disable Adobe Updater completely, I would be much appreciative. (Yes, I'm aware of Adobe's official method of disabling it and mass-deploying CS3, but we use standard methods like NetRestore, which precludes using Adobe's custom XML.)
     
    |
    Mark as:
  • Steve Werner
    Currently Being Moderated
    104. Steve Werner,
    Oct 15, 2008 6:57 AM   in reply to (Mike_Shanholtz)
    Report
    It's found in Utilities > Adobe Utilities. Just delete the updater. You can always manually download updates from the Adobe website.
     
    |
    Mark as:
  • Currently Being Moderated
    105. (Kurt_Tappe),
    Oct 15, 2008 8:01 AM   in reply to (Mike_Shanholtz)
    Report
    >Just delete the updater

    No, sorry, it's nowhere near that easy. CS3's self-repair puts the Updater back and runs it after doing so. Removing the self-repair version of the Updater from deep within Adobe Acrobat.app causes Acrobat to no longer launch, complaining that it needs reinstalling.

    As usual, Adobe has no concept of how to design an application for Enterprise.
     
    |
    Mark as:
  • Currently Being Moderated
    106. Buko.,
    Oct 15, 2008 8:33 AM   in reply to (Mike_Shanholtz)
    Report
    With updater installed I always manually update. some of them take a while but they always finish.
     
    |
    Mark as:
  • Currently Being Moderated
    107. (Jonathan_E_Cohen),
    Nov 13, 2008 10:42 AM   in reply to (Mike_Shanholtz)
    Report
    HOW TO SOLVE THIS PROBLEM (THANKS TO RUSSELL STUEVER)

    After getting the infuriating "hang" at installing Flash Lite for Device Central, simply locate Device Central, using Spotlight and launch it. Then fiddle around with a few of Device Central's buttons, doing ostensibly nothing, then quit it. A few minutes later, the Updater freeze comes to an end and the installation finishes. (I launched Device Central twice so I have no idea which one did the trick). But it actually worked. Now, of course, comes the task of finding a valid causal connection for this anomaly.
     
    |
    Mark as:
  • tenortom
    Currently Being Moderated
    108. tenortom,
    Feb 12, 2010 12:46 PM   in reply to (Jonathan_E_Cohen)
    Report

    This happened to me a few times so I repaired permissions, restarted and tried again. It appeared to stall again in the usual spot about 7/8 through the install so I thought I'd just surf for solutions while it was sitting there and it magically finished after about a half hour sitting in the same spot. Who knows.

     
    |
    Mark as:
  • wlaoman
    Currently Being Moderated
    109. wlaoman,
    Jan 13, 2011 5:52 AM   in reply to (Mike_Shanholtz)
    Report

    OK, so I was bitten by this when I tried to install CS3 on my brand new MacBook Pro. Most of the updates installed - after much waiting - but the lllustrator 13.0.1 patch just hung time after time. After many uninstall/reinstalls, and trying just about every trick found here on the forum and elsewhere on the Intertubes, I started to troubleshoot it myself.

     

    Soon I found evidences that pointed towards a "bspatch" process, and after learning about what that is I started to suspect that the Adobe updater is using a version of bspatch that is not compatible with Snow Leopard, Intel Macs, or the combination thereof. So I replaced the bspatch provided by Adobe (found deep inside their updater application) with the bspatch already installed in MacOS and tried to apply the update once more.

     

    Lo and behold! Never before had I seen an Adobe installation work so fast!! Almost the same speed as any other installation I've seen!

     

    Inspired by the success with the 13.0.1 update, I did the same thing with the 13.0.2 update, and is now a very happy camper. (Well, as happy as can be when Ilustrator crashes immediately after start one time out of three...)

     

    Here is what I did:

    1. Download the Illustrator 13.0.1 updater from adobe.com, and double-click the downloaded disk image file (.dmg)

    2. Copy the AdobePatcher application from the disk image to the desktop (or somewhere else on your hard drive)

    3. Right-click on the copy of AdobePatcher, and choose "Show Package Contents"

    4. In the window that is opened, open the folder "Contents" and then "Resources"

    5. In the Resources folder, right-click "PatcherApplication", and choose "Show Package Contents"

    6. In the window that is opened, open the folder "Contents" and then "Resources"

    7. Rename the file "bspatch" to "bspatch_fubar" (or just delete it if you dare)
    8. Start Terminal and type the following command (without the quotes) and press Enter:
          "which bspatch"
        The response should be something like "/usr/bin/bspatch".
    9. Type the following command (without the quotes, but with the space at the end). Don't press Enter afterwards!
          "cp /usr/bin/bspatch "
         If the response in step 8 was not /usr/bin/bspatch, you'll have to replace the "/usr/bin/bspatch" in the command with the response you got.
    10. From the Finder, drag the "Resources" folder that contains the (recently renamed) "bspatch_fubar" file, and drop it on the Terminal window
    11. Now press Enter.
          The Resources folder should now (once again) contain a file named bspatch.
    That's it. Close all the windows and double-click the modified copy of the AdobePatcher, and be amazed (if you are as lucky as I was).
    The Illustrator 13.0.2 updater is fixed in the same way.

     
    |
    Mark as:
  • jimmydtx
    Currently Being Moderated
    110. jimmydtx,
    Apr 8, 2011 11:27 AM   in reply to (Mike_Shanholtz)
    Report

    Same issue with one of my systems and the Device Central 'fix' resolved the issue.  I basically just launched Device Central, mucked with some of the settings, quit the program, and continued (it was still running) the Adobe Updater installation.  It loaded in seconds! 

     

    Launching Acrobat after a clean install often gives a message that Photoshop or some other CS component needs to be run first.  So, it appears that the Suite does need to be 'initialized.'  Perhaps, Adobe Updater needs that, as well.  It would be nice if it also gave you a heads up! 

     
    |
    Mark as:
1 2 3 4 3 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)