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

Though I agree with many posters that MS, a company known for purchasing other software companies, forcefully integrating their solutions into their OS then claiming you cannot not have it and still run their OS, has clearly failed their community of users in regards to SIB. There 'nuf said.

As for the solution, please reference:

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

AOMEI Backupper (free for now) is a viable and stable replacement for Windows 10 1709 systems. I am a hardware production tech that creates a base image and then needs to redeploy that image to hundreds of client machines. When SIB failed in 1709 I needed to find a solution quickly and AOMEI, thus far, has satisfied all my needs. Also, I am no longer restricted by drive size. I can create a base image on a 1TB HDD and restore it to a 128GB SSD (as long as the overall data is smaller that the destination drive). It has a very easy to use GUI and you can do a full disk backup and restore from a local USB HDD or network location. It is everything SIB should have been. 

If you have created a vhdx using SIB and do not have a stable system to create a new BU using AOMEI, sorry this will not help you, but going fwd this is the best solution I have found.

I DO NOT represent AOMEI in anyway - I am just a tech that needed a solution like the rest of you and this has been a very good solution for me over the two months. There may be other 3rd party solutions out there that do a good job as well, but I cannot argue with stable and free.

YMMV

****************************

Remembering all the Daleks this 21st day of Dec 2017 -EXTERMINATE!!!!

Hi everyone

I have just finished recovering my refurbished surface from a windows image backup I took before returning it to Microsoft for a replacement.

So it was the worst case scenario ie backup from a device no longer available with a different ssd.

Definitely needed a workaround.

The problem was as underlined throughout the internet that restoring simply won't work trying to repartition a different disk. So to make a long story short what I did was

a) converted vhdx to vhd

b) used a third party software to create a bootable flash drive

c) restored the vhd to my "new" surface deleting everything in the process

d) created an efi partition on the recovered drive using a windows recovery drive to boot

e) made the new c: bootable

I know that this solution is far from perfect but honestly I can;t even imagine the pain of getting everything installed, updated, tweaked etc all over again. It sounds easy but it usually takes me at least a couple of weeks before bringing the system back to where I want it to be. So you can call it workaround or anything else but at least it works!!!

Unfortunately, I don't have a 1703 machine available to create the image on. 

The bigger issue for us is that we have scripts on scheduled tasks for backing up our MFG Windows machines that uses Windows System Image.  Now we're supposed to go buy a 3rd party app to get this done?  Not cool Microsoft.

I am in complete agreement that this is a business-critical function and should be resolved immediately.  The fact that it slipped past development is beyond me.  Especially since the issue is not vendor specific and is even occurring on Microsoft hardware.

Come on Microsoft - if you're not working on mobile and you're not fixing bugs...what are you doing?

Yeah, the workaround won't work for our company either.  I had wiped the Surface and distributed to a user, so the base OS is gone - no extra recovering.  

It's not a huge deal because I still have my data, but I now have to install all programs again as well as any settings that were changed.  For an IT administrator, it's a bit of a pain in the **** because there are much more important things to be done.