But with a happy ending.
I had made a couple of changes this week to my PC (Win 8.1 Pro). I decided to roll back to my latest image created by MR – last Sunday’s. Having remembered how to get to the images using WinPE, I restored that day’s image. So far so good.
But it failed at 3% saying the image was corrupt. I then rebooted into Windows and lo and behold, it couldn’t. It did a diagnostic and repair. Only it wasn’t successful. No matter I thought, I’ll restore from an image from the previous week. That got to 5%, but now when booting into windows I got a screen telling me (in the end) to contact my system admin (me!) or the PC manufacturer. Nothing worked other than just shutting the PC down. I then tried Linux (Ubuntu on a memory stick I have – it couldn’t even see the c drive – saying there was a problem.
So it looked like the image restore failing had screwed the disk and it was hosed (a quaint Americanism?). I tried a couple of more images and finally the one from the 27th October worked. Phew! It took just over an hour, and another hour updating Windows and other programs (good thing I keep stuff in the downloads folder).
Lessons to learn. Verify the image after you create it. And before you use it to restore.
I would say that my decision a few months ago to separate OS and data also helped greatly as the time to restore was so much less than it might have been. And also I didn’t have to download anything I had added since the 27th Oct.
So, has anyone any ideas what caused the corruption? I think it was error 5 that was quoted.
Eliminate spare time: start programming PowerShell