It's still happening - but with a slight twist. A few days after the original report above, Chrome's menu icon went green, and the 'you need to update' item was there at the top of the menu. So I went ahead and clicked that, and everything appeared to work. However, I wanted to check what the new version was. So I checked via Help/About, and it showed the same version as in the original report above - and, as in the original report, said that it was ready to update if I clicked 'Relaunch'. Didn't want to waste my time with that, so I just closed the window.

Then a few days later, the menu icon went green again, but I ignored it until today when it went red. So I went through the whole thing again. The update appeared to work, but when I checked the Chrome version, it hadn't changed, and it again wanted me to click 'Relaunch' in order to update.

I would be nice if someone would please take a look at this ... Thanks in Advance ... Ian

... and it just happened again. Menu icon went to green bars yesterday, then red today. So I tried the 'update'. It all appeared to work, but once again, when I went to Help/About Chrome, it is still showing the exact same version.

Clearly Chrome has managed to get itself very confused about something !!!

... and it happened again. Same as my previous comment, but with the added data that Session Buddy shows that Chrome only relaunched 27 windows with 69 tabs, instead of the 31 windows and 78 tabs that I had just saved before attempting the 'upgrade'.

Very disappointing that no-one seems to have looked at this yet !!!!!!!!!!!

... and it happened again, although this time I did the 'upgrade' while the icon bars were still green.

This time it looks as though Chrome 'only' managed to lose 1 window with 4 tabs in it out of 32 windows containing 80 tabs.

Hi Ian. Apologies for the delay in helping you investigate this. It sounds to me like there's an inconsistency between some values in the Windows registry and with the actual version of Chrome on your system. Would you please check the version number in these two places:
1. The file version of chrome.exe (probably C:\Program Files (x86)\Google\Chrome\Application\chrome.exe).
2. The "pv" registry value for Chrome's registration with Google Update.

For #2, you can try the following command from a cmd.exe prompt:

c:\Windows\SysWOW64\reg.exe query HKLM\Software\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}

Attach the output of that command to this issue so I can see if there's anything else amiss there.

Thanks.

Thanks for the response.

Actually, it appears that Chrome finally managed to fix itself by doing a 'real' update to version 51.0.2704.106 m.

Since I didn't actually initiate this I'm guessing that it happened when I did a Windows 10 update on Tuesday.

Hopefully it won't recur !!!

Thank you for providing more feedback. Adding requester "grt@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

Thanks for the info. I'll close this out for now. If it happens again, please re-open and add the info requested in comment 5 and we'll see what we can figure out. Cheers.

Thanks!