ATIH2010 - "Unexpected Shutdown" window after restoring an old image !!!
So, i was doing a system backup with validation, when the computer locked up with a BSOD during validation process (so the image was completed). Then, i´ve decided to restore to a previous backup made some days ago (not the last). After the restoration and logon, windows shows this message: "Windows has Recovered from an Unexpected Shutdown". I´ve never get this message before, so i decide to figure out what´s wrong. Here in this forum there is a topic almost identical to my problem (http://forum.acronis.com/forum/6083) except that my dmp file doesn´t show any file associated with the problem. I´ve tried older images with the same behavior, but here goes something very strange: just after the boot up and the message, i´ve create a new incremental backup of the partition, and tried a restoration. After the restoration, no windows message about unexpected shutdown. So, how can it be? An older image doesn´t work but a new (not a full backup but a incremental) after the accident yes. It´s look like the BSOD get was record some where and the recovery process doesn´t delete this information. So, can anyone help me? Any advise?
I´m using Windows 7 Ultimate 64bits and ATIH2010 7046.
Thanks for helping

- Accedi per poter commentare

Colin B wrote:What seems likely to have happened is that the disk image contains this marker. It should be reset once you've successfully booted into W7 and then Shutdown via windows shutdown command successfully.
I'm trying to understand, but the problem is weird. The image i'm trying to recovery were made 08/25/2010. The BSOD i've got happend in 08/30/2010. If i made a partition recovery, i imagine that every thing in this partition is replaced by the image. So, how can this marker survive?
So i've made some tests here without success. I've try other boots cd (2010b7046,2010b5055,2011b5105) and try to format the drive before recover, with all getting the message. So, the only reasonable explanation is that the created image have this marker, but how this marker appears there? And why the new image works as supposed to be?
- Accedi per poter commentare

Is this a complete disk image you have restored or a single partition?
If a partition which one?
If a complete disk does it contain the 100MB system partition that might be part of your W7 setup. Note not all W7 installtions will have this 100MB partition, only those set up on drives formatted by W7.
- Accedi per poter commentare

First, thanks for helping me. So here go the answers...
A single partition, the boot and system partition (C:)
I don't have this 100MB hidden partition, as i partition the drive with other software (not windows installer)
The other partition (D:) has my data and some games installed.
The second HD (E:) has the backup images only.
- Accedi per poter commentare

Open a Windows command prompt with Admin permissions.
Type in the following fsutil dirty query c:
See what the response is.
Then, mount the image that you restored and this time run the above query, substituting the partition letter of the mounted image for that of C: above.
- Accedi per poter commentare

Ok..............
I've done what you suggested: all drives and the mounted image show "is not dirty" !
- Accedi per poter commentare

Alex:
I don't know exactly where Windows stores the OS state (running vs. shut down) but it's in a file somewhere. If you create your image using the Windows version of TI while Windows is running, the OS state is "running". When you restore this image and reboot, Windows is expecting the state to be "shut down" at boot time, so it flags the inconsistency as an error. It is the same error that you'd get if the power fails while Windows is running and then you reboot. Windows will detect that there must have been a power failure since it sees the stored state as "running" when it was expecting to see "shut down".
One way to avoid this error is to create the image from a boot CD while Windows is shut down. The stored OS state in an image created this way is "shut down" and there will not be any inconsistency when you boot into the restored image.
- Accedi per poter commentare

I can agree with you if i always get the error. But, the last image, made while Windows running, boots up without the message. That is the weird part.
This post http://forum.acronis.com/forum/6083 shows the same problem as i, and a different boot cd resolve the problem (maybe cleaning something inside windows just after the restoration). But, for a time (since 01/2010) i was using TIH2010 without this problem, and for some unknown reason the message appears from nothing.
- Accedi per poter commentare

Alex:
I can't explain why you do not get the error sometimes unless TI 2010 attempts to "fix" the state (running vs. shut down) after image restoration. Perhaps they do but older versions of TI always produce the error on the first reboot into a restored image that was created while Windows (Vista or Win 7) was running.
There is also this post from Acronis: http://forum.acronis.com/forum/8299
- Accedi per poter commentare