Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Cannot create system image: Error 0x80780166/0x80070001


  • Please log in to reply
26 replies to this topic

#1 TechlessOS_3211

TechlessOS_3211

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 29 July 2017 - 11:04 AM

Hi all,
 
I heard about the Windows 10 Creator's update and the fact it's going to deployed to everyone's computers whether we like it or not. After my awful experience with the Anniversary update...I'm not too keen on the idea. Seems like my Windows 10 Pro doesn't have the option to defer feature updates, so I decided to try and create a system image. And failed, multiple times.
 
backup_error.png
 
The error message is always the same:

The backup failed.

Windows Backup encountered an error when writing data to the backup target. (0x80780166)

Additional information:
Incorrect function. (0x80070001)

^for those of you who can't see the image/are on mobile.

 

I have done quite a bit of searching on the error and it seems like a lot of people have had this problem but no solution other than resetting your PC, and Microsoft hasn't really offered much help with it either.

 

I had a similar problem with a system image on Windows 7 before I decided to update, which was solved using Tweaking.com.

So I ran Tweaking.com with the same settings as last time, but I still got this error. Or at least I think it was the same settings as last time...it was whatever was saved from the previous run from the looks of it.

 

For reference, the external disk I'm backing up to looks to be in good health (ran a Chkdsk and there were no bad blocks or errors or anything), and has sufficient space. It is a 1TB Seagate Backup+ for Mac, which I partitioned into 566Gb HFS+, 364Gb NTFS. I had two existing system images on the disk, and had to erase one to ensure I had enough space, so I haven't had this issue with the disk before and I have been able to save system images to it in the past.

 

The version of Windows 10 Pro I'm using is the original build, Build 1511, on a Boot Camped Mac, if that makes any difference.

 

Any help would be much appreciated!


Edited by TechlessOS_3211, 29 July 2017 - 11:35 AM.


BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:36 PM

Posted 29 July 2017 - 12:04 PM

You could Macrium Reflect to clone the drive.  You can find a tutorial for this program here.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 29 July 2017 - 12:41 PM

That makes a good workaround, but it's no solution--I'd like to solve these errors if possible.

#4 xrobwx

xrobwx

  • Members
  • 197 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Panama City Beach, FL USA
  • Local time:07:36 PM

Posted 29 July 2017 - 12:41 PM

You could Macrium Reflect to clone the drive.  You can find a tutorial for this program here.

I have and am using this on multiple systems for years and even in a server environment with RAID 1. It works great and very reliable, easy too.


7581204627.png


#5 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 29 July 2017 - 12:43 PM

I'm not really looking for a third party program though. I want to fix the problem :/

#6 xrobwx

xrobwx

  • Members
  • 197 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Panama City Beach, FL USA
  • Local time:07:36 PM

Posted 29 July 2017 - 12:48 PM

have you come across this in your researches?  http://www.instant-registry-fixes.org/how-to-fix-incorrect-funtion-0x80070001-error/


7581204627.png


#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:36 PM

Posted 29 July 2017 - 12:50 PM

Problems like this are what  makes people switch to a program which is more dependable and easier to use.  But if this is too complicated for you I can understand wishing to stay with the Windows app.

 

Let's see if running the system file checker can clean this up.

 

 Please run System File Checker.

The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.

Important:  There will be a short message at the end of the scan informing you of the results.  If you receive the message "no integrity violations were found" you don't need to do anything else, no corrupt files were found.  You should watch the scan to see the results at the end of the scan.

This needs to be run using an Administrator account.  

You should not do anything else with the computer while this scan is running.  Do not stop the scan as this can damage Windows files.

You will need to open the Command Prompt to run the sfc /scannow.  The easiest way to do this is to press the Windows key and the X key.   A menu will open with the option Command Prompt (Admin), click on this.  This will open the Command Prompt.

If you are prompted for an administrator password or for a confirmation, enter the password, or click Allow.

Copy and paste the command below in the Command Prompt, then press Enter.

sfc /scannow

This scan will take a while to run, please do not abort the scan as this can result in damage to the operating system.

If integrity issues are found in the scan please post the CBS log using the instructions below.

To find sfc /scannow log click/tap on File Explorer, select the drive which Windows is installed on (this usually is the C: drive), click/tap on Windows, then Logs, then CBS.  If there are more than one log you can identify the log you want by the date and time it was run.  

Copy and paste the log at the host website I've suggested below.

