Hyper-V Error messages without copy message and without an Error ID - it's a shame
M$ is really doing it's best to make the work with their products as hard as possible. This is example 291:
If Hyper-V is not able to start a VM, then we get a lot of GUIDs.
Of course, M$ no longer offers a professional path to the solution:
a) M$ no longer displays a unique Error ID. So we have to google for Text and try to find the best matching solution.
b) M$ does not allow to past the Error Message to the Clipboard, so we have to find a useful workaround to get the details.
It's really a shame that we have to create this kind of uservoice - we talk about the most basic usability and administration subjects.
Of course, today, it's even worse: paying customers have to vote that this kind of illness gets fixed.
Yes, it's a shame.