Removing com.google.keystone.daemon

WZZZ

here is the last paragraph. It skips your (phantom) question, though it was a good read.

Reiterating your suggestion somewhat,...

The initial inquiry proved that he has a bit of Google stuck in the guts of his machine, and I think the better course would be to 'go back to the drawing board' and examine all log-in / launch / startup items with reference to Google and remove them. It is surprising how many different locations for these there are. I don't think this was dome throughly enough to begin with. I reckon if he does that, he may solve the problem without resorting to surgery.

Some places check. list is not exhaustive.

~/Library/LaunchAgents

HD/Library/LaunchAgents

HD/Library/LaunchDaemons

HD/Library/StartupItems

HD/System/Library/LaunchAgents

HD/System/Library/LaunchDaemons

HD/Library/StartupItems

Message was edited by: roam

Post just the one line from the Console log, showing us the message.

Try this?

http://wireload.net/products/guu-google-update-uninstaller/

You would think ds-store's pointer would had have worked.

Have you searched for "com.google.keystone.daemon" for any reference to it on your computer?

I have not installed Google Chrome, nor had the problem of getting rid of it so what follows is more out of curiosity than troubleshooting… In Terminal, what is the output of the following command. Copy and paste it to avoid errors

kextstat | grep -v apple

This is everything keystone on my system. I only have Chrome (and only as a backup browser) installed in my user and nowhere else, so it's possible you might find it elsewhere, depending on your settings.

/Users/****/Library/Preferences/com.google.Keystone.Agent.plist

/Users/****/Library/Caches/com.google.Keystone.Agent

/Users/****/Library/Caches/com.google.Keystone

/Users/****/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore .lock

/Users/****/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore

Get EasyFind and search.

http://www.devontechnologies.com/products/freeware/

This may be the cause. Concentrate on removing that.

com.google.driver.Gild

I could suggest a command to unload that, but as I have not actually unloaded that driver, I can't confirm the command would work. In other words I can't test it and don't want to put your system at risk if something was mistyped. This driver sits at a fundamental level but that is what I'd be angling to get rid of.

What's in /Library/LaunchDaemons and, same place, LaunchAgents? Also, Accounts>Login Items?

Have you tried EasyFind? Make sure you have show invisible checked and search all files folders. Also check your home folder/Library for LaunchAgents

If you find any in LaunchDaemons or Agents, you can disable them using the following:

sudo launchctl unload -w (space) path to file

or just use sudo launchctl unload -w leave a space and drag in the file.

This can easily be reversed by substituting

sudo launchctl load -w

After hitting return, you will be asked for your admin pword, which you won't see as you type it in, then hit return again.

This won't work for the file roam gave you. There is an easily reversible command for that as well. For that, have a look in /System/Library/Extensions.

com.google.driver.Gild' does ot exist.

It does exist. You have already proved that. But it is not something to be found in Finder. It is a process that is loaded in the kernel.

I said "This driver sits at a fundamental level"

It does not have to be removed, it has to be unloaded. using the correct command in Terminal.

I cannot specify the command because I don't have that driver loaded to test it. If you unload the wrong thing, and there are dozens and dozens of kernel extensions, you can make your system inoperable. This is no time for me to try an experiment on your computer.

edit: deleted extraneous information.

Message was edited by: roam

The only Google related Launch Agent found is: 'com.google.GoogleML.plist.' Could that be the culprit? I'm uncertain what GoogleML really is

You seem to have Google stuff still being loaded after all.