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

OK folks -

so, I ran the backup again (still from a clean boot), using the following command in Windows Power Shell (run as Administrator)

**** wbadmin start backup -backupTarget:F: -include:C: -allCritical

It failed again!

The console output is no more use than running from the GUI: it's just the same message about an I/O error and advice to run CHKDSK /RIt also claims to have created log files saying which files were and were not backed up -

however this is bogus - the successful files log is blank, and the failed log just contains this error message:

Backup of volume C: has failed. The operation failed due to a device error encountered with either 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.

I'm getting a bit sick of this!! I suspect that whoever wrote this code just put that text string in there for the error message, but it's not appropriate.

Again, you do not need the -include:C: switch in the command.

The wbadmin command starts and shows you which partitions are going to be backed up and then you have to agree.

It then starts configuring the partitions then the copy process.  Can we assume as soon a you select Y the process threw the error?

You have stated you have some encrypted files on the drive with might be interfering.  Have you tried decrypting or moving them to a non-critical partition?  Are you using Bitlocker or some other utility?  I do not have any encrypted files, but it appears something is keeping the drive from being accessed, so I suppose the encryption could be involved.

Here are a couple of relatively easy things to try, which may or may not help 

• Try running the System File checker in case there are some of the System Files that are corrupted and preventing the system image from completing.
  • From Within the Command Prompt (run as administrator)
  • Type sfc /scannow
• If any errors are found which can't be fixed then try the Deployment Image Servicing and Management Tool.  Once again this is run from within the Command Prompt as administrator.
  • DISM /Online /Cleanup-Image /RestoreHealth

The wbadmin command starts and shows you which partitions are going to be backed up and then you have to agree.

It then starts configuring the partitions then the copy process.  Can we assume as soon a you select Y the process threw the error?

You have stated you have some encrypted files on the drive with might be interfering.  Have you tried decrypting or moving them to a non-critical partition?  Are you using Bitlocker or some other utility? .

No, actually - after I select "Y" to proceed, the console output shows lines for percentage progress, it reached about 45% before the backup failed. 

(This is exactly the same as when I use the Control Panel GUI to make the system image... the progress bar gets a long way through before it declares there is an I/O error)

I haven't tried taking the encrypted files off the drive yet, no. I'm not using Bitlocker, just the Windows filesystem's own encryption feature on a couple of my folders.

Since Windows can read its own folders, and I'm running Windows' own Volume Copy Shadow Service (as Administrator), it would be daft if the VCSS can't read the encryption and can't display a suitable error message if that's the problem...

I also have 'BlackBerry Link' installed, and that has backed up some content from my BlackBerry phone (which is also encrypted), so I'm suspicious of that too...

The fact the backup actually gets to the progress listings tells me the VSS is working.

I just did a backup after encrypting some files.  The backup completed normally and the encrypted files were in the backup and still encrypted.

Your Blackberry link might now be the prime suspect. 

Edit:  I seem to remember quite a while ago, way before Windows 8, I had used some software which put a file on my system that caused me not to be able to search a certain directory.  The software was no longer installed but the file was still there.  I do not remember if it effected backups, but the way I found it was to search folders to see if the search would complete and then narrow down the search until I found the offending folder.  Probably not relevant, but something to think about.