Comment by purpleflashing

Because modern tech and modern tech support has a terrible UX in general built by engineers around their engineering heuristics.

By the time a non-tech user reaches the point of seeing an error they are cognitively overloaded and since the errors are pretty much incomprehensible to the users, the user doesn’t get the feeling of it being anything that’s tied to their actions. It’s just anxiety-inducing noise, it never registers as something that has a meaning, so even copying and pasting an error feels like a meaningless step that their overloaded and already anxious brains skip.

If errors are meant to be shared with tech support, the UX should reflect that (and some interfaces do that where you just have a button to send the crash report or smth). If errors are meant to give users agency to solve the problem on their own, the UX should reflect that too.