System Image Restore Failed 0x80070057

Hi guys,

I have 2 SSDs in RAID 0 with Windows 10 Pro 64-bit installed. I tried to make a system image using the windows backup utility, then disable the RAID array, reformat, and restore to one of the SSDs. At this point I realized I needed to shrink the partition first. I have the image on a 1 TB hard disk in the computer.

However, I rebuilt the array and now I can't restore my image, I get an error that the parameter is incorrect (0x80070057). This happens right at the very end of the restore. I'm using a USB stick with the windows recovery environment on it, created with the backup utility in windows. I tried the method of pulling out the USB stick once the recovery environment is loaded. I also tried running diskpart clean, same issue.

Any ideas?

Thanks

- - - Updated - - -

Well, I don't know what the problem was but I got Windows running.
Essentially after rebuilding my RAID array, running the system image restore, and getting the error, I ran Startup Repair and after that it just booted right up. Chrome even remembered my tabs.
I'm not sure I'd call it a solution, but if your image restore fails at the very end running startup repair may help.

I did also get Macrium Reflect, hoping it could read the image created with Windows backup but that didn't work either. From now on I'll be using that to make backups and images.

If anyone knows of a third party tool that can real and restore images made with Windows backup, I'd still be interested to know. Or if anyone knows the real cause of this issue.

Thanks!

Essentially after rebuilding my RAID array, running the system image restore, and getting the error, I ran Startup Repair and after that it just booted right up.

Did you try booting into it before running startup repair?

Yes, I got a message that no OS was found.

If anyone knows of a third party tool that can real and restore images made with Windows backup, I'd still be interested to know. Or if anyone knows the real cause of this issue.

Because startup repair fixed it, that seems to indicate the issue was due to switching from raid to single ssd - or whatever you meant by this

At this point I realized I needed to shrink the partition first.

One of the advantages of .vhd(x) format is that other programs can access the images. One way is to mount the vhd(x) via diskmgmt/diskpart and then clone to the target using any number of 3rd party tools, or even xcopy. Some programs will mount vhd(x) internally, e.g. diskgenius, if you prefer that.

storageman said:

First off the Windows (7) backup that your using has been depreciated by Microsoft a couple of years ago. Which means its not supported and there are NO new enhancements to support newer configurations. Your lucky you were able to get your system back.

I would suggest you look at "Macrium Reflect" as a backup imaging system. Super reliable and supported even with the free version to Windows latest system version.

Have a great afternoon !

Yes I saw Macrium mentioned a lot on this forum, I already have it downloaded. It will be my go-to from now on, this isn't the first time Windows backup has screwed me over lol.

SIW2 said:

Because startup repair fixed it, that seems to indicate the issue was due to switching from raid to single ssd - or whatever you meant by this


One of the advantages of .vhd(x) format is that other programs can access the images. One way is to mount the vhd(x) via diskmgmt/diskpart and then clone to the target using any number of 3rd party tools, or even xcopy. Some programs will mount vhd(x) internally, e.g. diskgenius, if you prefer that.

Yes I would agree. Thanks for the info! I'm going to try again to separate my RAID disks and use Macrium this time.