Forum Discussion
Windows 10 Pro v1709 Bug in Backup and Restore
My solutions are.
1. Stick with third party that are Good and Reliable.
2. Never rely on VSS, Always Backup from WinPE with the same 3rd Party's Recovery Tools.
The reason, One never knows if one has a faulty Image until One is Restoring it. I will look fine, Verify fine in all ways, but if VSS has jangled something one finds out at the worst possible time.
One never know when VSS is going to get a minor update or Revision. It is completely out of the Users/IT/Admins/DevOPS control. Is the resultant update good, stay tuned, if you used it for a Backup you will find out later.
Best Regards,
Crysta
- AnonymousFeb 03, 2018
Third party solutions are just a workaround, not a good solution, what about Microsoft fixing what they broke ?
The restore on 1709 works when you restore on the same disk without checking the reformat option, the error occurs only when you need to partition and reformat the disk, which is the case when you need to replace it because it failed.
The bug only occurs with the EFI systems, no problem with the legacy machines.
Also the EFI partition size on the real disk and on the Esp.vhdx do not match.
Microsoft Disk Management shows the partition size on the vhdx file is 4MB shorter than the one showing on the real disk. Not sure if that is the source of the bug, but this error 0x80042302 it needs to be fixed by Microsoft, restoring the WindowsImage is a basic function for recovery and needs to work.
- PhotM Phantom of the MobileFeb 04, 2018Copper Contributor
You certainly are entitled to your opinion But this is not the first time for MS.
In this area, I will not trust any MS solution Recovery/Restore/Refresh/Backup, I will only use 3rd Party solutions, I have been left out in the cold holding an empty bag way, way to many times over the years.
The exceptions are 'In Place Update' and 'WinPE CMD Tools' on USB/DVD made from the latest ADK, but even there MS has had a few problems. When that is changing over, I listen very closely to Mike Neihaus.
Now of course one needs a reliable 3rd party solution that is acceptable, for sure!
Best Regards,
Crysta
- AnonymousFeb 04, 2018
The problem is that there is no good third party solution, they all have different problems.
Also you have to create a bootable recovery disk (Most third parties use winPE anyway) which is customized for every different machine.
The Windows installation disk works on all the machines I'm dealing with, I don't need to keep a different recovery media for each computer.
I just want Microsoft to fix the **bleep** restore image. It used to work fine till they broke it on windows 10 and the EFI machines. It only fails when the disk needs to be partitioned and reformatted. The restore on the existing disk without reformat works fine. Also it works fine on all the old legacy Bios boxes, the bug is with the EFI FAT32 partitions.