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

Sid-B,

Sorry for late reply, I didn't get an email response until today...  Something must be wrong with email delivery system.

You can ignore everything I said below...  System Image Backup doesn't exists on Android....

You've obviously done some researching otherwise you would not have found this thread.

It's wise that you want to be proactive and backup all your data and system configuration.

I think you may be the first person on this thread ( which has been around for awhile  ) asking about performing this operation on a tablet.

I don't think system image backup, though feature may be available in windows 8.1 or whatever OS is installed on your tablet is supported.  And even if it is, I still wouldn't use it for the reasons below..

Even if you could get it to work, you would have to save image on a separate disk, not the internal disk that is in your tablet.

1. Does your table have port to connect to an external drive?
2. If it happens to have USB or micro USB, then you could possibly try purchasing a dongle of some sort to connect from USB to the drive or drive enclosure.
3. Will tablet software accept writing to a flash thumb drive or external USB drive using System Image Backup app?

If you just like to tinker, go for it...   But if you're conscientious about time I'd say find another alternative.

I highly recommend you do not use Windows System image backup for anything ( desktop, laptop, etc.. ) for following short reasons...

1. It simply isn't reliable

a. it works for many

b. it doesn't work for many

c. it's not reliable

d. it may work for you today - creating images

e. then it could fail later on - which happened to me

** even if someone tries to challenge me on this issue, they most likely haven't used image to restore or if they did, they don't do it often...

I'm very serious about my data and system configuration, etc...  You can read through thread to see my other comments

2. More important than the ability to create a system image backup is confirming image is good.
3. I'd guess that the vast majority of people who are able to create a system image backup, never do a recovery using the same image for the following reasons:

a. time... it's very time consuming

b. complicated, it's not straight forward

c. destructive, no one want to write back to their only system drive they backed up...

d. practically no consumer is going to purchase another disk and try and insert in into their laptop or desktop...

4. Finally, you don't see Microsoft anywhere on this thread offering advice that has been useful.

MicroSoft System Image backup is a very poorly designed product, quality assurance is even worst and I don't think Microsoft pays much attention to this feature.   Vast majority of people use some other means to clone their disk, create system image backups, etc...

I wish you best...    Good luck...

Hi,

I too was facing this problem till just a minute back. I read somewhere in these answers that we need to ensure:

• File History service is enabled
• Volume Shadow Copy service is enabled.

In my case, File History was not, so I

• Enabled File History from Control Panel.
• I retried creating the system image ... failed after taking a long time with progress reaching almost 90%.
• I gave it one last shot, clicked on System Image Backup from Control Panel -> File History applet.. after about 20% I was asked to label my disk with a name which cannot possibly be given to a volume, got the Class not Registered error message, click OK and continued, after around 15 minutes of steady progress the process completed.

In the target location I can see the folders which I usually see getting created after a system image is created.

I am doing all this on my new HP Stream 7 tablet. Its funny, I never even thought about protecting the OS of my DELL Android table, but after getting the Stream 7, in a day as if by some sixth sense I want to create a system image ;).

Backing up " User " data is trivial and not focus of this thread.  Anyone can simply drag and drop folders or files from one location to another.

If all one wants to do is backup pictures, music, documents, ( files ), then system image backup isn't necessary.

Purpose of system image is to backup " Whole " system in case of disaster or should one want to upgrade to a faster or larger drive.

So while I agree you can inspect and look at " User " files primarily, there's no way to know which system files and binaries may be needed or could be restored when system misbehaves badly, application is corrupted, or worst drive dies...

Even if you could identify a system file or binary that had problem, rarely ever will you be able to simply drag and drop one system file and get an application to work or system to boot, etc...

I'm of the opinion whatever works for one is correct solution.

For me I want something that works flawlessly, 100% of time with minimal effort on all my windows platforms ( hardware, software, operating systems ).

System Image Backup has never, ever worked for me once.

While I've been able to perform successful System Image Backups in the past, I've never been able to simply, plug in recover disk and restore System Image Backup to a brand new drive and have the system boot afterwards or if it did boot, come up with same exact configuration, including the hidden partition that most vendors include the original system configuration from factory, plus OS.

Something was always missing and since I didn't know how extensive the differences were I would basically have to reinstall Windows from scratch and re-install all applications again which could take days, even weeks.  And many of the application configurations and settings ( browser, word processors, spreadsheet, video and sound editing, program editors, virtual machine software, etc... simply could not be reconfigured from memory...

***************************************************************************************

So for all of you who like System Image Backup, great...

... Just make sure you've confirmed you can restore complete image to same or different disk and system boots as expected...

I wouldn't recommend recovering to same disk, because if it fails at all, you lose everything.

And most people will not do following because of time, expense, effort and / or lack of knowledge:

1. purchase separate disk to practice on
2. create system image backup
3. create recovery or boot disks
4. remove original drive from system
5. install new / practice drive in system
6. boot off recovery disks
7. restore system image backup to practice disks
8. confirm it's working

***************************************************************************************

For me, I would like to see MS create cloning feature so I could clone to an external disk, boot off of  external cloned disk, then later swap it with internal disk in laptop should need arises.

Highly unlikely they MS will ever do that because of Monopoly Laws and software vendors complaining.

If MS did implement a superb functioning backup and cloning built in apps that work 100% of time then there would be no need for after market and third party software which would cause hugh anti-trust and monopoly lawsuits...

Again, find whatever works and stick with it until something better comes along.

Acronis True Image isn't without faults.  From reading threads, only cloning works without glitches, rest of the features, file backups, partial file backups, differential backups, etc... are highly flawed.  I wrote an extensive letter to Acronis about this issue and they acknowledge and confirm there's work to be done...

Better release a package that has less features and they all work ( have been tested and QA ) than to have lots of features that don't work...

That is true. You can mount an image as a drive and inspect the contents. When restoring I've had issues where the recovery console was a deferent version of the OS then the image. You can also have issues from an hdd image to SSD too

Dan,zIZme,

Thanks for all info...

System Image Backup has never worked on any of my systems going back many years whether it's HDD ( IDE, SATA ) or SSD ( mSATA ).

I suspect feline1 may be interested in reaching out to Microsoft to get a solution; however, as for myself. I've already found solution that works 100% of time on all my systems regardless of OS or drive types.

Have Happy Christmas and Merry New Year...

P.S.

Even if MS acknowledged issue and had fix, user still has to go through the process of testing it, ie: create image backup then restoring it to make sure both backup and recovery ( restore ) works.

As I mentioned in several previous post, just because a backup was completed doesn't mean it's not corrupted and even if it's not corrupted, doesn't mean it can be restored...