Update Failed, Error Code 11
Reported by
asfoste...@gmail.com,
Nov 5 2016
|
|||||||||
Issue description
Chrome Version : 54.0.2840.87
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox: OK
IE:
What steps will reproduce the problem?
(1)Downloading from Google site and installing the latest version.
(2)
(3)
What is the expected result? Normal auto update
What happens instead? Some websites load only text with no Graphics
Please provide any additional information below. Attach a screenshot if
possible.
,
Nov 8 2016
Sorry , Attaching screen shot. Thanks!
,
Nov 9 2016
When I go to the download site to get the latest Chrome version, and then download and install, the version that is listed along with the error code (Error 11), is 54.0.2840.87. This seems to not be the actual latest, as your email information shows version 54.0.2840.90 as the latest. How can I get access to the ".90" version?? To clarify, the error still exists, even with a fresh install of version ".87". Andrew
,
Nov 9 2016
That sounds like a Keystone error. Andrew: Is this on a Mac?
,
Nov 9 2016
Yes! A MacBook Pro running Sierra 10.12.1. I'm attaching the "Hardware Overview" from "About This Mac" Andrew
,
Nov 17 2016
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 23 2016
Unable to reproduce the issue with chrome latest stable #54.0.2840.98 on Mac 10.12.1. Tried upgrading from 54.0.2840.87 to 54.0.2840.98. upgraded successfully. @Andrew: Could you please re-check with latest stable and update.If possible please go through the below link for more information. https://support.google.com/chrome/answer/6284476?hl=en&ref_topic=6328697 Thanks in Advance!
,
Nov 24 2016
I upgraded to version 54.0.2840.98, but the same error exists, as follows: Update failed (error: 11) Error details: The operation couldn’t be completed. Operation not permitted [NSPOSIXErrorDomain:1] KSServerUpdateRequest fetch failed. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain: 702 - 'https://tools.google.com/service/update2?cup2hreq=f0ab38dea091ed93639731625282ce0dfee019966283654d5c 6183969cb5f0f9&cup2key=5:999884908'] (The operation couldn’t be completed. Operation not permitted [NSPOSIXErrorDomain:1]) Andrew
,
Dec 1 2016
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 7 2016
+borisv for error in #8
,
Dec 7 2016
Is the error 11 above consistent? Can you try reloading the chrome://chrome page? If yes, can you try to press the button "Enable Updates for All Users"? If this doesn't help and the error persists, please open Terminal app, run the diagnostic command below (as one line) and attach the generated .zip file with the logs for us to investigate. /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
,
Dec 7 2016
Error is very consistent, now for about 6 weeks. Reloading page has no effect. Can't find the button "Enable Updates for All Users". Where is this button? In some drop-down menu?? I'll try the diagnostic command and send results in another message. Andrew
,
Dec 7 2016
Results: KSDiagnostics-502835232.143397.zip Hope it helps! Andrew
,
Dec 7 2016
Thank you, Andrew. I do not see an attachment, though. Can you re-attach the file 'KSDiagnostics-502835232.143397.zip' from your Desktop?
,
Dec 7 2016
KSDiagnostics-502835232.143397.zip Not sure why it didn't get thru before??
,
Dec 8 2016
Still not getting thru. It is possible that one of my colleagues have detected a PII in it and have removed the attachment, as the bug is publicly visible. Unfortunately, older versions of the updater did not sanitize the usernames on the machine (e.g. "borisvidolov") that are logged in the paths, e.g. "\Users\borisvidolov\Library\Google". Do you mind emailing the file directly to me at borisv@chromium.org? I will post back here my findings from the logs.
,
Dec 8 2016
I think I was not attaching the file correctly! My mistake in my haste! See attached.
,
Dec 8 2016
Andrew, thanks for sending me the logs. It seems like Google Software Update is not able to talk to the server at all. The initial error was that internet is offline (on November 30th before 3pm) and ever since the error above appears. Do you remember doing any installation on November 30th - maybe an OS update, firewall or antivirus? Overall, the updater is several months old. We did a few improvements in that area, including significantly more logging. Could you try installing the latest version from here: http://www.google.com/dl/release2/5b/auto/GoogleSoftwareUpdate-1.2.6.1370.dmg 1. Download the image from above. 2. Open it and open the application "Install Google Software Update.app". After you install it, please try navigating Chrome to chrome://chrome and let us know if the problem persists.
,
Dec 8 2016
Will do the install soon. Don't really remember what I did on Nov 30th. Let's see what happens. Will update soon. Andrew
,
Dec 8 2016
OK. Install completed, but no change in error condition. See attached screen copy. Andrew
,
Dec 8 2016
Sorry about that, Andrew. Can you re-run the diagnostic tool and send me the new .zip file to borisv@chromium.org? We should produce more details in the logs now.
,
Dec 9 2016
I worked directly with Andrew to identify the problem. It turned out to be a third-party antivirus software (Intego) blocking the updater from communicating to the network. I will try to reach to Intego to see if we can get an exception by default for the updater, so that the user Chrome instances are not kept outdated.
,
Dec 27 2016
As per comment#22 removing "Needs-Review" Label. Thank you.
,
Dec 28 2016
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rbasuvula@chromium.org
, Nov 8 2016Components: Internals>Installer
Labels: Needs-Feedback