Correct, I won't defend all of that, some of these messages were irritatingly vague, and it doesn't tell you how to find the log. Though in fairness, I believe

Correct, I won't defend all of that, some of these messages were irritatingly vague, and it doesn't tell you how to find the log. Though in fairness, I believe though the most common cause for an error in that path would be a problem with the installation media, and probably more likely to be checksum errors on an optical drive, or perhaps corruption on the machine capturing the WIM file, or even a bad drive on the target machine -- all of these are much more likely that than someone stuffing a Linux image onto installation media.. So I could see a message geared towards that. When I was responsible for the WIM code, I got pinged with a lot of noise from people all over Microsoft installing Windows onto bad disks. They usually thought they hit setup bugs.