New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 685574 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 674421
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Error when updating to 56.0.2924.76

Reported by andey.mi...@gmail.com, Jan 26 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Go to Settings
2. Click "About"
3. An error is occurred while updating

What is the expected behavior?
Update is successfully done

What went wrong?
 An error occurred while checking for updates: The installer encountered error 42. (error code 7: 0x80040902: 42 -- system level).

Did this work before? Yes Previous update

Chrome version: 55.0.2883.87 m (64-bit)  Channel: n/a
OS Version: 10.0
Flash Version:
 
update error.png
38.3 KB View Download
Labels: Needs-Triage-M56
Cc: ranjitkan@chromium.org bustamante@google.com nyerramilli@chromium.org ligim...@chromium.org
Labels: -Pri-2 M-56 Pri-1
Owner: grt@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: Error when updating to 56.0.2924.76 (was: Update error 55.0.2883.87 m (64-bit))
I also encountered an error when updating from chrome 54.Chrome got updated to -56.0.2924.76 after second try.

Some users are reporting the same in release blog.

https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html

Assigning to Greg for further investigation.
Update_error.png
37.7 KB View Download
andey.misnikov@ can you please refresh chrome://chrome tab or exit and relaunch Chrome should update to Chrome 56.0.2924.76.

Comment 4 by grt@chromium.org, Jan 27 2017

Mergedinto: 674421
Status: Duplicate (was: Assigned)
ligimole@: the error you encountered is being tracked in  issue 685960 .

OP: another user is reporting the same problem as you have reported in  issue 674421 . I will dup this into the existing issue. I am so far unable to reproduce this.
Ctrl + F5 resolve this issue. Thanks

2017-01-27 2:16 GMT+03:00 pbomm… via monorail <
monorail+v2.2239043687@chromium.org>:

Sign in to add a comment