After all, speed is important, but reliability and bs-free in both backup and restore are more so.

Considering this potential pitfall for whole disk restore, I will ditch Acronis, and do my duplicate OS backups with IFL and Macrium Reflect. Neither Macrium Reflect nor IFW/IFL has that option, while they restore perfectly fine without confusing users with that stupid 'restore MRB and track 0' option.įortunately I have a disk image made by IFL, which saved my ass this time. I am very curious why Acronis still keep that option (Restore MBR and Track 0), no matter the type of your OS/system (MBR vs UEFI Secure boot). But since this was no longer considered a 'Whole disk restore', I had to manually confirm the correct location for each GPT partitions to restore.

I then tried to restore again, with the 'Restore MBR and track 0' manually unselected. the restore resulted in a non bootable OS, not surprisingly, since my OS is a UEFI with secure boot system. Since I don't do OS image restore often these days, I accidentally ticked the 'restore whole disk' option, which automatically selected 'restore MBR and first track 0'. However, a test restore of the whole disk turned out to be a disaster. The backup went well, as always: quick, efficient with small disk image size. Tested the new Acronis True Image 2017 backup and restore for my Windows 10 LTSB Enterprise install on an SSD drive, using the whole disk backup/restore options.

Acronis restore from backup