Hi there

I have had this issue all the time, I tried to restore SBS 2003, XP professional and home images which got password onto a duplicate or a differential hardware system. all of them failed to restore MBR. 

I tested it, the outcome was MBR sucessfully restored from the image which got  NO password, but the one with password keep failing, even the backups are exatly the same content.

I tried different restoration options, such as restore MBR from image file or restore original windows XP file. neither of the options will help.

keen to get anwsered, Cheers!

Thanks for reporting this.  We have found and fixed the issue.  I only occurs in the 3.1.0.3 recovery environment.  We will soon release the 3.2 recovery environment with the fix for this particular issue.  In the mean time, users who experience such an issue will generally only have problems caused by this if they are restoring to a blank disk which never had an initialized MBR.  In such a case, you will need to run fixmbr from the Windows Install CD's Recovery Console.  The exception is those users who have MBR hook code (such as FD-ISR and RollBack Rx users). For them, until they received the fix in the form of the 3.2 recovery environment (ETA 3 weeks) they should not encrypt images which they are migrating to different hardware.  For restore to the same machine, they can encrypt images but just select NOT to restore MBR and hidden track (as the MBR and hidden track data is already there, with their MBR hook code in place).

Hi Nate,

Appreciate the feedback. I am also having this happen with ShadowProtect Desktop v3.1. Just to make sure I understand correctly, this is an issue with the 3.1.0.3 recovery environment, not the image. When the 3.2 recovery environment comes out, I should be able to restore MBR and hidden track with my current image (made with 3.1) with no issue.

-Jackson 

That's correct.  Also, this issue *only* occurs if your image is encrypted.  If you restore to the same machine this is not an issue as the MBR and hidden track sector data are already there, so this is only an issue if you are restoring to a new blank uninitialized drive, in which case you can fix this by booting the Recovery Console of the Windows install CD and running the FixMbr tool after you restore your image.

hihi,

just wondering that this has been fixed in 3.2 server edition cd?

i have had 2 encrypted images 'fail' when restoring using when wanting to restore the MBR and HIR.

i re-ran them without restoring the MBR - only HIR and they restoreed as expected. i was prepared to fixmbr and fixboot from win2003 rescue prompt after i had imaged them so was not a big deal.

love the software :)

- Tom