This worked 100% successful - In other words Win7 64 seems to fully accept this clone with no issues whatsoever! Booted as a rocket! :-) I just did a experiment: I physically excluded the original system HDD and plugged back the cloned system SSD. It seems that a disk signature collision is occurring! The signatures ARE identical as it is. Incidentally, you did clone the entire drive including hidden system partitions, didn't you? Not just its OS ("C:") partition? In this case, if you want to leave both drives in place, some boot priority changes (or drive connection changes) are likely to be required and possibly resolution of a disk signature collision as well as explained in that linked article.
In those circumstances, no boot order change is usually needed and any temporary "glitch" can usually be overcome quite simply by running the " Fix Windows Boot Problems" utility in Reflect's WinPE rescue environment. Cloning is more usually used for drive replacement where, upon completion of the cloning operation, the old drive is removed and the new drive is installed on the same internal connection port. A precise analysis would require additional details about the system configuration and the Windows OS version, but the problem seems likely to involve the system's boot priority setup (UEFI-GPT or older BIOS-MBR) and its boot order setting, and possibly a disk signature collision as well.
0 kommentar(er)
