Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, October 16, 2015 4:06 AM | 3 votes
Hi,
When I backup on external drive, the backup goes fine. When I backup on password less NAS, I get this error:
I searched online for solution but seems like it is an unique problem for me. Asked on Microsoft Answers Community but the technical support engineer suggested to ask here on TechNet rather then in the community. Now I really wish someone can give me a solution for this problem.
All replies (31)
Wednesday, June 8, 2016 7:38 AM ✅Answered | 7 votes
The key is that windows only allows one image backup. So the first image backup succeeds and the second image backup fails. Unlike windows 7, windows 10 is unable to overwrite or delete the old image backup. One solution is to rename __nas_backup_WindowsImageBackup_host-name to __nas_backup_WindowsImageBackup_host-name.bak. Replace _ with \ Now run Windows 10 image backup.
Friday, October 16, 2015 5:34 AM | 1 vote
Hello,
Suggest you to try the suggestion mentioned here and see if it helps:
Hope this helps, Good luck :)
Windows Troubleshooting & How to guides - http://www.kapilarya.com
Friday, October 16, 2015 2:59 PM | 1 vote
Though the error numbers are not same, I tried your suggestion and did not work. It works perfectly alright with local drives (USB, 2nd partition etc.) but do not work over NAS.
Tuesday, October 20, 2015 2:08 AM | 1 vote
Hi,
We don’t know your NAS system but it might occurred due to bad compatibility of your NAS system on new version of SMB protocol.
You need to navigate to your NAS side and find out the path of smb.conf (for example, /etc/smb.conf).
Edit /etc/samba/smb.conf.template
Find "max protocol = SMB2”, and replace it with "max protocol = SMB2_02"
Service samba restart
And try to back up again to see if error is gone, if the issue still persists, try post it at Linux or your NAS system forum see if they have similar practice.
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, October 20, 2015 2:39 AM | 1 vote
Same here, my first backup worked fine, but the second one, nah, no way...
It fails when it is creating the "system image restore".
[]'s
Friday, October 23, 2015 8:24 PM | 1 vote
Just got the same problem. Have been backing up to my Synology NAS for years, but recently the backup has started failing. First it reported RPC error and on the last try I got just the same error as reported here. Could this be caused by some recent update?
/SJB
Monday, November 9, 2015 7:44 AM | 1 vote
I have the same error on system image .
No errors during the backup in local usb disk but errors with system image saved in network position (NAS) .
I reinstalled the os and continue to have the error.
With old insider build of Windows 10 , no errors . Is it a bug ?
Monday, December 21, 2015 9:02 PM | 1 vote
Same here, my first backup worked fine, but the second one, nah, no way...
It fails when it is creating the "system image restore".
[]'s
Same here. First backup done on Dec 5 is fine, 4 subsequent backups have all failed with this very cryptic message. Not sure if this is an update or that it just flat out doesn't work on second attempt.
Wednesday, August 10, 2016 11:55 PM
This is the answer. Richard, thank you.
Monday, August 29, 2016 2:46 PM
Thanks!
Monday, August 29, 2016 2:46 PM
Don't have access to the NAS shell, so cannot do anything on NAS end.
Wednesday, March 1, 2017 7:03 PM
Not sure I follow this for at least one reason:
1. I have Synology NAS
2. Three Win10 PC's plus others
3. File Share on nas called \NAS\MyBackups\Computer1...\NAS\MyBackups\Computer2 and so one, Five PC's.
4. Windows 2008 DC (We'll call it Computer1) is backing up to NAS just fine.
5. Win10 PC (Call it Computer2) is backing up to that NAS location just fine, and does so weekly, therefore overwriting the current system image with new one each week.
6. Problem is I have two other win10 computers that seems to give same error each time when I try to. A. Create a System Image, or B. Run Backup (which btw I only create a system image) and would like to do so weekly.
So when you say: Only one and rename, that doesn't make since to me, cause I have one doing so all by itself and running 10, and another running Win2008...And when MS says one computer per location, is that the entire NAS mount point? Or if different folder will that help...cause that's what i'm doing and two work each week just fine...
Any help is appreciated here, thanks
Friday, May 5, 2017 7:53 PM
Did you find a solution to this problem?
Tuesday, May 23, 2017 4:07 PM | 4 votes
I have a Synology NAS and just started receiving this error after updating to Creators Update. Before the update no problem. How did you resolve. Most suggestions I have seen are not applicable
Tuesday, May 23, 2017 4:08 PM
Did you find a solution to this problem?
Wednesday, December 6, 2017 5:55 AM
I just solved this problem on my home setup. One Win10 client (only that one out of many!) was failing with this error while backing up to Synology NAS. The issue seems is related to backup credentials on the client machine.
Going to "Control Panel->Advanced sharing settings->All Networks" and selecting "Turn on sharing so anyone with network access can read and write files in the Public folders" solved the issue for me.
Tuesday, December 19, 2017 3:23 AM
I've changed my backup HDDs recently. On one of them, I left the old image folder of one of my PCs (had this problem on both of them) and was able to fix this error on that one.
I copied the old image folder from this PC onto the new backup HDD (implies changing the owner of the "imagefolder" to yourself, restoring it to the new backup HDD and then reassining the ownership of this folder to "system", once again) and finally used the normal backup wizard. This worked immediately and I was able to perform a full system image backup!
Unfortunately for the other machine, I don't have neither the image folder nor the old backup disc, so I'm still waiting on a solution...
I think this has to be linked with finding a way of resetting the full backup location in Windows 10, to a new HDD or NAS share or whatever... I even tried deleting the registry keys related to the backup, but to no avail...
Sunday, January 21, 2018 2:56 PM
I too am fighting with this same issue.
This is my first backup of this system and i repeatedly get the error, even if i delete any previous attempts. I'm backing up a Windows 10 system to the network.
I have another Windows 10 system on the same network, backing up to the same network destination, where there are no issues.
Has anyone successfully solved this?
Sunday, January 21, 2018 9:55 PM
I believe it is related to having an EFI partition. My laptop fails when System Image backup process tries to backup the EFI partition. I have an older laptop without EFI partition and System Image Backups work. For me non-System Backups to UNC path work as expected. I discussed with [email protected] at the Microsoft Insight Confernce 2017 in Orlando. So far, even though he expressed at Microsoft Insight, no response.
Tuesday, January 30, 2018 7:25 PM
I have just found an answer. As a fresh NAS user i was also battling with the could not reconnect drives' at startup, even though i tried the two most common 'fixes'.
I then saw someone saying to use the IP of the NAS instead of \FREENAS\ in the path (or \xiaomi as the thread starter's case is). That helped with the drive reconnection AND also allowed me to make backups to the network.
EDIT: i spoke too quickly, after actually transferring the size of the disk i was trying to backup, i got the same error. At least the data was transferred, i used to get an error after only a few MB were transferred.
Thursday, February 1, 2018 2:02 AM
I had a similar problem with Windows 10 backing up to a share on a NAS. My solution was to change the device name to an IP address. Example: \NAS or computer name\share\folder to \IP address\share\folder... In my case it was \10.100.1.66\WS_Backup\COMPUTER12 ... hope this helps. Then ran the Backup and Restore (Windows 7) again.
Chris
Thursday, February 1, 2018 6:05 AM
Like i mentioned in my edit above, this did not help me.
The backup process did fail right at the end, after transferring all of the data, while it failed at the beginning before. But the error is the same and the behaviour is now the same if i put in the IP or the servername (\FREENAS\, so something else had to change.
I tried backing up to a USB drive a few days ago and the backup did complete, but i got the 'Parameter is incorrect' error until i unplugged the USB drive.
Something weird has to be causing this.
Sunday, February 4, 2018 8:59 PM
Does your PC have an EFI partition? The EFI partition is definitely the cause of my failure.
Sunday, February 4, 2018 9:29 PM
Indeed it does. If it's a problem, what is the solution then?
Monday, February 5, 2018 6:11 PM | 1 vote
No idea. I back up to USB and copy to NAS. I created a trouble ticket with Microsoft. The support was horrible. They could not comprehend the problem
Wednesday, February 14, 2018 7:43 PM
Try AOMEI backup its free and works every time, windows 10 backup is not very good outdated and many faults and this is the best Microsoft can come up with for backup from windows 7 to windows 10 I too had same problem an this error backup error 0x807800c5 windows 10 I tried on a usb 1Tb external hard drive with no data on it
Masbro40
Wednesday, September 12, 2018 9:23 PM
Obviously it's not the reason. I used a totally empty folder but still got the same error. Everything went well till the end of the backup process. I suppose the backup is finished normally but still got this error. Could it be a false-alarm? How to verify the integrity of the current backup.
Saturday, October 27, 2018 1:33 PM | 1 vote
This sounds a interesting direction, but not solve the issue for me. I have exactly the same error ID while trying to backup to a Synology NAS. my /etc/smb.config:
max protocol=SMB3
also tried to remove any previous unfinished backups or even reset whole setting, all not successful. very frustrated, but still desperately seeking a solution.
WIN 10 64 pro (Version 10.0.17134 Build 17134)
Apparently, the error ID of 0x807800C5, which indicates backup images creation failure, but can be diverse details:
- OP: I/O operation aborted
- me: The specified backup disk cannot be found
I notice the red bar and error turns up just after finishing my local profile(~500MB) copied and while trying to create system image! and the structure created within the appointed the NAS backup folder :
- WindowsImageBackup\
- myPCName\
- MediaID.bin
apparently, myPC profile was backed-up successfully in .\myPCName,
but Windows Image creation was crashed.
Just now I did a test without the system image only my local profile folders, the backup passed. if add system image (3 partitions) then it fails at Esp.vhdx only 4096KB!
So indeed it may related to EFI partition & SMB, VHDX file mounting...
Wednesday, November 7, 2018 8:30 AM
here some workaround:
Wednesday, November 7, 2018 8:34 AM
There is an issue about timing on big files writing on fs used into the NAS (e.g. ext4 or xfs). A workaround is to add a string: "strict allocate = yes" into /etc/smb.conf (into the NAS s.op) under [global] area.
It does not always work.
Wednesday, May 13, 2020 10:01 AM
Open File Explorer and navigate to the C:\System Volume Information.
Look for the WindowsImageBackup folder.
If the folder is present under System Volume Information folder, right-click on it and select Remove.