Cannot auto-update Google Chrome anymore (error: 12) - OS X 10.8.2

"Update server not available (error: 12)"

This is what I get when I check for updates in Chrome - About Google Chrome.

I tried the official solution which did not work: https://support.google.com/chrome/bin/answer.py?hl=en&answer=1367288

I tried everything here which did not work: http://productforums.google.com/forum/#!topic/chrome/t9iK_JcJsuA

I hoped it would be solved by manually updating from 21.x to 22.x but no.

OS X 10.8.2

I know this is an old question, but I have run into this issue over and over again while running various versions of Chrome on OS X 10.9. I too tried the solutions at https://support.google.com/chrome/bin/answer.py?hl=en&answer=1367288 and http://productforums.google.com/forum/#!topic/chrome/t9iK_JcJsuA but never had any luck. I would always resort to downloading and installing the latest from Google. Today, ran into the issue again and decided that there HAD to be a solution.

After the most recent failed update attempt, I turned to the Console. A quick search for "chrome" revealed the following GoogleSoftwareUpdateDaemon error:

2/21/14 5:18:33.570 PM GoogleSoftwareUpdateDaemon[1784]: -[KSInstallAction performAction]
    KSInstallAction install script failure. (productIDs: com.google.Chrome)
    [com.google.UpdateEngine.CoreErrorDomain:2307 - '/tmp/KSInstallAction.6E6RqXqHyw/m/.keystone_install']
    ("dirpatcher.sh: can't patch nonexistent or irregular file /Applications/Google Chrome.app/Contents/Versions/32.0.1700.107/Google Chrome Framework.framework/Resources/am.lproj/locale.pak\n.keystone_install: dirpatcher of versioned directory failed, status 12\n"
    [kKSInstallScriptErrorDomain:12])

A closer inspection of the "nonexistent or irregular file" in the error revealed that it had to do with a localized version of Chrome. While conducting a deeper Google search, I found a similar error message with this comment: "Do you have an application installed that removes localizations from application packages?" It was then that it dawned on me that I had been using CleanMyMac to, among other things, remove "unneeded" localization files from my machine! And, sure enough, it was removing all but the required en.lproj resources from Google Chrome, including the am.lproj folder that the updater was complaining about in the error.

My solution: Download and install the latest version of Google Chrome and either turn off any localization removal settings in cleaner apps you may use or, like I did, add an exception to ignore Chrome during cleaning.

Good luck!

There is extensive discussion about this issue here: http://productforums.google.com/forum/#!topic/chrome/t9iK_JcJsuA

I followed many of these steps, including reinstalling the Google Updater but the issue remained. Finally, based on one of these recommendations, I changed my Chrome settings to "allow 3rd party cookies" to be set. This resolved the issue.

Google Chrome > Settings > Show Advanced Settings > Content Settings Un-check the setting "Block 3rd party cookies and site data", at least long enough to go to "About Google Chrome" and check for updates.

If you are using an application that removes localizations from apps (like CleanMyMac as I was using), this may be the answer.

According to this thread, it's because of the localizations stripping.

Nearly all of the update logs I get are due to https://code.google.com/p/chromium/issues/detail?id=165359#c17. The steps to fix are:

• Disable the application that is installed that strips application packages
• Manually re-install Chrome
• The next update should work; if not, file a bug ( at http://crbug.com )

I have ~40 OSX 10.7.5 clients that had this issue from time to time when going from 20.x to 23.x and 24.x

In terminal:

defaults write com.google.Keystone.Agent checkInterval 1

After re-launching Chrome I am then presented with a button, Set Up Automatic Updates for All Users. Clicking on that and authenticating shows the update process starting but then fails again with another error 12, except it actually is updating. Re-launching after about 5-15 seconds then shows the browser as up to date. I have no idea why the second error 12 reappears but I have seen it on every one of those clients I've updated recently even though the browser actually is updating. Those that remained at version 20.x were only able to update after changing that value in terminal.

If this still does not work, check to make sure you are trying to update the browser with the same account that initially installed Chrome. I have seen cases where the only solution was to completely remove Chrome (Firefox as well) from the system and reinstall.