Windows 8.1: System Image Backup of C: drive fails, Error 0x8078012D and 0x8007045D

Anonymous
2014-01-04T23:16:08+00:00

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.

Windows for home | Previous Windows versions | Windows update

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

190 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-17T09:11:44+00:00

    Well I'm so happy for you that you haven't had a problem with this, but it doesn't work on my system, hence this thread.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-17T13:22:15+00:00

    Actually, Acronis True Image 2014 ( ATI ), based on conversations I had with their support team ( which was excellent ), says it's front in to Linux.

    Again, I'm not using ATI 2014 for backups, only cloning.

    Also, there's nothing to deflate because it works. I've found a solution that works 100% of time.  To validated it worked:

    Test #1

    a. I change items on system

    b. cloned from a known good drive

    c. drive to drive clone, not image to drive

    d. system was placed back to time before changes in step "a"

    e. and it only takes minutes not hours because write speeds are ~ 250MB/s

    Test #2

    a. deleted items so system would not boot

    b. did drive to drive clone ( usb3 to laptop)

    c. system came back up in minutes

    Feline1,

    I'm grateful you created this thread, it was a starting point and it galvanized a lot of people.

    However,  all I'm trying to suggest, is move on... Microsoft isn't going to fix anything.  They are not convinced it's an issue.  They are not even participating in this thread.

    There are 1000s of threads all over internet concerning this issue and it goes back many years ( 2010 ) and it's broke on many different versions of Microsoft Operating Systems.

    I needed a secure and reliable method to backup ( clone ) my system 100% of the time, not 50%, 80%, or 95%, but 100%.  I found that solution and thought I share it with rest of the audience here.

    I spent $8000 plus, bought four Dell XPS 15 9530s.  The problem persists with System Image Backup across all four brand new systems running Windows 8.1 Update 1.  System Image Backup would start out working fine, but later failed.  And that isn't real issue, because I never even tried to restore because I had absolutely no confidence...   I returned 3 of the systems, kept one because Dell support couldn't provide a means to return system back to factory default ( way it was shipped ).  That's another story for different thread.

    So you can do whatever you think is best, but my suggestion would be to find another solution that works for you, if you haven't already done so...

    There's no need to reply.  I was merely informing others of my discovery.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-17T13:35:31+00:00

    feline1,

    DanlZme, was merely responding to my question below:

    Has anyone on these threads every successfully performed a restore using image backup?

    Thanks DanlZme for update

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-17T13:38:17+00:00

    The poster asked: Has anyone on these threads every successfully performed a restore using image

    And I answered. You were sent several troubleshootng steps did you ever try them?

    It sounded like your drive has some corrupted sectors maybe running a defrag on it would help. A lot of people think that you can't defrag a SSD but that is ridiculous because it will s just as or more damaging to reimage an SSD then a defrag. If the drive is not corrupt then it is most likely the controller. Windows doesn't really see the physical data location on a drive since the drive controler obfuscates it. The controller can dump a request for an IO without telling to OS or it can tell it.

    No reason to be rude toward people trying to help

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-09-17T13:50:30+00:00

    This is a community of peers not a Microsoft support forum. If you feel the issue is Windows you should contact their support as well as the PC vendors support since they are required to give support for windows for up to one year.

    Most error reporting is done automatically if you choose the option and by enterprise user. If this issue hasn't been addressed it could be that enterprise user haven't had a issue out side of a system configuration that had errors in the hardware. If you feel it is the OS then it is best to let support know. Otherwise Microsoft has no way to know very much about the issue. They can't read users minds and since there have only been a small amount of of people having the error it is hard to get an issue like that on their radar unless you tell them there is an issue. Imagine 200,000 users make images and 10 can't and they fail with a generic IO error. That would appear to be a hardware failure. So they check if a similar rig can make an image and it success. Since the issue can't be replicated on their hardware it can't be debugged. If you provide more info they maybe able to get more info to see where the issue is. Chances are its the drives drivers or a corrupt disk

    I don't mean this to sound rude just short on time. A lot of times users think this is a Microsoft support forum and get upset when an engineer doesn't offer help. Just trying to clarify some common misconception and how difficult debugging is. I do it everyday...

    Was this answer helpful?

    0 comments