Window System Image Backup fails error code (0x807800C5)

Question

I am getting the following errors messages when trying to create a backup image:

There was a failure creating the backup image in one of the volumes in the backup set (0x807800C5)

Additional information:

The process cannot access the file because it is being used by another process (0x80070020)

I have also attached a screenshot of the error message.

I have tried running sfx /scannow and that does not fix the problem.

This is a link to the event log entries when the failure occurs:

https://www.dropbox.com/s/fg0c4907mh3o0s4/System%20Image%20Backup%20Failed.evtx

Answer 1

Check this thread:

http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/windows-8-backup-error-code-0x807800c5/0ec7fea0-bb4d-44d2-9381-c364ef2c1f6c

http://superuser.com/questions/508932/windows-backup-failed-with-error-0x807800c5

Answer 2

Imagine a company that makes software that has a program that has bugs for backing up.

You cannot write fiction like this.

Meantime,

I have 0x807800C5 on one drive and 0x80004001 on another. Plus an hour of MS live chat. And they wanted to charge me to fix the problem, I just upgraded to Win 10 three days ago.

Any help would be really helpful.

Answer 3

I have a revo 3x2, pcie SSD, with win 8.1, I installed 8.1 pro, turned off file history, deleted the WIndowsImageBackup folder in the back up drive (the drive containing the backup), and re-ran the system backup and it worked fine. I made sure to start the VolumeShadowCopy service. Hope this hleps.

Answer 4

I had the same issues and found the solution it seems crazy to say this but you need to be logged on to the "local account". 

After I logged of my office 365 account and used local settings i had no difficulty creating a backup of my system.

Answer 5

Signing in to a local account makes no difference to my problem - it remains the same.

This problem is clearly associated with failure to access the EFI partition on the boot disk.

My problem is that I do not understand why this only happens on one laptop and not on any of my other laptops, with UEFI or with BIOS.