Same with error messages - they often have timestamps, or local object IDs/memory addresses, which you also want to be fuzzy-matched.
I think the issue is the de-emphasis of "power" modifiers for google - it's less obvious how to say "This part of the string needs exact match, this can be fuzzy"
https://www.google.com/search?q=%22kgirbudidndijrjjr%22 gives me "Your search - "kgirbudidndijrjjr" - did not match any documents.", at least it will until they index this comment and find kgirbudidndijrjjr
Agree with the peer - specificity matters. Model numbers are a good example. I feel like I've developed a weak form of dyslexia because I can't trust Google like I once did.
Things I want fuzzy searches for... will be presented fuzzy. Not as an opaque string of usually-quoted characters, but wrapped in keywords
A reply makes a good point - double quotes don't seem as effective any more.