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

Hi there, while launching the powershell and executing the command you have mentioned i get the red lines error as shown in the below pic, could you please tell me what wrong i am doing. And just a few question, the external hard drive we need to use does it need to be clean because i have about 400 gb of data on that hard drive and no where to save it and that hard drive comes as D: partation for me because E: is dvd drive on my laptop. And when it comes to 12th step:  do we need to enter the Format c: command first and press enter and then the rest or its all together and then press enter? 

Regards,

Ryan

fg2001 is correct.  The problem is fixed (for the moment?) in 16299.214 (KB4058258). 

I verified this on 2 systems on which an older 1709 Image could not be restored (error 0x80042302) but a new Image created after KB4058258 would be restored on a clean disk as it should.

Thanks, fg2001

Unfortunately I don't see anything mentioning an intentional fix in the release notes for KB4058258.

I hope they don't screw-up SIB again on the next build. :(

I guess we'll have to wait and see what happens next.

https://support.microsoft.com/en-us/help/4058258

...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.

What are interns for if they don't do all my donkey work!

Our test lab has 27 machines and all the images are on tape. They decided to test them all and a handful of other 'problem' machines. 33 in total

We had two machines that have never been able to complete the system image part of the backup. They now work under 16299.214.

All the machines restore under 16299.15 except three. Two of those restore under 16299.125 although I'm not sure if it's the restore program or the system it's sitting on. One of those two is the non-UEFI machine that wouldn't restore.

The third was the one I was using as a test machine and still won't restore any image so I use a FFU on it. I have hacked it about A LOT, but if I can capture an FFU and restore it, then SIB should be able to.

We have decided not to use SIB and will be using DISM under WinPE to FFU image the disks offline. No change that MS makes will affect this process.

Tomorrow the interns will be restoring all the images from tape that SIB cannot restore, converting them to WIM files, restoring them and then FFU imaging them. By the end of tomorrow I can forget about SIB.

fg2001 is correct.  The problem is fixed (for the moment?) in 16299.214 (KB4058258). 

I verified this on 2 systems on which an older 1709 Image could not be restored (error 0x80042302) but a new Image created after KB4058258 would be restored on a clean disk as it should.

Thanks, fg2001

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.