This log usually is very large, for this reason you should use a host website like Dropbox to post the log.  You can start a free 30 day trial.  Once you have loaded the log at Dropbox post a link to the website.
 


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:36 PM

Posted 29 July 2017 - 12:55 PM

By the way, if switching to a third party program allows you to create a clone of the operating system it is a solution. :thumbup2:


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#9 QQQQ

QQQQ

  • Members
  • 387 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:36 PM

Posted 29 July 2017 - 01:21 PM

https://www.bleepingcomputer.com/forums/t/515779/0x80070001-error-during-windows-7-system-image-backup/

 

Worth a shot, try running chkdsk with all options checked on your C drive.



#10 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 29 July 2017 - 05:15 PM

Problems like this are what  makes people switch to a program which is more dependable and easier to use.  But if this is too complicated for you I can understand wishing to stay with the Windows app.

 

Let's see if running the system file checker can clean this up.

 

 Please run System File Checker.

The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.

Important:  There will be a short message at the end of the scan informing you of the results.  If you receive the message "no integrity violations were found" you don't need to do anything else, no corrupt files were found.  You should watch the scan to see the results at the end of the scan.

This needs to be run using an Administrator account.  

You should not do anything else with the computer while this scan is running.  Do not stop the scan as this can damage Windows files.

You will need to open the Command Prompt to run the sfc /scannow.  The easiest way to do this is to press the Windows key and the X key.   A menu will open with the option Command Prompt (Admin), click on this.  This will open the Command Prompt.

If you are prompted for an administrator password or for a confirmation, enter the password, or click Allow.

Copy and paste the command below in the Command Prompt, then press Enter.

sfc /scannow

This scan will take a while to run, please do not abort the scan as this can result in damage to the operating system.

If integrity issues are found in the scan please post the CBS log using the instructions below.

To find sfc /scannow log click/tap on File Explorer, select the drive which Windows is installed on (this usually is the C: drive), click/tap on Windows, then Logs, then CBS.  If there are more than one log you can identify the log you want by the date and time it was run.  

Copy and paste the log at the host website I've suggested below.

This log usually is very large, for this reason you should use a host website like Dropbox to post the log.  You can start a free 30 day trial.  Once you have loaded the log at Dropbox post a link to the website.
 

 

Alrighty, there were apparently some errors. Here's the log link.

scannow.png[/url]
 

https://www.bleepingcomputer.com/forums/t/515779/0x80070001-error-during-windows-7-system-image-backup/

 

Worth a shot, try running chkdsk with all options checked on your C drive.

Definitely worth a shot; I'll try it.



#11 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:36 PM

Posted 30 July 2017 - 08:27 AM

To repair file corruption found in the sfc /scannow please do the following.

Press the Windows key  and the X key to open the Windows Mobility Center menu.
 
In the menu select Command Prompt (Admin)

Copy and paste the command below in the Command Prompt, then press Enter.
 
 dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.


Edited by dc3, 30 July 2017 - 08:31 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#12 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 30 July 2017 - 08:43 PM

To repair file corruption found in the sfc /scannow please do the following.

Press the Windows key  and the X key to open the Windows Mobility Center menu.
 
In the menu select Command Prompt (Admin)

Copy and paste the command below in the Command Prompt, then press Enter.
 
 dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.

 
Okay, did that. 
I also ran the CHKDSK and it seems it did fix a few things:

Spoiler

Then, I tried running backup again. The system image got a lot further--about 82% this time (before it was erroring out at 67%-ish).
Looking at more information, looks like 0x80070001 is gone, but 0x80780166 is still causing a problem.

In Event viewer:

The backup was not successful. The error is: Windows Backup encountered an error when writing data to the backup target. (0x80780166).

Looking at event logs, it's always CAPI2 that errors out alongside it. Dunno if that rings any bells?

Spoiler

Edited by TechlessOS_3211, 30 July 2017 - 09:05 PM.


#13 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:03:36 AM

Posted 30 July 2017 - 11:59 PM

You should also execute CHKDSK command on a backup drive.


Posted Image


#14 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 31 July 2017 - 02:55 PM

You should also execute CHKDSK command on a backup drive.

Oh yeah, I didn't mention it before, but I did run it on the backup drive as well, before the main drive. 

Spoiler

Edited by TechlessOS_3211, 31 July 2017 - 09:02 PM.


#15 TechlessOS_3211

TechlessOS_3211
  • Topic Starter

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Texas
  • Local time:07:36 PM

Posted 03 August 2017 - 02:16 PM

bump






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users