How To Repair Macrium Reflect Image File

3rd May 2022 - Macrium Reflect Release v7.1.3196

Unfortunately nosotros have just become enlightened that since release v7.i.3147 on 17th April 2022 information technology was possible that Macrium Reflect could create decadent and irreparable Incremental or Differential Image files. The trouble occurs if the Macrium Changed Block Tracker (CBT) commuter participates in the backup. By default, the CBT driver volition participate in the second and subsequent Incremental Image of a backup set later a Windows*full system reboot. For Differential Images, CBT will participate if the Total Image, in the same fill-in prepare, was created in the same Windows session, i.east, no Windows *full organization rebootsbetwixt the Total & Diff (see Fast Start-Upwardly notation below). If an epitome is affected so it is unlikely that information technology can be mounted and browsed successfully and restore will consequence in a corrupt file system.

*Note: Windows 10 includes a default option called 'Fast Commencement-upwardly'. If this is enabled then CBT may persist over a Windows normal Shutdown or Restart.

Show the Windows 10 Fast Start-up configuration...

Technically, the problem arose from a misaligned data structure in the lawmaking and our testing prior to release didn't trigger this error. We have since introduced more stringent tests that will forestall this type of error from occurring in the future.

Please be bodacious that integrity of your backups is our pinnacle priority. We sincerely and unreservedly apologise for this problem and have worked hard to repair this issue in the latest release.

What Images are affected?

The Post-obit Installations and Backups are Not Affected

Site Manager

Macrium Site Managing director clients are not affected. The amanuensis install for Site Manager did non receive the problematic updates. If you are running standalone Macrium Reflect installs with Site Manager and so delight bank check each install.

File and Folder

File and Binder backups are not affected.

Macrium Reflect Complimentary Edition

Images created by Macrium Reverberate Free Edition are not afflicted as Macrium Reflect Free Edition does not include the CBT driver.

Images that may be affected include Incremental and *Differential Images that utilize the CBT driver to participate in the fill-in.

*Differential images will simply use CBT if the image being appended to, the Full image, was created in the same Windows session.
i.e, there take been no Windows total system reboots since the Full image was created. (see Fast Start-Upward annotation in a higher place).

The words 'CBT init Success' and 'Searching for NTFS meta data' volition be seen in the Image log:

The build number of Macrium Reflect will also be shown in the footer of the log.

The affected build numbers are: v7.1.3147, v7.i.3159 & v7.one.3169. No other build numbers are afflicted.

If yous have whatsoever doubt, then you can mountain the epitome file and run chkdsk from and elevated command prompt. Use the mounted drive letter as the chkdsk target equally shown beneath:

The above example shows typical abuse of the NTFS file system.

If you come across errors and then ostend by running chkdsk on the source file organization

Information technology's possible that not-critical file organisation errors have been carried over from the source file system. In this case your image is fine

Note: Information technology's possible for proficient images to report minor and innocuous errors when using 'chkdsk'. These errors will have been transferred from the live file organisation but don't cause a problem with the image. If you see only the post-obit mistake then there is no problem:

CHKDSK discovered costless infinite marked every bit allocated in the volume bitmap.

This is cypher to worry about.

Note: Corrupt Image files will verify successfully using the Macrium Reflect verification role. The nature of this error is that key information was omitted from the epitome, the information that was backed upwards is not itself corrupt..

Note: The backup set chain is not cleaved. This ways that non CBT Incrementals and Differentials created after decadent files will exist OK to browse and restore.

What do I do with my corrupt Images?

These image files should not be restored and may exist deleted by using the Delete functionality in Reverberate. Deleting Incremental Images will too delete dependant Images created after the decadent file and this may not be desirable.

Later updating to v7.1.3196 or later on, leaving the corrupt images in the fill-in fix volition not affect the integrity of afterward Incremental or Differential images in the aforementioned backup set whether using CBT or non.

Notation: The side by side Incremental or Differential in the aforementioned backup set up created with v7.1.3196 or later will non be affected. So, if y'all are running an Incrementals Forever backup strategy you can continue and whatsoever corrupt Incrementals will eventually be consolidated successfully into the Full without whatsoever further loss of data.