This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I cannot restore any system image which was created in Windows 10 v1709 using Backup and Restore. I receive the following error:
“The system image restore failed.
Error details: A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information.
(0x80042302)”
This is a fresh Windows 10 v1709 installation. The repair disk was created using Backup and Restore. The image resides on an external USB hard drive which contains other images. I can restore any Windows 10 v1703 image using the repair disk. I cannot restore any Windows 10 v1709 image using the repair disk.
As a first test, I installed Windows 10 v1709 on a new HP EliteBook 840 G4 laptop (before installation I wiped its hard drive). I also used a different external USB hard drive to back up the image successfully. I checked Event Viewer and found no errors or warnings relating to Windows Backup. After a successful backup, I wiped that laptop using the “clean” command and tried to restore the same image I created earlier. It failed with the VSS error referenced above.
As a second test, I installed Windows 10 v1703 on the same HP EliteBook 840 G4 laptop (before installation I wiped its hard drive). I used the same external USB hard drive to back up the image successfully. I checked Event Viewer and found no errors or warnings relating to Windows Backup. After a successful backup, I wiped that laptop using the “clean” command and tried to restore the same image I created earlier. The restore was successful.
Unsuccessfully, I tried to restore an image using repair disks I created in Windows 10 v1703, v1607 and v1511.
I am aware System Image Backup (SIB) Solution is deprecated (not removed) in v1709. I searched online for other users with the same issue and came across the following post on TechNet forum.
The culprit appears to be v1709. Something changed to prevent a successful restore.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I see from your picture that the current Recovery partition on disk 0 is 450MB, while the size of the recovery partition on the VHDX file is 499MB.
You will have to see if the data from the old recovery partition will fit on the smaller current partition.
Maybe you can check the actual occupied and free space on both.
I'm not sure if it has been reported on this thread yet, but Windows/System Image Backup/Restore appears to be working for UEFI/GPT systems again.
I just successfully restored my system running 16299.248.
On my PC, it did sit on "Preparing to restore your disk..." for a good 5 minutes or so, but then it did successfully restore after that pause.
Glad it's working, and I also hope it stays working.
I'm not sure if it has been reported on this thread yet, but Windows/System Image Backup/Restore appears to be working for UEFI/GPT systems again.
I just successfully restored my system running 16299.248.
On my PC, it did sit on "Preparing to restore your disk..." for a good 5 minutes or so, but then it did successfully restore after that pause.
Glad it's working, and I also hope it stays working.
Yes, it has been reported, it was fixed on build 16299.214 and 16299.248.
I just hope they don't break it again.
The problem is that if you only have an image created with 16299.192 and earlier it cannot be restored without using some workaround method.
Hi Travis,
For us to isolate and provide you an accurate resolution regarding your concern with 1709, we would like to know the following:
- What is the exact issue are you experiencing with 1709?
- Are you getting any error messages? If yes, what is the exact error message?
- To make sure that we have not missed on anything, what troubleshooting steps have you done so far?
We look forward to your response.
Can you please stop asking stupid questions like an idiot and read all the comments and questions people have posted here... the user who posted this question has clearly mentioned the error message and the error code....
Give us answers for your faults and bugs without asking damn stupid questions...
We have paid for all these and when we lost everything I will sue MS for the loss of my data if I cannot recover my data back...
Hi Travis,
For us to isolate and provide you an accurate resolution regarding your concern with 1709, we would like to know the following:
- What is the exact issue are you experiencing with 1709?
- Are you getting any error messages? If yes, what is the exact error message?
- To make sure that we have not missed on anything, what troubleshooting steps have you done so far?
We look forward to your response.
Can you please stop asking stupid questions like an idiot and read all the comments and questions people have posted here... the user who posted this question has clearly mentioned the error message and the error code....
Give us answers for your faults and bugs without asking damn stupid questions...
We have paid for all these and when we lost everything I will sue MS for the loss of my data if I cannot recover my data back...
Your post was back on Nov 8 2017, we are now on Feb 28th 2018. Many changes since then.
The image backup/restore has been fixed with build 16299.214 and 16299.248.
Unfortunately if your backup was taken with build 16299.192 or earlier you will not be able to restore unless you use some workaround method which you may find on this thread.
If you look at the beginning of page 5 in this thread there is a description of a workaround method to restore your disk C from a image backup .vhdx file.
I had your problem and I followed the suggested procedure by rwb1012, it worked for me.
Since then I updated my windows 10 pro 1709 to build 16299.248 and now the image backup/restore works fine.
MS never described what was changed in those 2 updates that made the SIB work again. I just hope that Microsoft does not break it once more on the next build.
