The issue is with a Win10 System Image
Macrium came into play after Nick Clean installed Win10 to get a running system. I suggested he use Macrium to back up the Clean install in case further attempts to restore the System Image failed - which they did fail.
I thought out load about trying to Restore the System Image onto the Clean Install - Nick tried that and it failed. The Macrium backup was restored
In post# 90,, John Frederick posted some links with similar issues. I followed one to find the resolution they used. Macrium might be able to correct what ever is wrong with the System Image. It's a bit of slight-of-hand really
John Fredrick said:
I've tested this only as far as backing up the VHDs inside a System Image - the Restore will be on-the-job training
- All VHDs in the System Image are mounted in File Explorer
- A Macrium backup is separately created for each of the mounted VHD.
Four VHDs in the System Image = four separate Macrium backups
- A Macrium Rescue disc (CD is fine) is required for the restore process - so that needs to be created.
- Boot to the Macrium Rescue disc
- Wipe the drive that will receive the Macrium restore
** This step was included in the original solution because the drive needed to be GPT for UEFI. It might not be necessary in this case.
- Restore the separate Macrium backups (I would start with the System Reserve partition, then the Windows partition)
I think that's all that needs to be restored - the D: partition looks to be the HP Recovery partition, based on the 15 GB size and drive letter. Nick said he doesn't need that any more. It's probably HP OEM Vista + HP bloatware.
- the final step is to use the Fix the MBR feature in Marcium
No, the image is on one of Nick's external drives. I think he mentioned which one, but that's a good question.
Typing that out and thinking about the partition schema, it occurred to me that the system was, and is still, configured with no System Reserve partition.
This is not the schema of a Clean Install - I don't have enough information on how the Macrium backups were created or how they were restored, So I can only guess that Something went wrong
... to paraphrase MS "error" message
Win10 had some install issues in the Tech Preview when SysRes was too small - MS made some changes to the install process a few times to accommodate the new SysRes requirements. I'm now wondering if those changes to the install process affect systems without SysRes partitions.
The error message "0x80070057: Parameter is incorrect" that Nick gets on many of the restore attempts indicates, to the best of my knowledge, corruption of the System Reserve.
I think we all agree that the current Disk, cable, port, BIOS fiasco needs to be resolved.
I'm leaning towards flashing BIOS with the 5.05 version - holding off until Nick responds to my question about the 5.08 version on the system now.
You believe the Active flag on the other drives manifest the jumping drive # - I offered to walk through it with Nick earlier. That's easy to test and can be done before anything else.
If removing the Active flag from all drives except C: (we previously removed the Active glag from HP_Partition, beacuse it was the first Active partition) resolves the disk # changing based on what drive is connected, then I think it's time to try the Macrium magic trick. Nick has restored the System Image so many times, so many ways, that I'm convinced something about the image isn't quite right - could be in the XML, could be Win10 restore - no restore process using Windows native tools (on the install media, from within Windows....) has completed successfully
The VHD can be mounted and the data can be accessed / copied. Nick has a copy of his VHD user profile and he also copied the entire contents to a folder outside of the VHD.
If the Macrium prestidigitation fails to yield results, the only thing left is a bigger hammer.
Manually create the partition scheme for Win10, manually extract the data in the VHD containing C: (Nick tried this, but on a running system, we'll have to boot to the install media, mount the VHD, and Xcopy the tree to the HDD), bootfix, bootsect, reagentc?
- all of that is prone to error - Windows is fairly good at self healing, but that might be too many paper cuts
This is more of a recap for fdegrove and for anyone trying to figure out what has been done and what I think are the next steps.
Frank, I appreciate your taking time to put another pair of eyes on this
- I'm going blind and my brain hurts
Nick, I appreciate your hanging in there with me as each side issue crops up.
- this should be a simple thing
This is a brain dump of information - there are no actionable items in this post