Maybe I never experienced it, because if I want to force exact match results I simply place the error message within double quotes. But often you do not need exact match searches to get good results for a random error message. If it happens to you a lot, it should not be a problem to post a single example query that returns useless results.
I do agree that Google is focusing more and more on the common internet user, and not the early tech adopters. This forces us to use tricks like the double quotes, while keeping the search engine user-friendly for the vast majority of ad-clicking internetters.
The behavior you are referring to is called https://en.m.wikipedia.org/wiki/Query_expansion and while this improves the search results for many people with imprecise or misspelled queries, if you trained yourself to search with exact matches, you'll need some time to adapt (or get in the habbit of adding double quotes).
I do agree that Google is focusing more and more on the common internet user, and not the early tech adopters. This forces us to use tricks like the double quotes, while keeping the search engine user-friendly for the vast majority of ad-clicking internetters.
The behavior you are referring to is called https://en.m.wikipedia.org/wiki/Query_expansion and while this improves the search results for many people with imprecise or misspelled queries, if you trained yourself to search with exact matches, you'll need some time to adapt (or get in the habbit of adding double quotes).