Error in backup 0x807800C5

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

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.

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?

Hi Lawrence, no worries at all.

It does seem that Windows 10 has caused lots of issues for various different features, I suppose it's to be expected with a new release though. No doubt things will get ironed out over time.

I am doing this on Windows Server, but I'm not using Powershell, batch script or the command line directly. I'm doing this through Task Scheduler, and as the wbadmin command still exists in Windows 10, it should work with Windows 10 also.

I will guide you through what I have done, but on a Windows 10 PC:

1. Go to Start, type "Task Scheduler" and press Enter.

2. On the left, right-click on the item called **"Task Scheduler Library"**and click "New Folder...". Name the new folder something like "My Backup" so you can identify it later.

3. Right-click your new folder and click "Create Task...".

4. On the "General" tab, name the task something you'll recognise if you need to change it later. Select "Run whether user is logged on or not", tick the option to "Run with highest privileges" and to make it "Hidden". Also, on the general tab, you may need to change the "Configure for:" item to "Windows 10". 

5. Go to the "Triggers" tab and click "New...". Here, select when you would like to run the task. I have mine setup as a "Daily" occurrence running when my computer will be on, but not being used (e.g 03:00 am).

6. Go to the "Conditions" tab. If you have a laptop, you may want to "Start the task only if the computer is on AC power". the settings on this tab are really down to what kind of device you are using and how you want to configure it. Whatever you do, try to keep it simple!

7. Got to the "Settings" tab and tick, "Allow task to be run on demand", "Run task as soon as possible after a scheduled start is missed", "Stop the task if it runs longer than: 3 days", "If the running task does not end when requested, force it to stop". You can alter these selections if you wish, these are the settings I generally use.

8. Go to the "Actions" tab and click "New...". Leave the Action as "Start a Program", in the "Program/Script" text box, type: "wbadmin" (no quotes). in the "Add arguments" text box, type: "start backup -backupTarget:(Your Backup Drive, e.g E:) -allCritical -include:(Files to be included in the backup, e.g C:,E:) -quiet". Change the items in brackets to actual file paths/locations on your computer. Here's an example if needed:

start backup - backupTarget:\192.168.1.3\BackupFolder -allCritical -inlcude:C:\Users,E:\ -quiet

After this has been done, click "OK" on both windows you have open. A new task should appear in the middle pane in Task Scheduler. To test it, right-click the task and click "Run". You can view the history of each task by clicking on the task and then clicking the "History" tab on the lower-middle pane of the Task Scheduler. Here you can see whether the task has been started/completed successfully or not.

Thank you VexB, very helpful, that's probably about 90% of what I need to do... however, the files backup in Windows 10 was already working. How could I modify this process to take image backups of my 2 drive partitions in case I need to completely replace a hard drive and redeploy from a USB boot stick? My version of Win10 like many others is the free upgrade from a Win7 build, so if I have to reinstall from scratch I'm up the creek without a paddle because the free upgrade is no longer available.

I am running Oracle VirtualBox so that I can play a couple of old favourite games written for XP (XP mode doesn't seem to be powerful enough) and I think it may be the virtual XP machine which causes the image backup to fail.

Thank you VexB, the theory makes a lot of sense....

However, you're doing this on a server, probably through PowerShell. Those of us on desktops or laptops will be doing this through the Windoze backup and restore GUI. (Win 10 tries to emulate the Win 7 backup and restore because there is no native system image backup on 10.)

I've tried this, but as soon as I replace \NAS\ with the IPv4 address, the "OK" box greys out and I have to confirm the location using the Browse button. This of course replaces the IP address with the "friendly" name and we're back to square 1.

I'm wondering if anyone with any authority from Microsoft actually monitors these forums and admits that Windows 10 has introduced problems which simply did not exist in 7?

We should not have to experiment around to make an image backup of a home desktop device. It SHOULD simply work.