Error in backup 0x807800C5

Anonymous
2012-10-30T03:49:38+00:00

OS Win 8 pro 64 bit, no third-party antivirus (Windows Defender only).

System state backup on network share failed with error code  0x807800C5

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

73 answers

Sort by: Newest
  1. Anonymous
    2016-09-26T11:01:13+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-23T11:55:15+00:00

    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.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2016-07-31T01:59:34+00:00

    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)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-07-29T06:46:10+00:00

    To recover from the image, you will mount the VHD using another computer and extract the folder "WindowsImageBackup" with its entire content to the root of an external USB hard drive.  Then start your Windows Recovery process to recover from the external USB hard drive.  I have tested WBADMIN backing up to VHD/VHDX on Windows 7, 8, 10, as well as Windows Server 2012 R2 and they all work.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-07-29T01:48:53+00:00

    Thanks, creating a VHD is a great way to successfully put a WindowsBackUp image on my Synology NAS (D111).

    My problem isn't with the creation of an image, it's with the (more critical) RECOVERY of the image. I can recover the image if Windows is still operational...but...if the disc fails completely, all that is available is the use of a "Windows Recovery Disc." That disk boots into the "Windows Recovery Environment," which doesn't seem to recognize a VHD and renders the image unavailable/useless.

    Am I missing something?

    Win 10 pro 64 bit

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments