How To Fix Updater Process Ended With Error 1

[Taneka Tarring]

ButI found this morning that all EWC and EWC+ connected accounts would not update during OSU nor Update Now. OSU would start properly and would show that the update process was occurring but very quickly the update process ended. No error message was received but these accounts did not update.

What I did then was to do Reset Account for each of the EWC and EWC+ accounts. This set up the connections, again, as if they were new connections. So I needed to be careful to Link the downloads to the correct accounts already in Quicken.

Thanks. My issue doesn't appear to be as complex as yours, as I only had to recover from a single failure. I have gone through procedures like yours in the past and will keep them in mind for the future. My main gripe was that the error message gave me no hint that I was experiencing a problem I could clear up.

Quicken did provide a solution for a simple "server is unavailable" issue: Wait 10 minutes and try again. And that usually works pretty well if it's just a temporarily busy server or Internet connection issue.

However, when the issue is more complex like this one was there is no simple fix that can be put into a popup. Those popup messages are mostly designed to advise that an issue was encountered and what the basic issue was, not to lay out all of the possible root causes and possible fixes. Then, when appropriate, we need to start the troubleshooting process via Quicken Support (web, Chat, Phone), Quicken Help and/or Quicken Community. They are all great resources when deeper dives into an issue need to be done.

In this particular case (at least for me), it appears the cause was the Cloud Account got corrupted so it could not communicate properly with the server. Sometimes doing something simple like Sign in as a different user or Reset your Cloud Account will resolve Cloud Account corruptions. But other times it requires a more extreme measure like deleting the Cloud Account entirely and then letting Quicken rebuild it from scratch. In my case, deleting the Cloud Account was necessary because the other steps did not resolve the issue, so that is what I posted.

Tank you for posting this detailed information on the error and the update on how you fixed it. The reason balenaEtcher is writting to your Documents folder, is because it is storing its settings into a subfolder of your documents folder.

I noticed that the removal process was not complete. I used the Apps & Features to select and remove balenaEtcher. However, I saw that it left behind:

C:\Users\AppData\Local\balena-etcher-updater\installer.exe

After most recent update to Sonoma 14.0, all access to my iCloud account is gone - passwords, etc. are gone and I cannot re-establish the link between my laptop and my iCloud account. And it cannot log out of my iCloud account, that throws an error. I can log in via a web browser, but the OS is not syncing correctly to my iCloud account.

This issue is still not resolved 2 months later. I just updated to Sonoma 14.2.1 hoping it might help but quite the opposite. The Apple ID panel has now completely disappeared from Settings but my mac continues to sync with my iCloud account - e.g. I can see new photos take on my iPhone etc. When I select Internet Accounts in setting, my iCloud account is visible but as soon as I click it, I get the "Extension process Apple ID exited" error message. I checked the system logs and noticed that I can consistently generate a crash report - JetsamEvent - every time I try to open iCloud account in settings. So from what little knowledge I have about macs it seems that opening iCloud settings is somehow creating memory pressure that forces the process to quit?

You need to go to "Internet Accounts" in system settings, click on the icloud tab (which you can see in the image below) which will take you to another page where you can log in to your icloud account. Then that should just update icloud. Hope that works for you. It seems to have worked for me.

This started happening for me after switching Apple ID off and on to solve a sync problem; working with Apple Sr. Advisor on phone. Now on Sonoma 14.2.1, same result reported above: System Settings... Name/AppleID... gives "Extension process Apple ID (##) exited". I've tried all the suggestions mentioned above.

I also have the same problem on my MacBook after update to Sonoma. I have tried logging out of the Apple ID on my Mac but when I click Apple ID or Internet Accounts in System Settings it comes up blank or I get the "extension process exited..." error message. I have also tried removing my MacBook from the account under Apple ID/Devices settings from a browser but that does not have any effect. Finally, I tried setting up a new account on my MacBook, with the same Apple ID, which solved the issue for half a day but the problem re-occurred. I have two other accounts on the same MacBook with different Apple IDs and those are fine so the problem appears to be specific to the Apple ID. I have 3 other Apple devices (1 MacMini and 2 iPads) and I am able to access my Apple Id from System Settings on those devices without any problems. My Photos app on my MacBook updates so it is still connected to my Apple ID but I just cannot access Apple ID from System Settings....totally stumped!

That command deleted the profile picture which apparently was corrupted. After that I removed the MacBook from my iCloud using my iPhone. MacBook detected that and asked to re-enter the password. And now everything works fine.

I already posted a robust solution in this very forum that works to remove this problem (and has mysteriously disappeared from this thread?). Trying again. This is an iCloud issue after updating. Hopefully, you should still be receiving the error message above. If you've already done some of the other kludges posted herein, and are not still receiving this error message, this may not help you.

I was chatting and getting phone support for a total of 4+ hours. They managed to get me back into my MacBook but I had to sign out of my iPhone and log into the account that was connected to my MacBook. In addition to this I was told that I had to use my iPhone to do it. Can't remember all of the steps because it was literally trial and error (bless the representatives that had to help me because they remained patient while they too were trying to figure out trick after trick, hack after hack to get back into my computer. Anyway, after disconnecting the call, thinking that the problem was resolved, the Terms and Conditions message popped up in my MacBook settings, I clicked on it thinking that I would be allowed to accept it, but here we were again..it gave me the Settings Error Message!!! I say this to say, even when the problem appeared to be fixed it created other problems on my computer and MacBook, smh. If I knew that one update would cause so much strain I would've left it alone until my computer absolutely needed it because this is too much!!

I am not sure that I lost access to iCloud, but I was getting a message like that in System Settings with a fresh install of Sonoma--no data carried over--and I was getting a popup saying that I had to agree to a new iCloud agreement, but I just kept getting similar errors in System Settings. What seemed to help was signing out of my AppleID on the Mac and then signing in again. This also asked me for my phone password, and the Mac Password, so maybe that's part what was bugging the software. I don't know.

Is there a possiblity to get this running without doing a complete new installation?

Is it worth waiting for the next version, so the update will start with the new version ignoring the update process it got stuck.

I got some additional information from these files. NC Update shows me that he can install the stable 16.0.4, but during the update process 16.0.3.0 is downloaded. This zip file (nextcloud-16.0.3.zip) is under /cloudXXX/data/updaterXXX/downloads.

Sad to see how this and other threads about this bug are totally ignored by the team. GitHub threads are closed as if it is not a bug. Not sure this can be used in a serious production environment with this approach.

Hi,

with every update (20.0.4 at the moment) I have the same problem. Stuck in step5, but there is no error given (field is empty). My virtual server has not very much PHP memory (128 MB), so maybe this is the problem, but this is only a guess, since no error message is given.

After some manual updates, I find it most convenient to skip the verification by chnanging the .steps file to:

"state":"end","step":5

However, I always have a bad feeling, fearing that the update ultimately might fail and I have to set up the whole thing from scratch.

It would be nice if the dev team got a look into this problem.

Regards

3a8082e126