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 No comments

179 answers

Sort by: Most helpful
  1. Anonymous
    2018-01-28T19:25:10+00:00

    Two things:

    1. Deprecated does not mean removed. 
    2. In my case, I was able to create the system image from 1709 but not restore.

    The long-winded answers are pointless. Yes, MS recommends using a third party tool so that at some point in the future when the status goes from deprecated to removed users won't be left high and dry, but the tool  they provide to do the job currently  creates backups just fine. It fails to restore. Period. That's broken. Not deprecated.

    I agree, it is broken!

    It works fine with the old Legacy machines.

    It also works on a UEFI machines as long as you don't need to reformat the disk.

    If you try a restore to a different disk it needs to recreate the partitions and reformat, that is the phase when it fails.

    Using third party programs is not a solution as suggested by some in this thread.

    Microsoft needs to fix the bug.

    Another problem with third party programs is that you need to create a bootable disk or USB stick for every PC, because they just setup the drivers for the PC where you create the bootable media.

    The windows installation media works pretty much on every PC unless you need some new driver that is not yet included.

    I surely don't want to keep a separate bootable recovery media for every different PC I have to deal with :(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-25T04:28:12+00:00

    Microsoft has broken a critical safety safety feature relied upon by millions of non-technical users.  Users who do not have any exposure to or understanding of the official 'notice' and don't know what 'deprecated' means. 

    The unconscionable and criminal element is that the backup has not been disabled, just the restore.  Users will not find out about it until their data has been permanently and unrecoverably lost, with unlimited potential for material damages. 

    This is exactly like taking your car in for an oil change under warranty to the dealership, during which the seatbelt anchors are secretly replaced with 1# breakaway tabs.  There is some fine print on the website saying the seatbelts have been 'deprecated' and a 3rd party restraint system should be installed.

    I am shocked the Microsoft legal department hasn't stepped in and demanded that an emergency patch be issued for Windows backup.  At very least the backup feature should be riddled with pop-up warnings stating that the restore may not work post-1709.  This is the most egregious example of gross negligence I have ever seen in software (30 years in the business).  I know that EULAs are ironclad and could teach the dukes of hell a lesson, but this is so bad I doubt a well-informed jury would give Microsoft a pass.

    Seriously, Microsoft:  this is not only wrong and bad for business, this is going to cost you in court.  Warn people or disable the backup feature post 1709 NOW.

    I'd like to think so, but probably not since no one could cost justify the action, maybe a class action though.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-24T16:20:06+00:00

    They recommend it because they know the restoration FAILS!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-24T16:19:19+00:00

    Restoration of the OS to the point and time the OS was backed up should be a function of the OS. No ifs, ands, buts, or nuts, or excuses to sell 3rd party software. Its accurate to say XP can do something Win10 can not. Very, very, sad commentary. :-(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-01-24T15:36:19+00:00

    Two things:

    1. Deprecated does not mean removed. 
    2. In my case, I was able to create the system image from 1709 but not restore.

    The long-winded answers are pointless. Yes, MS recommends using a third party tool so that at some point in the future when the status goes from deprecated to removed users won't be left high and dry, but the tool  they provide to do the job currently  creates backups just fine. It fails to restore. Period. That's broken. Not deprecated.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments