Forum Thread: Google Chrome standalone installation's auto-updater

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
Programs

Relating to this vendor:
Google
And, this specific program:
Google Chrome 33.x

This thread has been marked as locked.
mtodorov Google Chrome standalone installation's auto-updater
Member 25th Feb, 2014 13:43
Ranking: 12
Posts: 185
User Since: 20th Mar, 2009
System Score: N/A
Location: HR
Last edited on 25th Feb, 2014 14:03

I am just sitting before a lab in which 75% of computers have Chrome 33.x auto-updated without my intervention. I believe installations are symmetric, but most machines updated and 3 have not.

What makes 3 computers fail to auto-update?

They seem to run similar GoogleCrashHandler.exe process and GoogleCrashHandler64.exe , equally the version with and without completed update.

I check versions with FileHippo update checker.

Options are:

- wait till (or if) automatic update starts
- run Google Chrome and do "About the program" update
- install from FH offered download link

1. I am running Windows 7 and OS restart didn't help.

What to do :-P

Regards,
mt



--
"If a task is worth doing, it is worth doing right. If it is not worth doing well, it is not worth doing." -- Dr. Jack Hyles
<><

mtodorov RE: Google Chrome standalone installation's auto-updater
Member 25th Feb, 2014 14:12
Score: 12
Posts: 185
User Since: 20th Mar 2009
System Score: N/A
Location: HR
SOLVED.

One installation had an error 0x00000000 reported when activating Wrench->About Program Google Chrome.

Second start / stop had done the trick.

The remaining machines seemed to have auto-updated on full hour (2 PM).

Thank you for your attention. I still don't have anything official despite browsing web and submitting to forums. As I single handed maintain over 50 computers, it is substantial for me to have browsers and plugins updated in unattended way.

It would still be the best to have unattended network install with .msi package distribution with GP, but for some reason it didn't work out for me. I am still working on it.

(The maintenance hole in Lab schedule doesn't allow for long admin jobs.)

Regards,
mt


--
"If a task is worth doing, it is worth doing right. If it is not worth doing well, it is not worth doing." -- Dr. Jack Hyles
<><
Was this reply relevant?
+0
-0

This thread has been marked as locked.