But then, there’s also that class of things that fail in exciting and unexpected ways: a bit randomly flipping in memory, a cable detached in an untimely moment, a missing system library that was there when the program started… you cannot enumerate all things that may fail unexpectedly, hence the only viable solution is to have a special case for those - „Unexpected error“ doesn’t sound wrong from that perspective.
Still, it’s completely useless to the human in front of the machine, so there’s that.
The useless error messages are still my number one reason to avoid anything from Microsoft.
There is no information on how long this will last, there is nothing I can do to fix this, and of course, there is no customer support available. I can't even confirm that waiting will actually fix this, as there is no error code. I thought the people at Google would know better.
“Unexpected error” basically means “I called a function that threw an exception, but didn’t have code in place to catch it, so it hit some toplevel global exception handler that just aborts the whole thing.”
Another thing is people are trained to ignore the content of error messages, probably because usually they're totally useless or meaningless. I used to teach computers at school and kids would demonstrate the problem they're having but when the error message popped up, they're reflexively close it. I'd have to get them to start again so we can read the message. Error messages really are stupid. If you try to copy photos from an Iphone to a Windows, it can fail with either "A device attached to the system is not functioning.", "The device is unreachable.", "Can't read from the source file or disk", or "The requested value cannot be determined.". What the hell is the difference between them? What does the last one even mean?