...
Unfortunately we have just become aware that since release v7.1.3147 on 17th April 2018 it was possible that Macrium Reflect could create corrupt and irreparable Incremental or Differential Image files. The problem occurs if the Macrium Changed Block Tracker (CBT) driver participates in the backup. By default, the CBT driver will participate in the second and subsequent Incremental Image of a backup set after a Windows *full system reboot. For Differential Images, CBT will participate if the Full Image, in the same backup set, was created in the same Windows session, i.e, no Windows restarts *full system reboots between the Full & Diff (see Fast Start-Up note below). If an image is affected then it is unlikely that it can be mounted and browsed successfully and restore will result in a corrupt file system.
| Info | |||||
|---|---|---|---|---|---|
*Note: Windows 10 includes a default option called 'Fast Start-up'. If this is enabled then CBT may persist over a Windows normal Shutdown or Restart.
|
Technically, the problem arose from a misaligned data structure in the code and our testing prior to release didn't trigger this error. We have since introduced more stringent tests that will prevent this type of error from occurring in the future.
...
*Differential images will only use CBT if the image being appended to, the Full image, was created in the same Windows session.
i.e, there have been no Windows restarts since full system reboots since the Full image was created. Most Differential images will not be affected. (see Fast Start-Up note above).
The words 'CBT init Success' and 'Searching for NTFS meta data' will be seen in the Image log:
...