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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-06-01T15:09:19+00:00

    Mine is definitely UEFI. Don't think any computers with Windows 8 or 8.1 as native OS have legacy bios.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-01T11:08:17+00:00

    Hi Bruce,

    Just to confirm and throw my theory out - Did you actually verify your motherboard has UEFI BIOS?   I guess it is possible to purchase a machine with Windows 8 and Legacy BIOS.  It's easy to verify.  Just RUN msinfo32 and see what it says for BIOS Mode.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-31T21:43:18+00:00

    my system does indeed have an old non-UEFI BIOS, so perhaps this is causing the issue... but if so, it would surprise me that the backup gets half the way through before failing - that suggests it is more to do with particular files, rather than a fundamental problem with talking to the underlying SATA bus?

    I agree that Microsof seem rather shifty in their response to this issue. Googling shows that it has been affecting users for several years now. No "MVPs" have had anything to say on this thread for months. I get the feeling it's a known issue which has been tagged 'won't fix' bymanagement- probably something along the lines of "this is a really nasty bug which makes Windows look bad, but it only affects legacy hardware so we'll just ignore it until it goes away". I could be wrong but the cynic in me smells a rat!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-05-31T19:13:30+00:00

    The problem, quite frankly, is Microsoft. My Toshiba laptop came with Win 8 and I upgraded to 8.1. When the dreaded KB2919355 spring update came out I literally wasted a month of my time unsuccessfully trying to install the update. I eventually had to wipe my HD, re-install Windows 8, download and install 114 updates, and update to 8.1 through the Windows store which, by this time, already included the dreaded KB2919355. Finally, success!!! Determined not to have to go through this agony again I attempted to create a backup system image on an external drive only to get the exact same error message you have gotten. I have read the entire thread you have created with interest hoping that there would be a solution. Unfortunately no one has a solution and especially not Microsoft. If I have learned anything over the past month it is this, Microsoft could care less. Thousands of people could not apply the spring update for Windows 8.1. Microsoft not only didn't fix the problem, they didn't even acknowledge that it existed. It is also apparent from Google that error 8007045D in creating a system backup image has been going on for years and Microsoft has yet to come up with a solution. I wouldn't hold my breath. I have determined when this one dies I am going to linux or Mac. I have had quite enough of Microsoft. Good luck to you and if you should be lucky enough to stumble upon a solution please let us know.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-05-31T14:25:40+00:00

    Hi,

    I'm new to this forum and thread and a novice at creating System Images in Windows 8.  I have the exact same issue as feline1.  I have 2 Pcs running Windows 8.1 but only one of them is giving me the problem.  Both have pretty much identical contents (personal documents, photos, music, and programs) on the C: drive (the drive I'm trying to image)

    I was successful (no problem worked the first time) in creating a System Image on the PC that originally came with Windows 8 and was later upgraded to 8.1.

    However, the PC that was upgraded from Windows 7 Pro to Windows 8.1 is the one giving the same problem and the same error messages as feline1.  I think feline1 also upgraded from Windows 7 to 8.1.

    From my perspective, the big difference in the the 2 PCs is BIOS.  The PC that created the System Image with no problem is UEFI.  The PC that was upgraded to Windows 8.1 from Windows 7 Pro has Legacy BIOS.  Is it not so, that Windows RE for these two machines are different?

    As I understand it, Legacy BIOS machines will not enter Windows RE automatically like UEFI machines will when the PC fails to boot from its internal hard drive.  Since the Recovery partition is one that is automatically included in a System Image, could this be a clue?   I'm not claiming to have any idea of a solution but was wondering if anyone thinks this could have anything to do with the problem?

    Just thought I'd toss in my nickel.

    Was this answer helpful?

    0 comments