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.
Here's the easiest solution. Stop using Backup and Restore or History. Start using AOMIE Backupper. MUCH faster (at least 2x), and about a 30% smaller footprint. Best of all, it's free. Read this quick, before it "disappears". I've tried it several times (testing) and have yet to have a problem. Read this quick, before it "disappears".
Though I agree with many posters that MS, a company known for purchasing other software companies, forcefully integrating their solutions into their OS then claiming you cannot not have it and still run their OS, has clearly failed their community of users in regards to SIB. There 'nuf said.
As for the solution, please reference:
AOMEI Backupper (free for now) is a viable and stable replacement for Windows 10 1709 systems. I am a hardware production tech that creates a base image and then needs to redeploy that image to hundreds of client machines. When SIB failed in 1709 I needed to find a solution quickly and AOMEI, thus far, has satisfied all my needs. Also, I am no longer restricted by drive size. I can create a base image on a 1TB HDD and restore it to a 128GB SSD (as long as the overall data is smaller that the destination drive). It has a very easy to use GUI and you can do a full disk backup and restore from a local USB HDD or network location. It is everything SIB should have been.
If you have created a vhdx using SIB and do not have a stable system to create a new BU using AOMEI, sorry this will not help you, but going fwd this is the best solution I have found.
I DO NOT represent AOMEI in anyway - I am just a tech that needed a solution like the rest of you and this has been a very good solution for me over the two months. There may be other 3rd party solutions out there that do a good job as well, but I cannot argue with stable and free.
YMMV
****************************
Remembering all the Daleks this 21st day of Dec 2017 -EXTERMINATE!!!!
I appear to be having the exact same issue, but my build is 16299 (10.0.16299)
Here's the easiest solution. Stop using Backup and Restore or History. Start using AOMIE Backupper. MUCH faster (at least 2x), and about a 30% smaller footprint. Best of all, it's free. Read this quick, before it "disappears". I've tried it several times (testing) and have yet to have a problem. Read this quick, before it "disappears".
AOMIE Backupper is not working. After preforming a AOMIE system backup and restore the computer is telling me there is no device capable of booting.
There are many people having same problem and you try to joke.
