what is means, don`t update
Reported by
666...@gmail.com,
Jan 4 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2970.0 Safari/537.36 Steps to reproduce the problem: 1. don`t update,watch this picture 2. 3. What is the expected behavior? What went wrong? don`t update and this question had a Long-term Did this work before? No Chrome version: 57.0.2970.0 Channel: dev OS Version: 6.3 Flash Version: Shockwave Flash 24.0 r0 nop
,
Jan 4 2017
This often indicates a problem with Google Update's registration on the machine. Please try the following from a CMD prompt: > cd %LOCALAPPDATA%\Google\Update > dir (take note of the directory named something like "1.3.X.Y" > cd 1.3.X.Y (or whatever version you have) > GoogleUpdate.exe /regserver This will re-register all of the COM objects. Then, you could try to see if manual Chrome updates start working. Please let us know, we are curious to see the outcome. Also, please let us know what version number you find in the ...\Google\Update directory. Thanks.
,
Jan 4 2017
ok, thanks ,it is done . it is working. 2017-01-04 19:22 GMT+08:00 g… via monorail < monorail+v2.304671779@chromium.org>:
,
Jan 4 2017
We don't know why sometimes registration of COM components for Google Updates breaks down.
,
Jan 4 2017
Great. I'm glad to hear that this suggestion helped. Sorin: assigning to you in case there's more info you can collect from the reporter. If not, feel free to close this out so long as your team has the issue on your radar somehow (is there another bug to duplicate this into?).
,
Jan 9 2017
sorin@ - Could you please update on comment #5. Thanks...!!
,
Jan 9 2017
We are tracking this issue internally but it is not actionable at the moment.
,
Jan 10 2017
please , take new issueon on there and Describe clearly your iusse ,let expert solve it |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Jan 4 2017