Feline1,
FYI only... I did do defrag on C: which is an msata 512GB SSD and system image backup still failed.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello everyone.
I've a lot of people encounter problems similar to this, but here is my particular flavour:
I have a Windows 8.1. Pro (64 bit) desktop PC.
I am trying to use File History > System Image Backup to create a backup image of my C: drive.
I have been trying to save the backup both an external USB 3.0 drive, and this time to a network location (on a WD 'MyCloud' EX4 NAS)
Every time, the backup fails about 3/4 of the way through.
I get an error dialog saying
"The backup failed. The operation failed due to a device error encountered either with the source or the destination. If the source or destination volume is on a disk, run CHKDSK /R on the source or destination volume, and then retry the operation. (0x8078012D)Additional Information: The request could not be performed because of an I/O device error. (0x8007045D)"
I've spent many hours diligently running CHKDSK /R both on my C:\ and the destination drives, and it has never once found any problems.
I've tried closing all applications, unnecessary services, background processes and disabling Windows Defender's real time malware checking whilst the backup takes place, but that doesn't seem to fix anything.
My hunch is that there's nothing wrong with the disks or hardware at all, and that this is some kind of obscure permissions problem, where Windows can't access symbolic links on my C: drive.
But I basically haven't a clue! :)
I'd be very grateful for any suggestions at fixing this, as currently I don't have any backup image of my C:\ drive, so if my PC goes kaputt, I'll have days of manual re-installing and configuring to do.
Thanks.
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.
Feline1,
FYI only... I did do defrag on C: which is an msata 512GB SSD and system image backup still failed.
There is a Backup error log file in the C:\Windows\Logs\WindowsBackup folder. Maybe that is what you are looking at for your earlier comment about no info being provided.
You may also find something in the Event Viewer, under the Applications and Services Logs, Microsoft, Windows, Backup section.
Since I have pretty much lost track of this thread, I will need to reinvestigate the situation. But the I/O errors seem to be stopping the transfer. Could you confirm your external drive is formatted in NTFS and you have full access to the network location?
You could try using WBadmin.exe to backup just one partition at a time to see if one is causing the error. Since a normal System will include all the critical partitions, like System, Recovery, MSR, and OS, you might just try the OS to see if it will complete.
Have you tried any other external drives?
What do I think?
lol well the whole point of creating a System Image of my C: drive is so that, if my C: drive fails or becomes corrupted, then I DO NOT have to completely reinstall Windows, all my applications, and data.
I simply restore the system image.
So saying "the solution to not being able to make a system image is to buy a new drive, and reinstall windows, all your application and your data" does little other than make me laugh.
The implication is that my C: drive is defective, however:
... so I'm disinclined to believe in some mysterious "drive problem" that is somehow immune to detection by all the regular methods, but somehow the WIndows Image Backup service can miraculously detect it.
Occam's Razor suggests a bug in the backup service is more plausible.
Saltgrass,
Thanks for feedback...
External ( destination ) drive I've been using is a Western Digital 2TB My Passport and My Passport Ultra. Both drives are formatted NTFS and both drives are connnected via USB3, not network ( Ethernet ).
My mention of logs were generic. Microsoft should know of other logs elsewhere in system that should help in isolating this issue.
I've located file(s) on my system where I believe problem to be.
When I drag & drop ( copy ) two folders, copying always stalls at 28% then system becomes non-response for some indeterminate time before coming back.
I'm able to reproduce the drag & drop ( copy ) issue 100%.
So instead of copying both folders, I'm going to try and copy each folder separately. If that fails, I'm going to simply delete both folders and see what happens...
Hello,
I really think we're really getting somewhere now!!!!!!!!!!
I failed to mention in my last post:
Before I committed to replacing the Samsung HDD SATA with the Toshiba HDD SATA I did exactly as you suggested. It was the next logical step.
I re-formatted the Samsung drive - then re-installed Windows 8.1 (using the Full Version 64 bit CD) - then installed all current updates.
I then (exactly like you suggested) attempted to to create a System Image (to the same newly formatted external drive) - prior to loading any of my programs or personal files.
I got the exact same error which really surprised me! This is what led me to the decision to replace my hard drive.
Also, and this is VERY VERY INTERESTING! I mentioned my system was acting up prior to my attempting the System Image when I first encountered the error. One of the things that was happening more and more frequently was exactly what you described in your last post.
I was also having problems dragging and dropping just like you. However, it was not isolated to just external USB flash drives but also between folders on the hard drive. The system would crash (freeze up) and I would have to restart. The problem would seem to go away for awhile but would reappear more and more frequently
These latest developments suggest to me that the Samsung SATA HDD was having some sort of physical problem. Probably electromagnetic issues. This is the weakness of HDDs that SSDs do not have. I'm thinking now I should have went with a SSD. However not knowing it would actually work, I was not willing to spend the money. SSDs are so much more expensive than HDDs.
Since you are using an SSD and not a HDD, I don't really know what "physical" affliction you might be having. SSDs are not electromagnetic but probably have their own set of electronic weaknesses I am not aware of.