Error in backup 0x807800C5

Solved the problem: in my case it was a volume name problem. 

 1. I wrote a system image to a volume named x. 

 2. Now I'm using x for a different purpose so I'll image to volume y.

 3. I got this error that it could not access the volume. 

 4. FIXED THE PROBLEM by doing: Control Panel, File History

 5. now it poops up that it can't find the volume x. So I tell it to use new volume y.

 6. AFTER THAT, then I "create a system image" and ... it works fine, even though at step 2 I specifically chose volume named y.

I'm using windows 10 home. So it seems that you need to go to File History and change the volume name.

Does that solve your problem also?

0x807800C5  Error on SYNOLOGY NAS while creating win10 system image...

Just don't get it, I've read hundreds of threads and blogs trying to resolve this and still MS and/or SYNOLOGY don't have an answer :-(

Meanwhile I hear about all these workarounds;  3rd party BU software, as well as creating VHDs on same NAS mounts to resolve, ARE YOU KIDDING ME Microsoft? and SHAME on you too Synology, why aren't you doing something?  Some of the solutions are quite good and very creative (these are the folks we need working at MS).

Here's the thing, I could create the WIN7 system image backup without issue on the Synology NAS, and I can create the WIN10 System Image on any MS pc/svr shared folder (e.g another network MS device) account, and yes on a WIN SVR 2016, however unable to create that WIN10 system image on my Synology NAS. It's very simple MS, how about you and synology start following some standards like the IEEE for example and collaborate.  Indeed I've read that some other NAS devices do not have same issue but there are a lot of threads on this and feel WIN8 and 10 have been around long enough for you not to have an answer, I expect more from you!

Bottom line, there should be NOTHING that prevents a user from backing up a system image to an SMB network share, and that my fiends is the end of it.  MS needs to own it and resolve, not asking folks to come up with some outlandish solution that WILL in comes cases burn them when Disaster Recovery strikes.

yeah, I gave up on MS and just got a 3rd party software worked like a charm.

yeah, I gave up on MS and just got a 3rd party software worked like a charm. 

Indeed for once in the 21st century I'd like to see some ownership!

yeah, I gave up on MS and just got a 3rd party software worked like a charm. 

Indeed for once in the 21st century I'd like to see some ownership! 

It looks like 3rd party software is the only way to go. In fact that's what I started doing some time ago.

Very annoying when Windows claims to have built in tools for backup, but in the real world they simply don't work!