Skip to main content
Byers Video
Known Participant
March 1, 2019
Answered

UpdaterStartupUntility Crash (everyday for past 3 months)

  • March 1, 2019
  • 9 replies
  • 20330 views

I start my system and apple's crash reporter opens with "UpdaterStartupUtility quit unexpectedly."

I have sent it, but it only goes to apple, not Adobe, the people that need to fix it.

I have looked on their support pages, yes all of them took an hour to finally decided to come here and see if anyone knows a channel, path, avenue to send this crash report to Adobe about their updaterstartuputility.  here is a sample. there is more.

Process:               UpdaterStartupUtility [576]

Path:                  /Applications/Utilities/Adobe Application Manager/*/UpdaterStartupUtility

Identifier:            UpdaterStartupUtility

Version:               10.0.0.19 (10.0.0.19)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           UpdaterStartupUtility [576]

User ID:               501

Date/Time:             2019-03-01 08:03:39.667 -0800

OS Version:            Mac OS X 10.13.6 (17G5019)

Report Version:        12

Anonymous UUID:        D04D36B4-10EB-3625-7443-63CD4FFB48BB

Time Awake Since Boot: 30 seconds

System Integrity Protection: enabled

Crashed Thread:        3

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:

abort() called

*** error for object 0x7fdf2fc060c8: incorrect checksum for freed object - object was probably modified after being freed.

This topic has been closed for replies.
Correct answer Jeffrey_A_Wright

The obligatory total cleanup and re-install as a possible solution is not only something that worries me, but annoys (to put it nicely) me too. It can't be that professional used software puts such a burden on its users. I use Photoshop CC 2019, so I doubt if this one is even the culprit. When receiving help from Adobe via a remote session, the person removed also virtually all background tools and reinstalled them, killing all running adobe processes, made a new user account etc. etc. It did not help. This is absolutely a problem on the Adobe-side. In my case it started out of the blue somewhere last month.

I understand that software is made by humans and that glitches and bugs do happen. If however it's the tool that mainly arrange DRM, subscription checking, updates etc and the main software runs fine, this is a bit of a blamage that should be repaired as quickly as possible. Also keep in mind that this problem might be much more widespread then Adobe thinks. Most users don't check the Console files on their Macs, probably can't even find it. I checked it because of the mentioned Adobe Desktop Services-crash, probably somehow related to the main error we're talking about here.

My humble suggestion would actually be that Adobe stops using the whole Creative Cloud Manager and all its associated tools and offer that as an option for people who really can't live without it. Offer all the apps seperate in de Mac app store and let that handle updates. Never have any problems with that. In other words: do what Microsoft did with Office (365) software. It would save a lot of headaches all over the world.


Ok, thank you all for the additional feedback.  The suggestions offered in post #5 do not appear to be allowing individuals to resolve this error.  Please contact our support team at Contact Customer Care for direct assistance with resolving the error.  You can use the process listed in View Adobe Support cases to update your support case if the error is not fixed during your first interaction.

I am very sorry that many of you are facing problems with the update mechanism. I am locking this discussion as any additional discussion on the topic will not resolve the error.  Please open a support case so that the error can be fixed.

9 replies

ronalds85227042
Participant
March 19, 2019

Hi!

Yet another victim here! ’Fighting’ with it since February. Had a loooong session with Adobe, they did a lot of things via remote help, including reinstalling Creative Cloud and some other tools. But nothing solved it. In the end, the advice was to leave if as it is since - in my case - Photoshop and Lightroom work fine and get also updated. Basically the same advice I read here. Besides uninstalling and running cleaning tools which I really do not have time for, since  use my computer for work, too many deadlines. Only ’side effect’ is that sometimes Adobe Desktop Service crashes, but that seems to resolve itself by restarting after that happens.

What I did NOT like about the helpdesk is that they told me this was an unknown problem. I see that it is widespread now (also in other threads in different languages it’s mentioned often). But I understand here too that it shouldn’t be a big problem. Hopefully a solution will come up soon, because it’s just annoying. Never had problems with any other software. And the rare occassion that something does go wrong, it’s always releated to some vague Adobe background tool of which I do not have any control. That IS a bit frustrating, to be honest.

By the way: I run the latest versions of Lightroom Classic and Photoshop, plus Adobe Reader. Would it help to remove Reader? Got this idea by reading post #18. Or do I misinterpret the fact that this program is - on my system - probably the only component that uses updaterstartuputility? And if it is advisable to indeed remove, what is a good alternative to Adobe Reader?

Greetings,

Ronald.

Participant
March 20, 2019

Hi Ronald,

I was able to stop the errors by uninstalling Photoshop CS6, quitting Adobe CC Desktop and killing all additional background processes on my computer. Signing back into Adobe CC did not bring back the errors. I've been crash free for three days now.

I am still bothered by the instructions in this thread to completely uninstall and reinstall, run a series of "cleaners" and generally make a hash of one's harddrive in the efforts to clean up the damage of various iterations of software updaters from the past. I am also concerned that I have no easy means of reinstalling Photoshop CS6 if I decide to stop my subscription to CC.

ronalds85227042
Participant
March 20, 2019

The obligatory total cleanup and re-install as a possible solution is not only something that worries me, but annoys (to put it nicely) me too. It can't be that professional used software puts such a burden on its users. I use Photoshop CC 2019, so I doubt if this one is even the culprit. When receiving help from Adobe via a remote session, the person removed also virtually all background tools and reinstalled them, killing all running adobe processes, made a new user account etc. etc. It did not help. This is absolutely a problem on the Adobe-side. In my case it started out of the blue somewhere last month.

I understand that software is made by humans and that glitches and bugs do happen. If however it's the tool that mainly arrange DRM, subscription checking, updates etc and the main software runs fine, this is a bit of a blamage that should be repaired as quickly as possible. Also keep in mind that this problem might be much more widespread then Adobe thinks. Most users don't check the Console files on their Macs, probably can't even find it. I checked it because of the mentioned Adobe Desktop Services-crash, probably somehow related to the main error we're talking about here.

My humble suggestion would actually be that Adobe stops using the whole Creative Cloud Manager and all its associated tools and offer that as an option for people who really can't live without it. Offer all the apps seperate in de Mac app store and let that handle updates. Never have any problems with that. In other words: do what Microsoft did with Office (365) software. It would save a lot of headaches all over the world.

Participant
March 16, 2019

I've started receiving this exception daily and on restarts too (EXC_CORPSE_NOTIFY).

The advice in #5 doesn't cut it. Thanks for ruining my weekend!

while we're at it, can you fix your updater so it doesn't trick me into installing Acrobat DC if I accidentally click "Update All"? Thanks.

Participant
March 13, 2019

Same issue here. Is there a known fix yet?

peterm32071317
Participant
March 9, 2019

I too am having the same problems. I uninstalled CC and all prefs per instructions and yet, 2 days later I get the message again. Will this be addressed in any updates? Very frustrating

Participant
March 8, 2019

Same issue over here, started around the time I installed Acrobat

basoct
Participant
March 7, 2019

Adding my two bits. This started happening to me on 3 different machines. They all Macs that Have current CC subscriptions with Acrobad, Illustrator, In-Design and Photoshop installed. They were at the time all running 10.13.6 and I tried to upraise one of the machines to 10.14.3 and the error still persists. I have since upgraded all the machines to 10.14.3 and the error persists on all 3 machines. So, ADOBE, clearly this is a problem and we will await your response for a solution.

Jeffrey_A_Wright
Community Manager
Community Manager
March 7, 2019

Moving this discussion to the Creative Cloud Download & Install forum.

For those facing errors with the Adobe UpdaterStartupUtility please try the suggestions in message #5 of this discussion.  Only a complete removal of all installed Adobe software will allow the update component to be removed.

If you continue to encounter errors or would like assistance with determining why the UpdateStarterUtility continues to crash on the computer then please contact our support team at Contact Customer Care.

Byers Video
Known Participant
March 7, 2019

Jeff A Wright

If I leave it alone will it affect anything? obviously, I am still able to use the apps without any problems.

I just do not have the time to remove and install the apps. some of us are on 1.25 Mbps per second download and .50 Mbps upload. Odd I know. But out in the woods in northern California, that is all we have to choose from. We whine and moan, but no amount of money will change that. They have no plans of giving us real dsl out here.

So it takes an hour to update an app. and it took many hours to install everything I needed.

PlayFire_1
Participant
March 7, 2019

Same issue

rocess:           UpdaterStartupUtility [445]
Path:              /Applications/Utilities/Adobe Application Manager/*/UpdaterStartupUtility
Identifier:        UpdaterStartupUtility
Version:           10.0.0.19 (10.0.0.19)
Code Type:         X86-64 (Native)
Parent Process:    ??? [1]
Responsible:       UpdaterStartupUtility [445]
User ID:           501

