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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-27T15:04:26+00:00

    I suppose you have eliminated any third party Anti-virus software from being part of the problem?

    Do you know for sure it is the C: drive that is causing you problems?  I was thinking you might try using the wbadmin command as JVDEV# illustrates.  When that utility works, you can watch the progress of each partition as it is being backed up. 

    I'm not using any 3rd party anti virus! :)

    All I know is what the error dialogs always say - some cryptic Microsoft Error Code, vague mumblings about an "I/O error" and urging me to run CHKDSK /R.

    I will try running when wbadmin command from the power shell, and see if that achieves anything...

    I still suspect it is something to do with encrypted files on my C: drive, although if that's the case, I don't see why we can't get a straight answer out of Microsoft as to whether the VCSS can cope with encryption (or why the error message can't report that as the problem).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-27T14:59:46+00:00

    I suppose you have eliminated any third party Anti-virus software from being part of the problem?

    Yes, as I am not using any third party Anti-virus software :)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-27T13:52:58+00:00

    I suppose you have eliminated any third party Anti-virus software from being part of the problem?

    Do you know for sure it is the C: drive that is causing you problems?  I was thinking you might try using the wbadmin command as JVDEV# illustrates.  When that utility works, you can watch the progress of each partition as it is being backed up. 

    JVDEV# has a problem with his basic command in that the -allCritical switch already includes C: so it does not need to be added again.  But you can see from his attachment, there is no progress in his EFI partition, which is strange since there is so little data in that partition.

    The command runs fine in a Administrative Command Prompt window, so you can start it there.  Hopefully, the result of this exercise would be to confirm which partition is having the problem and possibly how far into the process it occurs.

    I don't use OneDrive, but I have heard comments it is not included in backups.  Hopefully that is correct and it is not involved.  I suppose links to other drives or devices trying to be backed up during the process could also be involved.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-05-27T13:52:28+00:00

    I haven't tried the steps above as listed by JVDEV but I was successful in backing up my hard drive by using a third party program called Acronis true image ...

    Thanks animeowns, but if you read the whole thread, you'll see I've already tried Acronis True Image. It fails with the same error.

    As I understand, Acronis is basically nothing more than a fancy GUI front end for the same underlying Microsoft **Volume** **Shadow** **Copy** **Service** that Control Panel > File History > System Image uses.  So it's not surprising that I get the same problem.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-05-27T12:30:16+00:00

    I haven't tried the steps above as listed by JVDEV but I was successful in backing up my hard drive by using a third party program called Acronis true image with both drives connected. I will let you know my results after I disconnect my other hard drive.

    Was this answer helpful?

    0 comments