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.
Because you have to wait for quite a sometime after executing the first and second powershell command. Its copying the sib to the external harddrive (sib.wim). And why are you trying to save sib.wim on c drive? It doesn't work that way. It has to be saved on an external hdd.
Well maybe I'll just wait over night and see what I have in the morning. It is pointed to a usb drive. I tried the c drive simply to see if the same thing occurred. It looks like the process is working based on the hard drive I/O where the image is stored at. It would be nice if PowerShell could give some sort of output that it is working, without having to look at task manager. Anyways, thanks for the tip wait longer.
Even it got me same as you for first 2 or 3 tries. You can do one thing to see if its copying the sib.wim to external hdd or not. After executing 1st and 2nd command wait for few minutes and then copy and paste the 3rd command (thats what i did for all) if that command it not executing it means copying is going on at the background. At first it wasn't sure why the 3rd command is not executing ( newbie ) so i copy pasted it 4 or 5 times and i think at one point poweshell got tired of me ...lol and then suddenly operation is on going came up on it. Then i know itc copying the files and you can then also open you wim folder in external hdd and check in its properties that size of it is increasing.
Well maybe I'll just wait over night and see what I have in the morning. It is pointed to a usb drive. I tried the c drive simply to see if the same thing occurred. It looks like the process is working based on the hard drive I/O where the image is stored at. It would be nice if PowerShell could give some sort of output that it is working, without having to look at task manager. Anyways, thanks for the tip wait longer.
From what I remember when I tried rwb1012 procedure there was a progress line showing on the green portion of the screen...
It did for me after someone. Did you try to reset your window after trying rwb1012 method? Because whenever i try to do that i get error that window cannot be reset. I think it may be because we only restored the c partation of sib using that method and not the recovery and efi partation from the previous SIB. So if there's a workaround this please let me know. Thanks
