Google Update, regularly scheduled
Wednesday, July 1, 2009 | 3:00 PM
Labels: google update, omaha
Client software products have unique challenges, with one of the important challenges being keeping the product up to date. Deploying critical security fixes in a timely and effective manner is one key way that we help keep users secure. Another benefit is that cool new features get deployed and adopted quickly. Google Update is the shared updating infrastructure used by Google Chrome, Google Earth and other Google software that runs on PCs to keep our products up to date on users' computers.
A couple of months ago we released the Google Update source code to give users and developers transparency into our update mechanism. One month later, we released Update Controls that allowed network administrators and advanced users the ability to control the installation and updating of Google products via Google Update.
We hope to help address concerns users have voiced around Google Update running as a continuous process. Until now, Google Update would always run in the background, functioning primarily as a reliable scheduler performing update checks at periodic time intervals. With today's release, Google Update now uses the Windows Task Scheduler to only run at periodic intervals. We have worked hard to ensure that automatic updates work just as reliably, and that our users are just as safe and secure as before.
There are a couple of details that we want to mention. First, in a very small number of cases when Google Update determines that the Windows Task Scheduler or Service mechanisms are not working as expected, we have added in fallback mechanisms that cause Google Update to begin running as a continuous process again to ensure users are still receiving updates to their Google software. Second, if you opted in to sending anonymous usage statistics and crash reports to Google for a particular Google application, we will run a process in the background called GoogleCrashHandler.exe. GoogleCrashHandler.exe is responsible for reporting crashes to Google when they occur in your Google product.
by S. Ganesh, Google Update Team

