In my original dissection of Google Chrome's setup I noted that the Google Updater was left running after I uninstalled. After a pretty smooth installation experience, that partial uninstall left a bad impression on me. Well, it turns out that my observation was only half correct. A comment was left on my blog and a friend of mine at Google noted that the Updater is left behind but does remove itself a number of hours after the uninstall of Chrome.
I missed this fact because after uninstalling Chrome and noting that the Google Updater was still running I immediately went about removing it manually. After hearing that I just had to wait, I again installed then uninstalled Chrome and waited. About eight hours after my uinstall the Updater unregistered itself and shutdown. In the end, I was just left with some user data (good) and a couple directories in the LocalAppDataFolder\Google directory (less than ideal but no big deal).
So Google Chrome does get cleaned up and that makes me feel much better about the install (I've posted an update to my original blog post).
Now I'm just puzzling over the decision to not uninstall Google Updater right away. I can't come up with a good reason for the Google developers to risk upsetting geeks (like me). Geeks are the most likely to adopt the new browser in the first place. But geeks are the most likely to notice the "bad uninstall". And geeks are also the most likely to get upset by junk left over after uninstall.
Anyone out there want to random a guess why Google chose to have the Updater uninstall behave this way?
RobMensching.com LLC
8 Comments
Comment by Martino Sabia on Saturday, September 13, 2008 5:14 PM
The "evil" guess: Google wants to know that you've uninstalled Chrome and... what browser you're using after Chrome... [bad thinking]
Comment by Anthony Wieser on Sunday, September 14, 2008 10:13 PM
Comment by Christopher painter on Tuesday, September 16, 2008 7:33 AM
http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=networking_and_internet&articleId=325539&taxonomyId=16&intsrc=kc_feat
Comment by Joe on Thursday, September 18, 2008 1:48 PM
Comment by AlienRnacher on Friday, September 19, 2008 6:07 PM
Comment by Ilgaz on Saturday, November 08, 2008 11:20 AM
I am not sure if they fixed it or not, here is the bit by bit explanation of their "Google Desktop" installation.
http://daringfireball.net/2007/04/google_desktop_installer
Especially the part about installing anything to /System is plain amazing. That folder should be touched only by Kernel extensions (Drivers), nothing else. Even Apple themselves doesn't mess around with that folder except Core OS updates or driver updates.
While speaking about it, I think they should do what Apple does in "Software Update" for Windows. It uses the Windows built in "Scheduler" mechanism to fire up in regular intervals. There is no need to keep running or poll every 3 sec (!). Just be nice to the OS you work on and use its built in features.
The interesting thing is their "re inventing wheel". On OS X, there is .pkg and on Windows, there is .msi for such complex installations. No need to invent things while system provides open access to them.
Comment by Andrea on Wednesday, April 20, 2011 2:12 AM
Comment by Marathasita on Tuesday, August 23, 2011 8:21 AM