I too am having this problem. Mine fails almost immediately. Trying to backup to a QNAP NAS. When I try to change the settings to a different drive it hangs. Anyone find a solution yet? I ran SFC and it came back clean. Ideas?
Error in backup 0x807800C5
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.
73 answers
Sort by: Oldest
-
Anonymous
2012-11-12T06:58:18+00:00 -
Anonymous
2012-11-12T16:17:47+00:00 DER LINK zur Frage an Windows:
THE LINK on the issue of Windows:
LG
Thanks for posting this. I was pulling my hair out. Hard to understand why they don't support NAS servers.
-
Anonymous
2012-11-12T16:39:07+00:00 DER LINK zur Frage an Windows:
THE LINK on the issue of Windows:
LG
Thanks for posting this. I was pulling my hair out. Hard to understand why they don't support NAS servers.
Where do you see that NAS servers are not supported? My translated page says nothing about that.
-
Anonymous
2012-11-12T18:30:55+00:00 DER LINK zur Frage an Windows:
THE LINK on the issue of Windows:
LG
Thanks for posting this. I was pulling my hair out. Hard to understand why they don't support NAS servers.
Where do you see that NAS servers are not supported? My translated page says nothing about that.
The answer is not understandable! Which page was here read or translated?
-
Anonymous
2012-11-13T06:17:49+00:00 For anyone else interested - I did a few tests today. On four different workstations I can backup to 3 different window's servers without any problems. But any of those 4 computers cannot backup to any 3 of our QNAP NAS units. Two units were joined to the domain, one was left solo - didn't matter. Windows 8 does not let you backup to a NAS network share.
Who's problem is this? Is this a SMB v3.0 bug, a windows bug, a firmware update required on the QNAPs? Where do we go from here?