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

Then Microsoft should notify all Windows users that certain features will be obsolete ...

  

You mean like this: Features that are removed or deprecated in Windows 10 Fall Creators Update

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.

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.

Then Microsoft should notify all Windows users that certain features will be obsolete ...

  

You mean like this: Features that are removed or deprecated in Windows 10 Fall Creators Update

I never would have found that update article unless I knew about it. I learned about that particular Update from MS from reading the previous comments on this Forum. I consider myself to be quite computer literate with a technical background. Imagine the vast majority of people are aren't. They would have no way of knowing SIB restore has be disabled purposely by Microsoft until they try to restore their System Image and fails like I did. All Microsoft needed to do was make a POP-UP window show when the people are going to use System Image Backup saying it is obsolete and System Image can't be restored. To use a 3rd Party software to replace SIB. How difficult is that to do. That can easily be incorporated in a Windows Update.

I first learned of my problems with SIB when trying to restore my System Image yesterday and kept failing. As mentioned before, I was able to find a workaround to get it to restore by booting a Windows 10 Installation from one of my other internal Hard Drive that I use as a backup for this reason.

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 am totally in agreement. Vast majority of computer users are not technical or computer literate  enough to be able to troubleshoot why a feature is failing. 

But as Allen Hall mentioned, Who would go to court to sue MS because a Windows Feature was disabled without proper notification. Unless as mentioned, as a Class Action suit, that can show millions of dollars of damaged due to the fact users weren't able to restore their System Image.