Troubleshooting

Macrium Reflect Error Guide

Common clone and backup errors, what they actually mean, and what to try. We only cover errors we could verify against real reports — for anything not listed here, Macrium's own forum is the most reliable source.

Error 0 — "Unable to match partition"

Usually caused by a partition-table mismatch between source and destination (one is MBR, the other GPT), or by the destination disk already having partitions on it that conflict with the clone. Try: converting the destination to match the source's partition style, or deleting all partitions on the destination disk before cloning so Macrium Reflect can create fresh ones. Also worth checking: disable Secure Boot and Fast Startup temporarily, and confirm cable connections if using external enclosures.

Error 8 — Clone/backup failed

Most commonly means there isn't enough free space on the destination disk to hold the source's used data. Check the actual used space on the source (not its total capacity) against the destination's capacity — you may need a larger destination drive, or need to shrink the source data first.

Error 9 (and "Code 9") — Clone/backup failed

Typically points to bad sectors, a loose or failing cable connection, or antivirus software interfering with disk access mid-operation. Try temporarily disabling real-time antivirus protection, reseating/replacing cables, and running chkdsk /r on the source drive. If bad sectors are confirmed and few in number, Macrium Reflect's "Ignore bad sectors" option lets the operation continue past them.

Error / Read Failed 23, Error 433 — read failures during backup

These point to bad sectors on the source disk being read during imaging — a real hardware reliability signal, not a software bug. Run chkdsk /r repeatedly until it comes back clean, try switching from Intelligent Sector Copy to Forensic Copy mode (forces through problem sectors), and enable "Ignore bad sectors" to let the image complete despite them. Repeated read failures on the same drive are a sign the disk itself may be failing — back up what you can and plan to replace it.

"GPT format is not supported" (Rescue Media Builder)

Macrium's Rescue Media Builder can't write bootable rescue media to a GPT-formatted USB drive — it needs an MBR-formatted one. Reformat the USB drive as MBR (this erases it) before building rescue media, or use a different USB stick specifically for this purpose.

"The destination path is included in the image"

This means your backup destination is accidentally selected as part of the source you're backing up — for example, a checkbox next to the destination partition got checked along with the source disk. Carefully review every checkbox in the source-selection screen (including on disks you didn't mean to touch) and uncheck anything that matches your destination.

Not detecting / not seeing an SSD or NVMe drive

Usually a driver or BIOS storage-mode issue rather than a Macrium bug. In Windows, update chipset/NVMe drivers from your motherboard or SSD manufacturer. In the bootable rescue media environment specifically, the built-in driver set may not include your NVMe controller — you may need to rebuild rescue media with the correct drivers injected, or check your BIOS storage mode (AHCI vs RAID) if the drive doesn't show up even in Windows.

Don't see your error code here?

We'd rather point you to a real source than guess. Macrium runs its own official support forum where staff and experienced users troubleshoot specific error codes and messages — search your exact error text there, or check Macrium's knowledge base directly.

FAQ

Common Questions

Sources

Written by

Last updated: July 30, 2026

MacriumReflects Editorial Team

MacriumReflects is an independent site that researches and writes guides on backup, disk imaging, and disk cloning software, including Macrium Reflect and its alternatives. We are not affiliated with Macrium Software Ltd.

Need More Help?

Check our full support and guides section, or reach out with feedback.