0x80070001 error during Windows 7 system image.

Topic

New Reply

Hardware: Dell Inspiron 1545 laptop, includes single HDD 320 GB
OS: Windows 7 Home Premium SP1 64 bit, all MS updates applied.
External HDD: Argosy HD260T 120 GB, USB 2.0

Symptoms: Quick format of the external HDD (NTFS) followed by system image creation using the CONTROL PANEL>BACKUP & RESTORE facility within Windows. Approx 64 GB space is required. The process runs for about 20 minutes and approx 60% completed on the progress bar, when the progress bar turns red and the warning ‘Backup failed, incorrect function (0x80070001)’ appears.

Tried the following (some are suggestions from other forums):
Rebooting laptop several times.
Running CHKDSK on both internal and external HDD.
Running CCleaner cleaner and registry repair.
Scan using Avast antivirus 2014, and Malwarebytes, both with latest definitions.
From CMD prompt, run DIR /AL /S, which gave 95 ‘junctions’. Each junction was checked in Properties of Windows Explorer to ensure it was a File Folder and not a Mounted Volume.
Using DISKMGMT.MSC, make the C: OS partition active (there are 3 partitions – 39 MB OEM, 14 GB repair E:, remainder OS C: ). This caused a BOOTMGR MISSING error on next boot up, which I could only fix by booting from a system repair DVD and following instructions to repair the OS. I think this is when the Repair E: partition was created.
Roll back to earliest System Restore Point available (only a few days old).

Previous system image creations using the same hardware and procedure have been successful.

The above has taken several hours of effort (I’m not a whizz at IT!) so any help would be much appreciated thank you

Reply | Quote

Replies

Have you recently run a chkdsk on your drive?

Reply | Quote

Yes – see above plz.

Reply | Quote

Yes – see above plz.

Of course, please accept my apologies.

I think you have pretty much covered all the usual recommendations. I fear I can’t add much more to that.
Sorry if you don’t want to read this, but maybe it’s time to try one of the free alternatives – Macrium Reflect Free or EaseUS Todo Backup?

Reply | Quote

No problem

Thank you – I haven’t heard of those, but will investigate.

Reply | Quote

Both alternatives are used by many Lounge members, Macrium probably being the most used, according to my own heuristics. I just included free apps, but if you are interested and have a look in the Maintenance forum, there are recommendations for paid apps too.

Reply | Quote

I think Macrium looks a little more user friendly.

Please excuse what is perhaps a daft question, but from what do you boot if you need to restore a Macrium system image? With Windows 7 I created a system repair DVD as soon as I got the laptop.

Reply | Quote

Macrium allows you to create its own boot disk, so you boot from it and restore the image. It’s similar to the way the system repair disc allows you to restore an image made with the Windows native imaging tool. If you install Macrium, creating boot media should be one of your first tasks.

Reply | Quote

Thank you ruirib, that makes sense.

Reply | Quote

You are welcome :).

Reply | Quote

Be sure to create a Boot Disk with whatever Imaging app you choose, and with whatever version of that Imaging app you use. For example I have had Acronis True Image 2010, 2011 and now 2013. I have created a Boot Disk for all 3 versions. Imaging is too important to chance it not working when you need it.

Reply | Quote

That sounds like good advice Medico, thank you.

Reply | Quote

Thank you to all who replied – the fault is fixed!

I stumbled across a partially-related topic in another forum that mentioned running the CHKDSK routine with both options ticked. I had to select both ‘Automatically fix file system errors’ and ‘Scan for and attempt recovery of bad sectors’, then let CHKDSK run at the next boot-up. It took a long time, but did find and correct some bad clusters. The system image backup then ran without a problem.

Hurray!

Reply | Quote

I thought you had run it with /R, chkdsk /R, which should accomplish the same result as what you just stated. I actually always execute chkdsk like that. Anyway, thx for posting your success and well done for sorting it.

Reply | Quote

It was obviously trying to write to a bad spot on the disk. chkdsk marked the spot as unavailable if it couldn’t fix it, and that’s why you were able to do the image after running chkdsk.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

ruirib – sorry, I should have been clearer in my original post. I ran the CHKDSK from Computer > OS C: > Properties > Tools. I’m not really au fait with the CMD prompt alternatives – maybe it’s something I should try to learn! Thank you once again.

mrjimphelps – yes, that makes sense, thank you.

Reply | Quote

ruirib – sorry, I should have been clearer in my original post. I ran the CHKDSK from Computer > OS C: > Properties > Tools. I’m not really au fait with the CMD prompt alternatives – maybe it’s something I should try to learn! Thank you once again.

mrjimphelps – yes, that makes sense, thank you.

Funny, I always run it from the command prompt :).

Reply | Quote