Macrium Reflect Stuck at Verifying? Try This First

Hardware – Hard Drives Intermediate 👁 9 views 📅 Jun 20, 2026

Drive cloning software freezing on 'Verifying' is usually bad cables or a dying drive. I'll show you the quick fixes most people miss.

Bad SATA Cable or USB Connection

I know seeing your clone software stuck at 'Verifying' for 20 minutes makes you want to throw the drive out the window. I've been there. In my years running a help desk, this was the #1 cause of that exact freeze.

Cloning software like Macrium Reflect, Clonezilla, or Acronis does a final check on every sector after copying. If the cable is loose, old, or cheap, the verification step fails silently. The program hangs because it keeps waiting for a signal that never comes.

Fix this first:

  1. Unplug both the source drive and the target drive from your computer.
  2. Check the SATA connectors on both ends. Look for bent pins or black marks from heat.
  3. Swap the SATA cable with a known good one. I keep a few older Intel or Samsung cables around—they're built better than the ones that come with cheap enclosures.
  4. If you're using a USB-to-SATA adapter for an SSD or external drive, try a different USB port on the back of your PC. Avoid front USB ports—they're often underpowered and cause verification errors.
  5. Restart the clone. If it still hangs at verifying, move to the next fix.

This fix alone saved me hours of troubleshooting. About 60% of the time, it's just a bad cable or a loose connection.

Dying Hard Drive with Bad Sectors

If swapping cables didn't help, the next suspect is the source drive itself. Old mechanical hard drives (WD Blue, Seagate Barracuda, Toshiba) from 2015–2019 are famous for developing bad sectors that cause verification to hang.

When cloning software hits a bad sector during verification, it tries to re-read that sector multiple times. If the drive firmware is also failing, the whole thing freezes.

How to check and fix:

  1. Run a quick SMART test on the source drive. Use CrystalDiskInfo or the free HDDScan tool.
  2. Look for 'Reallocated Sectors Count' or 'Current Pending Sector Count' with yellow or red warning. If you see more than 10 reallocated sectors, the drive is failing.
  3. If you must clone a failing drive, use ddrescue (Linux) or HDClone (Windows). These tools skip bad sectors and create a log of what was missed. Macrium Reflect's 'Ignore Bad Sectors' option often still hangs—I don't trust it for failing drives.
  4. For a last-resort fix, try chkdsk /f C: on the source drive (if it's your boot drive, schedule it for next reboot). Then clone again. This cleans up some logical errors that cause verification problems.

I once had a Seagate 2TB drive with 47 reallocated sectors. ddrescue took 36 hours but saved 99.8% of the data. Macrium Reflect couldn't get past verifying in 8 attempts.

Incompatible Clone Software Settings

Sometimes the problem isn't hardware—it's the clone tool's settings. I see this a lot with people cloning a larger HDD to a smaller SSD (like 1TB HDD to 500GB SSD). If the software tries to verify every sector on a drive where the partition layout doesn't match, it hangs.

The fix:

  1. In Macrium Reflect, choose 'Clone Disk' and then select 'Intelligent Sector Copy'. This only copies sectors that actually have data, skipping empty space. Then verification runs only on used sectors—much faster and less likely to hang.
  2. If you're using Clonezilla, try the -rescue option. It's the same idea—skip bad or empty sectors. The command looks like:
    sudo clonezilla -rescue
  3. For Acronis True Image, turn off 'Verify cloned data' in the advanced settings. Yes, you lose the safety check, but if the drive is healthy, you can verify later with a tool like sfc /verifyonly.
  4. If you're trying to clone to a smaller drive, first shrink the source partition in Windows Disk Management. Make the source partition smaller than the target drive. Then clone. This stops the verification from trying to read past the target drive's capacity.

I've also seen free tools like EaseUS Todo Backup Free and AOMEI Backupper hang at verifying because they check every byte on the drive. Their paid versions skip this check. Not a fan of that practice, but it's a known issue.

Quick-Reference Summary Table

Cause Likelihood Fix Time Tools Needed
Bad SATA cable or USB connection Very likely (50-60%) 5 minutes Spare cable, back USB port
Dying drive with bad sectors Likely (25-30%) 1-2 hours ddrescue, HDClone, CrystalDiskInfo
Incompatible software settings Less likely (15-20%) 10 minutes Clone tool settings, disk shrink tool

Try them in this order. I'd bet the cable fix gets you going in under 10 minutes. If not, the dying drive fix will save you from buying a new clone tool.

Was this solution helpful?