Windows 10: Attempt to create a system image fails

I am new to Windows 10. I just tried, for the first time, to use the legacy "Backup and Restore (Windows 7)" to create a system image on an external hard drive. The creation failed with an error:

The backup failed. A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information (0x807800A1). Additional information: The writer experienced a transient error. If the backup process is retried, the error may not reoccur (0x800423F3).
As suggested, I retried, but the operation failed again.

I used the Event viewer to check the SPP and VSS events:

SPP: Writer ASR Writer experienced some error during snapshot creation.

VSS: Volume Shadow Copy Service error: An invalid XML document was returned from writer {89374701-e2cf-4855-bd6e-6992c14fc30f}.

VSS: Fail to parse XML file. Reason An invalid character was found in text content.
There was an old (Windows 7) system image on the hard drive. In case Windows 10 was having trouble reading it, I deleted it. But I the operation still failed.

:)

 

Create a system image fails

I have Windows 10 Home 64-bit - running on an ASUS machine with 16 GB of RAM.

I can successfully create a "restore point" (System - System Protection - Create)



When I attempt to create a system image (Backup and Restore - Create a System Image) on an external USB drive, it fails. I get the following message:

"Create a system image

The backup failed.

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

Additional Information:

Incorrect function (0x80070001)"

I have successfully done this in the past with no problems.

How do I fix this?

 

Creating a System Image backup - keeps looping

Hi,

Thank you for giving us an opportunity to assist you with the query.

I understand the inconvenience caused, now that you have me with you let me take care of this.

The system image is exactly like the mirrored copy of the Operating System which contains the configuration of the Operating System. When you create backup system image your windows 10 comes back to the same position at when the image was created earlier.

As an initial step, I suggest you to make sure that the services required for backup to run successfully is enabled. Refer to these steps:

• 
  Press Windows + R
  keys, type services.msc and press Enter.
  
• 
  In the services window, locate the services
  File history service and the Volume shadow copy service and check if they are running.
  
• 
  If they are not running, right-click and select
  Start to manually start the service.
  
• 
  Check if you are able to create a backup now.
  

Step 1: I suggest you to follow the steps from the below article created by

Andre Da Costa and check if it helps.

How to: Create a system image in Windows 10

How to: Create a system image in Windows 10

Step 2: If the issue still persists, I suggest you to boot the computer in a clean boot state and then check.

Booting the computer in a clean boot state can reduce software conflicts and help identify the root cause of the issue. You can refer to this article for more information:

http://support.microsoft.com/kb/929135

Note: After troubleshooting, reset the computer to start as usual. Refer to the step
How to set the computer to start as usual after clean boot troubleshooting under more information.

Hope it helps.

Let us know the status, we are glad to assist you further.

 

"Create a system image" "The backup failed"

Windows 10 Pro Build 1809 fully updated

Trying to create a system image.

Steps followed:

File History - System Image Backup

New windows opens - "Backup and Restore (Windows 7)"

Click "Create a system image"

Browse to external USB drive

Process commences then this happens:





2 different external USB drives fail with same issue

From the Event Log:...













Event Details is less than helpful....





I create a system image once a month

Worked correctly every month last 3 years

Failed in December, tried a few times in last few weeks

I suspect issue started with 1809 update

Suggestions please........