Error in backup 0x807800C5

Thank you 16UE;  By following your instructions, I was able to recover a system image from my NAS  via a recovery CD!

Win 10 Pro 64 bit ("upgrade" from Win 7 Pro 64)

Synology Diskstation (NAS)

I have been battling this over the past few days on Windows Server Essentials 2012. I think I have a solution to this problem.

I have been trying to use Task Scheduler to run a daily backup to a Synology DS1515+, which I have made a network share ( I'll call this \NAS on here). I created a task, ran it with "highest privileges", etc. In the "Action window, my settings were:

Program/script: wbadmin

Add arguments: start backup -backupTarget:\NAS\FullBackup -allCritical -user:Username -password:Password -quiet

It failed everytime with the same error as you were getting. However, I have just changed the network share name to the NAS IP Address and it ran without a hiccup. So the structure of my working backup settings are:

Program/script: wbadmin

Add arguments: start backup -backupTarget:\10.10.10.15\FullBackup -allCritical -user:Username -password:Password -quiet

So for people using windows 7/8/8.1/10, maybe try using \[IP Address]\Folder instead of \NetworkShare\Folder and see if that helps.

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.

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.

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.