MS is so bad with error messages these days. "Oops something went wrong" and a "funny" picture of a dropped ice cream cone. Just tell me what is actually happening.
I find those cutesy error messages just make a bad situation worse.
Error descriptions are probably too much to ask these days - I would bet they'd be perceived as intimidating by the UX group, given that the same group seems to prefer a level of discourse appropriate for grade-school classrooms.
A error code would be wonderful, though, since it would be a nice unique search term. It could be put in small greyed-out text in a bottom corner, too, to make everyone happy.
One thing that keeps surprising me, even though it shouldn't by now, is how reluctant people are to learn from experience.
Rust's community got huge benefits out of work to improve the error messages from its compiler and tooling, but we didn't see a lot of real effort to mimic that even in other programming languages, let alone the wider tool ecosystem. A few people, here and there, put in some effort, but nothing at scale.
For Rust this work was imperative because their slogan is "A language empowering everyone to build reliable and efficient software" not "A language with terrible error messages that only nerds can handle" so I'm not surprised other people weren't doing this before Rust showed how much difference it makes, but I was surprised they didn't learn from that.