Date/Time:         2019-03-07 01:40:03.357 -0500
OS Version:        Mac OS X 10.14.3 (18D109
Participant
March 4, 2019

I have the same issue. I've been through with an Adobe Support Specialist a couple of times who took over my computer and did all their bits and the error went away. (They reinstalled the Adobe Cloud Updater.)

However, although I stopped having that issue on startup every morning, consequently, Adobe Acrobat would not launch. No amount of reinstalling would fix that so had to go back to an Adobe Support Specialist who then took over my computer and managed to reinstall Adobe Acrobat (in a different method than I did.) Finally I could use Acrobat again with no error...

But guess what - the original problem returned. So I guess I have to put up with this update error every morning because the alternative seems to be that Adobe Acrobat doesn't run.

Kinda think Adobe should fix this though...!

David__B
Adobe Employee
Adobe Employee
March 1, 2019
Byers Video
Known Participant
March 1, 2019

Thank you David__B. I did not know which area to put it in...

Jeffrey_A_Wright
Community Manager
Community Manager
March 1, 2019

Byers-video, I am sorry that you continue to face errors with the updater application crashing randomly on macOS 10.13.6.  Can you please list all installed Adobe software and the version to this public forum discussion.

When did you start facing this error?  Are you facing problems with any other Adobe applications or components?  Finally, is there anything preventing you from updating to macOS 10.14.3?