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.
Ok, thank you RWB I appreciate all the great information! I created a VHD of a drive and it took hours, normally with Windows image it would take about 20 to 30 minutes max!
The Windows image was such a great tool just like it is sad that it is gone now. Windows Easy Transfer was amazing tool and now it is gone. It is weird how Microsoft gets rid of great tools that help techs!.
I know it was a bug, I spend 2 days trying to figure out what happened when trying to clone from a system image. Now I was trying to figure out how to scrap the system image that is no longer working after the fall update and update and find another way to clone computers without having to buy third party software.
Mainly we use cloning for swapping out machines. For example, we have a Surface Pro 4 battery start to expand and bulge the screen. We used to simple click on Windows backup and then create a image and then get the new Surface and then simple boot from a Windows boot disk and choose restore with image and then the new Surface Pro 4 is an exact clone and the user is back up and running exactly the way they were with all software and programs in a few hours.
So in your post it sounded like the VHD would do the same thing without having to mess with 3rd party software, is this true?
Installing Windows 10 usually creates 4 partitions (when using UEFI to boot). These are System, C:, EFI and recovery. The quickest way is to create these correctly is to install Windows 10 (20 minutes) and then replace C: with DISM.
DISM takes .wim files. You can convert a mounted disk image to WIM or you can capture a WIM directly by using DISM. The only reason we would start with a VHDX is that SIB created one.
e.g
Dism /Capture-Image /ImageFile:E:\c.wim /CaptureDir:C:\ /Name:Drive-C
You may also be able to capture a physical disk as a FFU (full flash utility) image with DISM. This would not require Windows 10 installation on the destination. You do need to have a good understanding of what you are doing.
Capturing the FFU with something like
Dism /Capture-FFU /ImageFile:E:\d0.ffu /CaptureDrive:\\.\PhysicalDrive0 /Name:Drive-0
Apply the FFU with something like
Dism /Apply-Ffu /ImageFile:E:\d0.ffu /ApplyDrive:\\.\PhysicalDrive0
Microsoft recommends that you use one of the following:-
Acronis https://www.acronis.com/
EaseUS https://www.easeus.com/
Paragon Software https://www.paragon-software.com/
Parted Magic https://partedmagic.com/
Yes, please!!!! what is DSIM? and how it this a true "bare metal" recovery solution if the image has to be applied to a logical drive that has already been formatted?
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.
I appear to be having the exact same issue, but my build is 16299 (10.0.16299)
