I cannot restore any system image which was created in Windows 10 v1709 using Backup and Restore.

Anonymous
2017-11-04T01:05:06+00:00

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.

https://social.technet.microsoft.com/Forums/windows/en-US/1f21b451-1431-414c-89e4-8010dfa5d239/win10-1709-system-image-restore-vss-error?forum=win10itprosetup

The culprit appears to be v1709. Something changed to prevent a successful restore.

Windows for home | Windows 10 | Windows update

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.

0 comments

179 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-11-04T21:42:20+00:00

    The procedure for creating and restoring a system image hasn't changed. By process of elimination, the culprit is obviously v1709. This process is based on the following:

    v1507 - clean drive, install fresh OS, updates, drivers, create image... Restore via repair disk successful.

    v1511 - clean drive, install fresh OS, updates, drivers, create image... Restore via repair disk successful.

    v1607 - clean drive, install fresh OS, updates, drivers, create image... Restore via repair disk successful.

    v1703 - clean drive, install fresh OS, updates, drivers, create image... Restore via repair disk successful.

    v1709 - clean drive, install fresh OS, updates, drivers, create image... Restore via repair disk unsuccessful. VSS error.

    And yes, I know about AOMEI. I also know about Macrium, Paragon, and CloneZilla. That's not a workaround in my situation. I created about 20 images for 20 different laptop/desktop models. I should be able to continue the process w/o using 3rd party software. System Image Backup (SIB) Solution is still supported in Windows 10.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2017-11-04T18:19:39+00:00

    Tested it here & restore worked - but i didn't clean the disk first.

    You might want to run VSSADMIN LIST SHADOWS to see if there are any before the CLEAN.

    Maybe it no longer does the bare metal type restore.

    Anyhow I've switched to using the AOMEI free to be safe here, which makes a much smaller default image and runs much quicker like the old win system image did.   Newer 1709 system image is full size seemingly including unnecessary pagefile & hibernate.sys

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-11-04T16:46:05+00:00

    Let me rephrase.

    This is a clean/fresh installation of 1709 on a wiped drive. I installed 1709, installed all Windows Updates, installed all drivers and then created a backup on a USB drive without any errors or warnings. There are no third-party programs in the image.

    To perform a clean boot is not applicable since there is no OS to boot into. Like I said before, the problem is in the 1709 build.

    Put it this way, there are 7 images on the USB drive. 3 from 1703 and 4 from 1709. All images created from 1703 can be restored successfully.  All images created from 1709 produce a VSS error.

    I am an IT admin at my company. I have been creating images since Windows XP (I used Norton Ghost back then). In Win7, Win8, Win8.1 and Win10 I have been using Backup and Restore, successfully. Nothing in my imaging process has changed. What changed is the version of Windows, 1709.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2017-11-04T02:31:17+00:00

    Hi Dan,

    This issue might occur due to a damage in system files or interruption while restoring. For us to determine if there are any third-party programs/apps that is causing the issue, we suggest that you perform a clean boot.

    We would appreciate it if you could get back to us and provide us your feedback.

    Was this answer helpful?

    0 comments