ges_ez_BCD
Member
Friends of Easy_BCD,
Thanks for the great tool and community. My goal is to transfer my Windows 10 System to a new SSD on the same rig. I installed Easy_BCD on the old drive.
I have read that the new Windows 10 April/May/June 2018 upgrade may require a larger System Reserved partition to install, so that new partition size is increased to 3.6 Gigabytes (~10 times the old standard) on the new drive. In addition, the new SSD has the Windows partition (~830 Gigabytes) and the two small System Recovery partitions that appear on the old drive.
Using HD_Clone, I cloned each old partition onto the new drive's respective partition. There is automatic adjustment at the end of the clone that seems to be geared to resolving conflicts in device ID (?) etc.
The system boots onto the old drive (which has BIOS priority over the new drive) and I can see all drives and partitions in Computer Management/Storage utility. Note that the very original drive is still on the system, we'll call it the "data drive"; but it still retains its original System Reserved partition.
Booting to the old drive and using Easy_BCD, I added the new drive's installation partition to the boot menu, retaining the old drive's installation partition as default. System then goes through boot menu and boots fine to old drive as default.
When I reboot and select the new drive as boot drive from the boot menu, the system does start, but acts very flaky after giving me a pop-up error window:"sihost.exe - Unknown Hard Error" message and stumbles on for a while before I stop it. The disk activity seems to be on the new drive in this case (not the old drive), but a strange disk naming convention is sometimes used that makes reference to the original System Reserved partition on the data drive as a prefix to the partitions being referenced.
I am hopeful that Changing the Boot Partition or some other approach will allow me to straighten out this condition, but I am unclear as to how to proceed, and if the partition to be specified is the new System Reserved Partition or the new Windows installation partition, etc. I have no heartburn with having non-conflicting copies on multiple drives, and the above link seems to accommodate this. In addition, the BCD deployment feature of Easy_BCD seems somewhat relevant, with "Install BCD" and "Write MBR" operations.
If you cannot first suggest an obvious [test] approach with adequate detail to address this problem [that hopefully impacts only the new drive], please specify the additional information and screenshots that you need, and I will gladly provide it.
I appreciate your help on this.
Thanks
Thanks for the great tool and community. My goal is to transfer my Windows 10 System to a new SSD on the same rig. I installed Easy_BCD on the old drive.
I have read that the new Windows 10 April/May/June 2018 upgrade may require a larger System Reserved partition to install, so that new partition size is increased to 3.6 Gigabytes (~10 times the old standard) on the new drive. In addition, the new SSD has the Windows partition (~830 Gigabytes) and the two small System Recovery partitions that appear on the old drive.
Using HD_Clone, I cloned each old partition onto the new drive's respective partition. There is automatic adjustment at the end of the clone that seems to be geared to resolving conflicts in device ID (?) etc.
The system boots onto the old drive (which has BIOS priority over the new drive) and I can see all drives and partitions in Computer Management/Storage utility. Note that the very original drive is still on the system, we'll call it the "data drive"; but it still retains its original System Reserved partition.
Booting to the old drive and using Easy_BCD, I added the new drive's installation partition to the boot menu, retaining the old drive's installation partition as default. System then goes through boot menu and boots fine to old drive as default.
When I reboot and select the new drive as boot drive from the boot menu, the system does start, but acts very flaky after giving me a pop-up error window:"sihost.exe - Unknown Hard Error" message and stumbles on for a while before I stop it. The disk activity seems to be on the new drive in this case (not the old drive), but a strange disk naming convention is sometimes used that makes reference to the original System Reserved partition on the data drive as a prefix to the partitions being referenced.
I am hopeful that Changing the Boot Partition or some other approach will allow me to straighten out this condition, but I am unclear as to how to proceed, and if the partition to be specified is the new System Reserved Partition or the new Windows installation partition, etc. I have no heartburn with having non-conflicting copies on multiple drives, and the above link seems to accommodate this. In addition, the BCD deployment feature of Easy_BCD seems somewhat relevant, with "Install BCD" and "Write MBR" operations.
If you cannot first suggest an obvious [test] approach with adequate detail to address this problem [that hopefully impacts only the new drive], please specify the additional information and screenshots that you need, and I will gladly provide it.
I appreciate your help on this.
Thanks