14 comments:
Fowl said...
Great news! I'm glad to see this whole "listening to customers" thing is finally making its' way around the industry! =P
I have one question though, it might be specific to my box, but
GoogleCrashHandler seems to run all the time - that is even when no GoogleApps are running. Is this how it is supposed to work?
Also, is there ever going to be an option to check for updates only when a particular Google App is started or running? some people I know don't use google apps very often and would be reluctant to even install them if it meant that they would have to pay for data so that they could be updated even when not in use.
Thanks for you support
--fowl from Australia where data costs real money!
July 1, 2009 7:32 PM
primary0 said...
Macs?
July 2, 2009 3:57 AM
West Gone East said...
I just checked my task scheduler in Win XP Pro and have 6 different google update tasks? Can I delete some of them?
Google Software Updater
GoogleUpdateTaskMachineCore
GoogleUpdateTaskMachineUA
GoogleUpdateTaskUserS-1-5-21-1482476501-162531612-725345543-1003
GoogleUpdateTaskUserS-1-5-21-1482476501-162531612-725345543-1005Core
GoogleUpdateTaskUserS-1-5-21-1482476501-162531612-725345543-1005UA
July 2, 2009 5:33 AM
TB said...
That's great! When does the Google Update update rollout?
July 2, 2009 6:43 AM
Roger Karlsson said...
Thanks! Hope other software developers follows your example and start using the Windows Task Scheduler too.
July 3, 2009 2:57 AM
Ross said...
Thanks, but no thanks. I continue to reject the "benefits" of self-updating software. No Google Updater will ever run on a system controlled by me. Period.
July 3, 2009 9:07 PM
Damon said...
OK, at this point it appears that you guys are just hellbent on doing what you want to do, and these "fixes" are mere appeasements.
To say that "we run scheduled, unless WE think it 'needs' to be continuous" seems to flatly ignore the original complaint. Let me try to restate the issue clearly...
I don't EVER want Google to decide when to update MY computer. You don't own my machine, you don't pay for my network connection, and if something goes wrong you certainly won't fix it. And for the smart-alecs in the class, I'm referring to a conflict with another program, not something solved by yet another "automagic update" that you bestow on us through your omnipotence.
I don't care what rubric, model, assessment, or belief system you're trying to enact. YOUR assessment of MY security is of no consequence to me. I want to control MY machine, and those I'm responsible for, AT ALL TIMES. NOTHING is left after ALL.
So there should NEVER be a time when YOU decide what happens on MY machine. This isn't complicated, and this constant cat-and-mouse game about "well we want you to be safe so we'll take over for you" is a Microsoft-esque explanation if I've ever heard one. Can anyone say "Windows Genuine Advantage"?
Google is supposed to be different. Stop with the games and give users COMPLETE control. Microsoft seems to have figured this out with Microsoft AutoUpdate on the Mac. Dare I say it... please follow their lead.
July 5, 2009 10:43 PM
Marcio said...
Thats great! Now I hope every other company follow your path! This way, ppl will have like 400 different update softwares running from time to time and 400 different bug report systems running full time.
When I read things like that I'm really glad im a debian user... with a centralized smart update system...
July 10, 2009 12:11 PM
protopop said...
Damon is right.
Google is deciding what's best for people and despite their good intentions, this is a bad path for a company of this size to follow.
I bought a new computer 2 months ago and I have yet to install any google products on it specifically because of the updater. My last computer had Chrome (i'm a web designer) and Google earth, and I spent a lot of time promoting both products to friends, family and clients -free press for great products. But to be honest now I won't install any google apps on my new, clean machine until this issue is fixed - and i don't mean run as a scheduled task.
This issue is generating bad word of mouth and eroding the goodwill and trust the company has worked so hard to build.
I'm looking forward to using Chrome and Google Earth again once you truly fix this issue.
July 14, 2009 10:18 AM
Vincent said...
I'm not like the others that post previously because I know that Chrome is still a B-E-T-A so your still testing your software. But as a user, not only I aggree with the others in the way there should be a option that allow us to 1- set updates to Automatic or Manual. 2- Have a damn list of change your gonna apply to my browser i don't really feel safe to apply a patch when I have totaly no idea of the impact and more... That I don't have any idea after the patch of what I just did!!! To resume: let us decide wich way we want to set the updates and please provide us with a list of modification!
July 19, 2009 7:21 AM
Scandalon said...
Yea, you people seriously need to lay off the caffeine/amphetamines for a bit.
The whole point of this announcement is that it is now using the default, built-in system scheduling mechanism, (Scheduled Tasks/Task Scheduler in Windows, some version of cron on OSX... as all background-updating apps should do.) If you don't want it to run ever (dumb idea) then delete the task. Don't want it to run when on expensive mobile link? Disable it and have run it manually. Or only on Tues. when you're in the office or whatever.
Additionally, network admins (well, Active Directory based) can adjust settings via Group Policy now.
Is it perfect? No. Does it do everything I wish it would do exactly how I would do it? Probably not. (I'm still waiting for their update system to update my work order system. Also, I want a pony.) But it's a huge step in the right direction. Quit being such whiny little...well, whatever things are small and whiny and annoying, quit your hyperventilating long enough to let some oxygen to your brain and maybe you can offer some constructive criticism.
P.S. No, I don't work for Google, am not particularly enamored of them as a company, etc.
July 22, 2009 12:14 PM
Antony said...
I want Google Updater to: 1) not need 5 entries in my task scheduler, 2) not need a permanent process running, 3) tell me when updates are available, 4) not download or install updates until I choose.
July 30, 2009 4:22 PM
Jason said...
While I understand that the idea of automatic updates is there to cater to the casual computer user google need to understand that experienced users want complete control. Add a manual option.
Patches should be pre-released in open source with a full specification of changes.
While chrome is an amazing step forwards in browser design, resource handling and scheduling, it is still BETA. The experienced among us DO NOT want to upgrade to a new patch that is potentially unstable for each of our individual systems when we've got something that's running perfectly fine right now.
Listening to what the experienced want while still catering to the inexperienced IS the way forwards.
August 14, 2009 5:06 PM
Casey said...
@West Gone East:
It looks like everyone's ignored your question so far in favor of bickering, which is too bad...
I found this link, which explains the purposes of the various tasks:
http://omaha.googlecode.com/svn/wiki/GoogleUpdateOnAScheduleOverview.html
As for my contribution to the bickering: I agree with the general hostile opposition to a GoogleUpdate task. I support the idea of automatic updates especially for network programs with potential security vulnerabilities. However, I feel this role should belong to the application being updated, and the updates should be consensual and visible, rather than happening invisibly all the time -- it's no wonder to me that offends so many users.
August 21, 2009 3:08 PM
Post a Comment