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

Hi hp2159m, 

I don't have any disks bigger than 2TB.

The disks I used for the system are 512GB SSD's on SATA port 0, formatted with GPT partitions.

The system is a DELL XPS 8700 with 32GB RAM, it also has a 2TB HDD on SATA port 1 .

I have Windows Image Backup on both the 2TB internal HDD and also on external USB 3.0 disks.

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

B.T.W.

I found out that with Image Backups that I made after February 1st 2018, the restore works fine even when I need to reformat the disk.

The error 0x80042302 happens solid when trying to restore Image Backups that were made with Build 16299.192  or earlier build and it fails only when it needs to reformat the disk.

With Image Backups made with build 16299.214 I don't get any error restoring using either the recovery disk or the Installation media build 16299.15 or 16299.125.

It looks like build 16299.214 fixed the Image Backup, hopefully not just by luck. 

I hope this helps.

For the record, 'deprecated' means no longer being developed, which is why Microsoft recommends using a third-party solution.

I can't believe this thread is still going on, and with such convoluted 'solutions' being offered, when Macrium Reflect is rock-solid reliable and virtually effortless once you've learned how to use it. And Reflect isn't the only worthy third-party image solution. Moreover, third-party solutions can do things that System Image Builder can only dream of.

Maybe some of you folks enjoy making an engineering paper out of this. Me, I'm busy making and occasioinally restoring backups. Yes, restoring ... because every now and then one of the Bulldog's computer experiments has a rough landing.

Macrium worked for me too, but as most third party solutions, it requires a different bootable recovery media for each PC because the winPE bootable media they create is customized with drivers for the specific machine and it will not work on a different one.

With the same windows 10 installation media I could handle pretty much every machine I needed to recover and there is no need to create a separate bootable media.

The MS image restore just has a stupid bug when it needs to reformat the disk for a UEFI machine, Microsoft guys just need to fix what they broke.

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

Just confirming that I have the same issue.

Needed to send my Surface away for repair so did a full system image to external SSD & now can't restore it to the new unit.

Will watch with interest but I don't have a working laptop to contribute much!

Tested it here & restore worked - but i didn't clean the disk first.

You might want to run VSSADMIN LIST SHADOWS to see if there are any before the CLEAN.

Maybe it no longer does the bare metal type restore.

Anyhow I've switched to using the AOMEI free to be safe here, which makes a much smaller default image and runs much quicker like the old win system image did.   Newer 1709 system image is full size seemingly including unnecessary pagefile & hibernate.sys