That particular message deserved all the hate it received, and more.
So short, twee, and devoid of the vocabulary usually found in error messages that it virtually had to have been intentionally added by a human; rather than being an unfortunate corner case of a usually sensible concatenate-the-relevant-stuff error message mechanism; profoundly devoid of information(either provided directly or indirectly provided by being distinctive enough to search; like 0x8024400A); afflicted by a too-precious-by-half attitude(rather like a PR flack couching an event in the lowest-responsibility terms available; it doesn’t even acknowledge that ‘something’ is an error; mention what program ‘something’ happened to; or speculate on why).
And all about a process that, while complex, can be(and is internally) broken down into distinct parts that have verbose, if sometime cryptic, logs: the BITS transfer session to obtain the source files; formatting the target drive; probably some DISM stuff. Plenty of room for actually informative error messages; but nooo.
