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.
fg2001 is correct. The problem is fixed (for the moment?) in 16299.214 (KB4058258).
I verified this on 2 systems on which an older 1709 Image could not be restored (error 0x80042302) but a new Image created after KB4058258 would be restored on a clean disk as it should.
Thanks, fg2001
...I found out that with Image Backups that I made after February 1st 2018, the restore works fine even when I need to reformat the disk.
The error 0x80042302 happens solid when trying to restore Image Backups that were made with Build 16299.192 or earlier build and it fails only when it needs to reformat the disk.
With Image Backups made with build 16299.214 I don't get any error restoring using either the recovery disk or the Installation media build 16299.15 or 16299.125.
It looks like build 16299.214 fixed the Image Backup, hopefully not just by luck.
I hope this helps.
What are interns for if they don't do all my donkey work!
Our test lab has 27 machines and all the images are on tape. They decided to test them all and a handful of other 'problem' machines. 33 in total
We had two machines that have never been able to complete the system image part of the backup. They now work under 16299.214.
All the machines restore under 16299.15 except three. Two of those restore under 16299.125 although I'm not sure if it's the restore program or the system it's sitting on. One of those two is the non-UEFI machine that wouldn't restore.
The third was the one I was using as a test machine and still won't restore any image so I use a FFU on it. I have hacked it about A LOT, but if I can capture an FFU and restore it, then SIB should be able to.
We have decided not to use SIB and will be using DISM under WinPE to FFU image the disks offline. No change that MS makes will affect this process.
Tomorrow the interns will be restoring all the images from tape that SIB cannot restore, converting them to WIM files, restoring them and then FFU imaging them. By the end of tomorrow I can forget about SIB.
fg2001 is correct. The problem is fixed (for the moment?) in 16299.214 (KB4058258).
I verified this on 2 systems on which an older 1709 Image could not be restored (error 0x80042302) but a new Image created after KB4058258 would be restored on a clean disk as it should.
Thanks, fg2001
Unfortunately I don't see anything mentioning an intentional fix in the release notes for KB4058258.
I hope they don't screw-up SIB again on the next build. :(
I guess we'll have to wait and see what happens next.
Hi there, while launching the powershell and executing the command you have mentioned i get the red lines error as shown in the below pic, could you please tell me what wrong i am doing. And just a few question, the external hard drive we need to use does it need to be clean because i have about 400 gb of data on that hard drive and no where to save it and that hard drive comes as D: partation for me because E: is dvd drive on my laptop. And when it comes to 12th step: do we need to enter the Format c: command first and press enter and then the rest or its all together and then press enter?
Regards,
Ryan
Hey there, can you please have a look at my last lost and i think may be you would be able to help me because i see in your previous post that you successfully resorted the SBI on your pc using fg2001's method.
Regards,
Ryan
