no way to turn off update engine if one does not want it

[GoogleCodeExporter]

What steps will reproduce the problem?
1.download google earth 
2. install
3. run

What is the expected output? What do you see instead?
I see a screen telling me about update.  The ONLY choice is ACCEPT.
Not to accept it requires a force quit

What version of the product are you using? On what operating system?
5.0.11733.9347     <- what's up with a version number like that!?

Please provide any additional information below.

Original issue reported on code.google.com by Dr.J.W.Dreher@gmail.com on 26 Mar 2010 at 10:14

[GoogleCodeExporter]

Google earth layers no longer work (unclickable) since update engine installed 
itself. I cannot use an older and 
better functioning version without being forced to update to a useless Google 
earth.
A pathetic and unfriendly move on Google's part. Mac OSX 10.6.3.

Original comment by r...@interlog.com on 6 May 2010 at 4:57

Attachments:

• [Screen shot 2010-05-06 at 12.56.07 AM.png](https://storage.googleapis.com/google-code-attachments/update-engine/issue-22/comment-1/Screen shot 2010-05-06 at 12.56.07 AM.png)

[GoogleCodeExporter]

I agree. This is very bad practice by Google. The thing runs even when the 
software is not. Google's supposed to 
be smarter than this (and less evil).

Original comment by fonnesb...@gmail.com on 12 May 2010 at 2:47

[GoogleCodeExporter]

The "evil seed" was planted by the upgrade tool methinks. On my other Macbook 
left untouched by this curse all 
items in layers work. 

Original comment by r...@interlog.com on 12 May 2010 at 2:55

[GoogleCodeExporter]

I also think the mandatory updater being forced on folks is a big mistake for 
Google. Who do you think you are, 
Adobe?

I won't install Google Earth on this computer after all.

Original comment by withab...@gmail.com on 14 May 2010 at 4:08

[GoogleCodeExporter]

i found a way to uninstall the daemon but i'd like an option to enable or 
disable software update whenever I want

Original comment by pandolfo...@gmail.com on 20 May 2010 at 2:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The daemon is just a LaunchDaemon or LaunchAgent, depending on how it is being 
run.  See "http://developer.apple.com/mac/library/technotes/tn2005/tn2083.html" 
(Technical Note TN2083: Daemons and Agents) and 
"http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/
man1/launchctl.1.html" (man(1) launchctl).  In general:

1. check /Library/LaunchDaemons/ and /Library/LaunchAgents/ for agents starting 
with 
   com.google.keystone
2. stop them with:
     $ sudo launchctl stop com.google.keystone.[agent | daemon | daemon4]
or
   unload them (remove them from launchctl entirely) with:
     $ sudo launchctl unload /Library/[LaunchDaemons | LaunchAgents]/com.google.keystone.[agent | daemon | daemon4].plist
(That is, when you unload you need the full path to the .plist file.)

With the current installation you can check for updates manually through:

$ 
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resou
rces/CheckForUpdatesNow.command

but I have not confirmed whether that will update the products.  If you have 
dragged all the Google products to the Trash (Google Chrome, Google Earth, 
etc.), running CheckForUpdatesNow.command will automatically uninstall the 
Google Updater (Keystone) for you.

Cheers,
Pete

Original comment by peter.ta...@gmail.com on 22 Jun 2010 at 3:50

[GoogleCodeExporter]

I'm launching Google Earth 5.2.1.1329 and got this retarded message about 
Google Software Update being a mandatory install option.  Automatic update 
notification should be a user preference, not a required, perpetually running 
background process.

I guess I'm not going to use Google Earth after all.

Google, you're out of line.

Original comment by therealh...@gmail.com on 28 Jul 2010 at 8:22

[GoogleCodeExporter]

Agreed.  This is completely unreasonable.  Use the running application's 
context to check for updates at start and periodically.  In applications that 
don't have to contact Google already to work (like Earth), check for updates 
only with permission from the user.

Original comment by thomas.s...@gmail.com on 4 Sep 2010 at 9:12

[GoogleCodeExporter]

I agree. 

Original comment by josephkn...@gmail.com on 17 Sep 2010 at 5:33

[GoogleCodeExporter]

yep, I won't be installing it either. 

Original comment by jsabr...@gmail.com on 10 Nov 2010 at 5:33

[GoogleCodeExporter]

Me either. Nasty stuff.

Original comment by geoff.la...@gmail.com on 2 Dec 2010 at 9:42

[GoogleCodeExporter]

Me too, I wanted to try Google Earth 6, but I won't try it anymore. I do not 
want their Update Engine always running on my machine. It's totally no sense.

Original comment by franat.r...@gmail.com on 3 Dec 2010 at 12:30

[GoogleCodeExporter]

I had an interesting chat with some people - the lack of controls and the 
inability to cleanly uninstall this Update Engine has actually led to a 
corporate wide ban of Google Earth in some companies, with the observation that 
if they found any more Google products installing it they would be banned too 
(I think it's also part of Chrome).

There are a number of reasons which make this the only sane move for any 
company.  First of all, corporates control their desktops, so they want to know 
what changes and why, and need control over when that happens so they can 
ensure a rollback is available.  Secondly, there are questions why an always 
active agent has to sit in the background instead of a shared module called on 
program launch.  Thirdly, security people are especially wary of the virus-like 
appearance an unclean uninstall suggests.

Could I suggest that Google development (a) bumps thus upwards as a priority 
issue, (b) publishes a decent uninstall guide for all the platforms and (c) 
starts to think a bit more ahead?  It's not just corporates that don't like 
excessive baggage - the more sophisticated end user won't touch this either if 
it has all the appearances of another Sony root kit.

I have already seen that an uninstall of Google Earth on Mac leaves the engine 
silently in place.  For now, the mix of Win XP, 7 and OSX Lion desktops in a 
number of companies I know are barred from installing any Google product.  
That's thousands of seats lost by not following very common software practice.

Original comment by peter.ho...@gmail.com on 11 Jan 2012 at 4:45

[GoogleCodeExporter]

I too would like this option.

Original comment by n.brunberg on 27 Jan 2012 at 3:43

[GoogleCodeExporter]

March 2nd, 2012 I too am trying to KILL this 'com.google.keystone.daemon';
I have removed ALL Google paying ADs from my website, Chrome,  Google Earth, 
Google+,
ALL Google Search Engines on ALL browsers, next will be my Google mail.

I am FED UP with this running every 10 seconds on my OSX Snow Leopard mini.

Original comment by cbchoi...@gmail.com on 3 Mar 2012 at 8:02

[GoogleCodeExporter]

Cannot afford to have background internet access going on since my network has 
sensitive information about others on some nodes, normally turned off when 
'playing' with non-essential programmes. Please make Update Engine an option: 
even Adobe allow this choice!

Original comment by freshwat...@gmail.com on 17 Feb 2014 at 6:09

[GoogleCodeExporter]

Same issue. I am running Mac OS X 10.6. Google Earth automatically updates to 
version 7.x, which is useless on my operating system. I found a download of 
Google Earth 6.x, and installed it, after uninstalling 7.x.  But every few days 
Google Earth automatically updates to the useless 7.x.  I keep the download of 
6.x permanently on my desktop  (in case it ever becomes unavailable), and I 
have to re-install it each time that the automatic update occur (and of course 
each time I have to accept the non-optional automatic update program). It's a 
gigantic pain in the butt (excuse my French), and apparently Google has not 
bothered to resolve the issue in the past 4.5 years that this issue has been 
under discussion.  

Original comment by harwood...@gmail.com on 30 Aug 2014 at 6:29

[GoogleCodeExporter]

There is a way to turn off the update engine. I have it somewhere and will
try to get it to you.

Original comment by gigli....@gmail.com on 30 Aug 2014 at 8:26