Windows 10 Backup

Feb 5, 2019
4
0
10
I am trying to create backup but every time at completion the green progress bar turns into red and following message appears
The backup failed
New bad clusters were found on the source volume. Theses clusters were not backup
(0x80780070)
 

kanewolf

Titan
Moderator
You have a disk that is failing. You may have to do a file-by-file backup of your personal data to see if any of your files are corrupted or if it is system files. It sounds like, you will probably end up doing a clean OS install on a new drive rather than being able to backup the system and restore.

What backup software are you using?
 
Feb 5, 2019
4
0
10


 
Feb 5, 2019
4
0
10
Thanks for reply, window and computer is working normally without any problem
But fails to create backup, in case of any crash n no backup everything will be lost
I am using windows 10 backing program included in windows 10
 
The backup tool included in Windows is terrible. I recommend using Macrium Reflect or EaseUs Todo Backup instead. Those will at least give you detailed error messages. I feel the pay version of Macrium Reflect is better. But the free version of Easus Todo has more features.

https://www.macrium.com/reflectfree
https://www.easeus.com/backup-software/tb-free.html

After you've made the backup, run the manufacturer's disk health check program as recommended by kanewolf. If that reports the drive is OK, run a chkdsk on the drive. If chkdsk reports problems that require fixing, run it again with the option to fix any errors. This is necessary to force the drive to move the bad sectors/clusters to a part of the disk which still works.

https://neosmart.net/wiki/chkdsk/#From_My_Computer-5

Unfortunately this can take a lot of time (hours, sometimes days if the drive is in a bad state), which is why you want to make the backup first. But hopefully it only takes 10-20 minutes, and successfully clears up any bad sectors. You'll want to monitor the drive closely for few weeks, to see if more bad sectors develop. If they do, that's a pretty good (bad) sign that the disk is dying, and should be replaced. But hopefully this was a one-time random incident.