Thanks jphughan but I already tried that.
If it DOES find something wrong, you'll need to do "chkdsk c: /f", which will require a reboot since you can't fix the OS volume while the OS is running. As long as it doesn't find anything wrong, it should mark the disk as clean and not require that next time you restart. If it helps though, you can try skipping it at boot and then manually running "chkdsk c:" within Windows afterward. I know it's aggravating, but this issue was definitely created by Microsoft, not Macrium, and since as I mentioned above I've triggered this simply by booting into Microsoft's own Windows Rescue Tools environment and running read-only diskpart commands, I kind of doubt that Macrium would be able to sidestep this after something as "disruptive" as restoring an entire image backup. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 10:18:31 AM Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: DESKTOP-5NG2HMG Description: The system has rebooted without cleanly shutting down first.
0 kommentar(er)
