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

There are many reports about the windows 10 1709 Image Restore  to a new disk bug. 

Perhaps not many when you posted your reply.

The error 0x80042302 happens on EFI systems on restore when the reformat and recreate partitions is checked.

The restore only works if you don't need to reformat the drive

The restore fails to recreate and reformat the 4 partitions required on the EFI systems.

This is an example of the 4 partitions created during installation on a 512GB SSD drive:

DISKPART> list partition

Partition ###  Type              Size     Offset

  -------------  ----------------  -------  -------

  Partition 1    Recovery           499 MB  1024 KB

  Partition 2    System             100 MB   500 MB

  Partition 3    Reserved            16 MB   600 MB

  Partition 4    Primary            476 GB    616 MB

The restore program should recreate the same partition from the image, but it fails with the error 0x80042302, it looks like the problem is with the EFI partition that looks 4MB shorter in the vhdx file. The issue could be also on the 16MB Reserved GPT partition.

This is a bug very easy to recreate, not sure why Microsoft doesn't have a fix yet.

Perhaps nobody is working on it ?

You need to escalate this basic bug !

This is one of the most helpful replies I have come across; however, due to MS unprofessional handling of the matter it does not solve the problem. Clearly MS is behind the curve in regards to EFI hardware. It like before the Win XP days. :-(

I think I figured out the fullpathofvhdxindoublequotes  , but there is more than one .vhdx files in the image backup folder, I figured it was the biggest one.

Also on the step to Format C:   perhaps /Q  would save some time ? or do I need to clean up the disk ?I'm now waiting for the disk to complete the format and then do the last step...

I finally got to last step and my image has been restored on the new disk (SSD)

Your procedure worked for me.

One note on Step 6 the external drive letter may be different when I just installed windows It showed as J: and when I restarted in recovery mode it showed as E:

I think a check is needed to verify where the CapturedWIM is.

Thanks for the workaround procedure.

Now Microsoft still needs to fix the Restore Image program.

Third party utilities are just another risky bet.

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.