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. :-(
I cannot restore any system image which was created in Windows 10 v1709 using Backup and Restore.
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.
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.
179 answers
Sort by: Oldest
-
Anonymous
2018-01-24T16:19:19+00:00 -
Anonymous
2018-01-24T16:20:06+00:00 They recommend it because they know the restoration FAILS!
-
Anonymous
2018-01-24T20:31:27+00:00 When Microsoft use the term deprecated they mean...
- The application is not regression tested - when they make changes to other parts of the OS, they don't check to see if is still works.
- The application is frozen - no development (which includes maintenance) will continue.
- The application is obsolete - Microsoft often use the terms deprecated and obsolete interchangeably.
-
Anonymous
2018-01-24T20:41:15+00:00 Hey> An update to your info- Yes Macrium Reflect freebie Macrium Reflect 7 - Free Edition works perfectly as I've just beta-tested it out the past two days upon my Windows 10 Enterprise E3 subscription & also w/ Windows 10 Enterprise LTSB 2016 under test setups!
Macrium Software Manufacturer: Paramount Software (UK) Ltd...
Results> Macrium Reflect works perfectly upon both Windows OS! Also do check-out my previous post w/in this thread w/ info on this very issue.
Best Regards,
Xen.
-
Anonymous
2018-01-24T20:44:23+00:00 Then Microsoft should notify all Windows users that certain features will be obsolete either by a message in Action Center or when the user tries to use the obsolete feature, Windows will warn them it will become obsolete or is obsolete. Then Microsoft should give instructions on a workaround to the obsolete feature.
Or have the newly obsolete feature removed entirely from the Windows OS during a Windows Update. That way the user will know something is wrong with the feature.
This way the User won't be shocked when the feature they have been using since Windows 7 or earlier doesn't work anymore at the wrong possible time.