This is spot on. Sometimes it's much quicker to just plug the error into Google than to search. Saves a lot of time and work.

I live in France, and I hate localized linux distributions, you can't google error messages when it's localized. I sometimes try to re-translate the message in English and google it.

Error messages are not messages for the users to diagnose anymore, they are keywords for google, give them a number. I google and if it fails, I'll try to use my brain.

Sounds like a good reason to use error codes (non-localized) alongside error messages (localized). E.g. "404: page not found".

Perhaps we need error messages that include a Google link for searching that error.

there is an ironic situation: in Google Chrome, when you get an error (like a rejected certificate, or something a bit browsery), they give you a link to a completely unhelpful "help" page about the chrome browser, instead of a google search "thatsite.com <certificate rejected error>".

Microsoft has started to include QR codes in the bluescreens of death.

Google is a DSL for troubleshooting.