Windows 10: Macrium Error Code 10 - Cannot create image because of unused cluster

I'm using the latest Macrium version (6.2.1495) and running the latest Win10 Pro 64bit Insider Preview Fast Ring (14393.67, v1607). In other words, everything is up-to-date.

In the past I've had no problems creating Macrium image backups of Win10 Insider Previews. However, I now keep getting Error Code 10 regarding clusters when the imaging process starts:

I've done the whole chkdsk /r thing via Windows reboot and via Macrium Rescue Media (for the drive I'm trying to back up and even for the drive I'm backing up to) but to no avail.

There seems to be very little on the Net about this issue and Macrium doesn't give support as I'm using an Insider Preview Windows. Would any of you fellow-tenforumers happen to know what would help?

:)

 

System Image Backup Failed In Windows 10

After having Windows 10 for several weeks now, I was attempting to do a System Image Backup to DVDs. After about 6 hours, and on the 24th dvd, the backup was almost complete when it just stopped and gave the following error message and code:

"The backup failed. New bad clusters were found on the source volume. These clusters were not backed up. (0x8078007D)"

I have no idea what to do because doing a System Image under Windows 7 was no problem. Since the backup stopped before it was 100% complete, does that mean I cannot use the 24 dvds already created for a restore? I appreciate any assistance.

 

Correct Format for USB Stick | FAT32? | NTFS? | Some Other Format?

Windows 10 on PC.

I plan to use Macrium Reflect Free to create a System Image on a USB stick (not a removable USB drive). Macrium will create the Image as a .mcimg file. The file will be approximately 74 GB. In the future, when
I want to restore to the System Image, I plan to use Macrium to perform the restore. Because Macrium will be used for the restore, the USB stick does not have to be bootable.

Given this scenario, what format should be used for the USB stick? FAT32, or NTFS, or some other format?

Thanks

 

Anyone? Since I posted the question, I've updated both Macrium and Windows 10 Insider Preview (I'm in the fast ring) many times and yet I always get the error code 10. I've ran chkdsk many times and it hasn't found anything. Recently I did a surface test w/ Minitool Partition Wizard and it didn't find any errors. I have noticed, though, that the Transcend app (for the Transcend MTS400 M.2 Sata -drive I'm using) shows 99% instead of 100% in the wear out indicator (I've used the drive under two years). Anyway, I cannot locate the problem since none of the disk checkers I've used point out to the problem (unused cluster according to Macrium).

 

Somebody else got this error in the past and it was attributed to a problem in the EFI (Fat32) partition. To make sure try imaging all of the other partitions on the disk. If this works then you will need to run chkdsk against the EFI partition. I think you can assign a drive letter to that partition via Diskmanagement. See this article http://www.howtogeek.com/197296/how-to-use-the-diskpart-utility-to-assign-and-remove-drive-letters/

 

You hit the nail in the head with that advice! Thank you so much! I did as you said: Checked that Macrium was working with the NFTS partitions, assigned a letter to the FAT32 partition, ran chkdsk (letter): /r, got asked if I wanted to save lost chains as files (to which I answered yes) and then exited. Voil , I'm doing a full image backup as we speak and am very happy I (meaning you) solved this. *Smile

To be honest, I probably had read the same thing you had about someone else experiencing this, but ,for some reason, felt that the solution would be too complicated (especially since it was given years ago to an older version of Windows). I'm glad, though, that you remembered it and shared that link which made things easy. *Smile

 

Your welcome. Happy it worked out for you.

 

Add another success story. Had an EFI hidden partition throwing the error 10. Used DISKPART and CHKDSK, and now all is well!

 

Just wanted to say that this also helped me fix the same problem. I was not able to make an image of my drive (I am changing hard drives) and was completely stuck. Gave a letter to my System partition and ran CHKDSK for it and it was fixed. Not sure what it did because it never gave me a prompt, but as soon as the laptop restarted I could get it done!

 

Like you I was not able to use Macrium as it posted error code 21.
Many chkdsk /x /f /r were ran without success.
Many HD tests were ran: Crystaldisk, HD tune, HD sentinel, Sea Tools HP UEFI diagnostics, etc. and all were OK
So it was a puzzling why the labeling was needed for Macrium.

In the google search there were Macrium threads that implied that chkdsk /x /f /r does not check the full drive.
It appeared that it will only checks the parts of a drive with attached letters.

Somehow the chkdsk /r command though has fixed drives that had inaccessible boot device.
Chkdsk is not supposed to be able to fix RAW drives but in threads it has done so.

Does anyone have any information or a reference on which parts of the drive chkdsk /x /f /r can and cannot fix?

 

"...Does anyone have any information or a reference on which parts of the drive chkdsk /x /f /r can and cannot fix?..."
I can't answer the question directly, however, I have found such fix-it attempts to be a mixed blessing when tried on usb external backup drives. I'm posting so that I can monitor thread and learn alongside you when others post the answer you seek.