"I am not sure I would class the change as an improvement. I mean, the old message ("Windows cannot start because the following file is missing or corrupt: \WINDOWS\System32") is one I understand since I know what the destructive operation was. But if I did not have that knowledge then I would not know much about what was going on.
The new message, though, is even harder to understand (though an internet search of 0xc000000f will see it relates to Windows File Protection, which I guess is a hint."
|