Windows 10: Macrium Reflect 6.3 1665 - ERROR 1000

I just purchased a brand new Samsung 512GB 850 PRO Series SATA III 2.5" SSD as my "main drive"
I also purchased a brand new Western Digital 1 TB Black 3.5" both for my Dell XPS-8700
I am running the newest Macrium Reflect Pro and I backup up my SSD on to the 1 TB HDD.
BOTH Drives are "clean". Yet EVERY time I successfully finish Back-up (with Verify) it finishes OK,
except I always get ERROR 1000. I've tried SFC, and dozens of other MS Programs, but always get same ERROR ????
I very seldom, if any, got ANY errors when I backed-up my SSD to my external Seagate USB 3.0, except it took three times as long !! PLEASE HELP ME !!






:)

 

Can I create a recovery partition for Windows 10 after I upgraded from Win 8.1?

TY for the suggestion.

I tried Macrium Reflect free edition version 6.3 today after using the backup tool in the Windows 10 Control Panel for a year - but never testing a restore until this week..

Macrium Software | Macrium Reflect Free

It seems to build a larger image file before initiating the backup than Windows 10 (version 1703 Creators Update) image creation tool in the Control Panel named "Backup and Restore (Windows 7)."

(However, once the backup is complete it appears the image was compressed resulting in a smaller footprint on my Western Digital 1T portable drive.)

It also seems to take about twice as long to complete the backup.

But since I got an error message at the end of an attempt to use "Backup and Restore (Windows 7)" to test a restore on a Dell desktop -- an error I learned I could ignore -- perhaps I will take a closer look at Macrium Reflect.

 

Disk Imaging

Hi, this is Rob again.

Try Macrium Reflect - Free for home use.

How to Create a Full-Disk Backup of Your PC with Macrium Reflect

https://www.howtogeek.com/howto/7363/macrium-re...

Macrium Reflect - Free

Macrium Software | Macrium Reflect Free

Hope that helps and feel free to choose a rating and have a great day!

 

I don't have an answer to your problem. My configuration is almost identical to yours, but I've never seen that error. Are you still on the Insider Preview, if so maybe that is the problem, since I've been using the current released version of W10 ( Ver 1607 Build 14393.693).