I did, however, change my UEFI set-up's boot order to make the cloned drive 1st for the Win10 upgrade process rather than relying on F-key selection during start-up. So saying that "you can't boot from a clone when you already have a valid boot drive installed" is certainly not correct in all cases. And I can still boot to the Win8.1 OS on the original source drive which remains exactly as was before cloning. On my Asus P8Z77-V deluxe system, I've just finished cloning my existing Win8.1 SSD to another SSD, booting to that 2nd SSD with the source drive remaining in place, and then I upgraded the cloned Win8.1 OS to Win10 Pro 圆4 (build 10240 - fully licensed and activated) without any problem at all. Did you try running Reflect's "Fix Windows Boot Problems" utility in the WinPE "rescue" environment? Maybe the problem in your case was due to some kind of mother board set-up issue or some glitch in the boot configuration data (BCD) store pointers for the ApplicationDevice and/or OSDevice on the cloned drive. Without in any way disputing your experience, it differs from my own. So for anyone else testing their Clone, you can't boot from a clone when you already have a valid boot drive installed. I'm sure I could have just left the clone dive plugged into the SATA port where I started - and just unplugged the C: drive and would have been fine.
When I looked at the clone drive in Drive Manager, it was now "C:" drive and had the "Boot, Page File, and Crash Dump" showing on the primary partition. This time when I rebooted and the computer started up. So to further test, this time I removed the current C: drive and installed the clone E: drive (plugging in to same SATA port that C: was using. I restarted but this time went into BIOS (UEFI) and set the new E: drive as first boot device, checked all the settings and restarted. All I got was a blinking white dash on a black screen. I booted up using F11 to select the boot drive, and I selected the new drive E: (a Samsung 850 Pro SSD). I was wondering if something didn't clone properly so I decided to try to boot of the cloned drive. Go to "Storage > Disk Manager"), the clone looks identical both the existing C: drive and cloned E: drive showed the primary partition as Active except the "E:" drive and does not show "Boot, Page File, Crash Dump" in the primary partition like the original drive does.
open File Explorer, right-click on "Computer" or "This PC" depending on OS, then select "Manage". When I looked at the clone drive in Windows Disk Manager (i.e. The clone was successful (took 2.14 minutes). I used Macrium v6 for the first time to clone a 64GB SSD for the purpose of replacing the drive with a larger SSD. I wanted to post this in case anyone else runs into this.
0 kommentar(er)
