I recently installed a Samsung 860 EVO 250GB mSATA SSD in my motherboard, and I'm trying to migrate an existing Windows 10 installation from an HDD in the desktop to the mSATA SSD. I initialized the SSD by doing a clean install of Windows 10 to a 100GB partition to get the BCD Store updated to boot to the SSD, which worked fine. I then restored a partition image (from a 100GB partition) to the 100GB partition on the SSD, but it boots to a mouse cursor on a black screen, and the drive activity light continuously flashes.
What am I doing wrong. The is basically the same procedure I've used before in replacing failing hard drives, which has always worked great.
Moving Windows 10 from HDD to mSATA SSD
Re: Moving Windows 10 from HDD to mSATA SSD
bbearren,
When you restored the image did you select "Change GUID"?
Have you tried disconnecting the HD? Does the SSD boot?
It might need a BCD Edit if it doesn't boot with the HD disconnected.
I assume it is a MBR system.
When you restored the image did you select "Change GUID"?
Have you tried disconnecting the HD? Does the SSD boot?
It might need a BCD Edit if it doesn't boot with the HD disconnected.
I assume it is a MBR system.
Re: Moving Windows 10 from HDD to mSATA SSD
Brian K wrote:
> bbearren,
>
> When you restored the image did you select "Change GUID"?
> Have you tried disconnecting the HD? Does the SSD boot?
> It might need a BCD Edit if it doesn't boot with the HD disconnected.
> I assume it is a MBR system.
No, I didn't select "Change GUID". I'll try that.
I've done a clean install to initialize the SSD and check it out, and it booted fine.
This is a GPT system.
> bbearren,
>
> When you restored the image did you select "Change GUID"?
> Have you tried disconnecting the HD? Does the SSD boot?
> It might need a BCD Edit if it doesn't boot with the HD disconnected.
> I assume it is a MBR system.
No, I didn't select "Change GUID". I'll try that.
I've done a clean install to initialize the SSD and check it out, and it booted fine.
This is a GPT system.
Re: Moving Windows 10 from HDD to mSATA SSD
OK. Your HD should have 4 partitions associated with the OS...
Recovery
ESP
MSR
Win10
I suggest imaging all partitions (single file) and restoring the image to a blank, empty SSD. Use "Change GUID". For safety I'd disconnect the HD prior to the restore or at least before the first boot from the SSD. You will probably need to do a BCD Edit. Wait and see.
Recovery
ESP
MSR
Win10
I suggest imaging all partitions (single file) and restoring the image to a blank, empty SSD. Use "Change GUID". For safety I'd disconnect the HD prior to the restore or at least before the first boot from the SSD. You will probably need to do a BCD Edit. Wait and see.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: Moving Windows 10 from HDD to mSATA SSD
simple operations backup, install new drive, restore.
Or if in the same system, simple operations copy.
All handled for you.
To manually do it, do an entire drive backup, restore entire drive backup,
use the "update boot partition" option if it shows up, and if planning on
both drives attached at the same time on any boot or hot swap, ensure to use
"Change disk ID and guids" option as Brian suggests.
"bbearren" wrote in message news:16794@public.image...
I recently installed a Samsung 860 EVO 250GB mSATA SSD in my motherboard,
and I'm trying to migrate an existing Windows 10 installation from an HDD in
the desktop to the mSATA SSD. I initialized the SSD by doing a clean
install of Windows 10 to a 100GB partition to get the BCD Store updated to
boot to the SSD, which worked fine. I then restored a partition image (from
a 100GB partition) to the 100GB partition on the SSD, but it boots to a
mouse cursor on a black screen, and the drive activity light continuously
flashes.
What am I doing wrong. The is basically the same procedure I've used before
in replacing failing hard drives, which has always worked great.
Or if in the same system, simple operations copy.
All handled for you.
To manually do it, do an entire drive backup, restore entire drive backup,
use the "update boot partition" option if it shows up, and if planning on
both drives attached at the same time on any boot or hot swap, ensure to use
"Change disk ID and guids" option as Brian suggests.
"bbearren" wrote in message news:16794@public.image...
I recently installed a Samsung 860 EVO 250GB mSATA SSD in my motherboard,
and I'm trying to migrate an existing Windows 10 installation from an HDD in
the desktop to the mSATA SSD. I initialized the SSD by doing a clean
install of Windows 10 to a 100GB partition to get the BCD Store updated to
boot to the SSD, which worked fine. I then restored a partition image (from
a 100GB partition) to the 100GB partition on the SSD, but it boots to a
mouse cursor on a black screen, and the drive activity light continuously
flashes.
What am I doing wrong. The is basically the same procedure I've used before
in replacing failing hard drives, which has always worked great.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: Moving Windows 10 from HDD to mSATA SSD
(you may also need "scale to fit" and "remove gaps", if not enough room,
also "compact data" but only if needed).
"TeraByte Support" wrote in message news:16799@public.image...
simple operations backup, install new drive, restore.
Or if in the same system, simple operations copy.
All handled for you.
To manually do it, do an entire drive backup, restore entire drive backup,
use the "update boot partition" option if it shows up, and if planning on
both drives attached at the same time on any boot or hot swap, ensure to use
"Change disk ID and guids" option as Brian suggests.
also "compact data" but only if needed).
"TeraByte Support" wrote in message news:16799@public.image...
simple operations backup, install new drive, restore.
Or if in the same system, simple operations copy.
All handled for you.
To manually do it, do an entire drive backup, restore entire drive backup,
use the "update boot partition" option if it shows up, and if planning on
both drives attached at the same time on any boot or hot swap, ensure to use
"Change disk ID and guids" option as Brian suggests.
Re: Moving Windows 10 from HDD to mSATA SSD
Brian K wrote:
> OK. Your HD should have 4 partitions associated with the OS...
>
> Recovery
> ESP
> MSR
> Win10
>
> I suggest imaging all partitions (single file) and restoring the image to a
> blank, empty SSD. Use "Change GUID". For safety I'd disconnect
> the HD prior to the restore or at least before the first boot from the SSD.
> You will probably need to do a BCD Edit. Wait and see.
My system is a bit more complicated. I have 3 HDD's as well as the mSATA SSD that I recently installed. I created an EFI partition for the SSD, imaged the existing EFI partition of HDD 0 and restored it to the SSD, booted into BootItUEFI and deleted the EFI partition on HDD 0 and rebooted into Windows. That worked. Next I created the 100GB partition (using BootIt) on the SSD, and another partition for data that took the rest of the drive. There is no MSR partition. My Recovery partition is still on HDD 0, boots from there (with Image For Windows added) and works fine.
I just did an Image For Windows copy of my existing installation to the 100GB partition on the mSATA SSD, and I'm booted into it now. I used "Change GUID" as you suggested, but it still wouldn't boot. Then I found an erroneous entry in the BCD store that was evidently pooching driver loading on the SSD. After I deleted that entry, it booted just fine. The entry was "loadoptions DDISABLE_INTEGRITY_CHECKS" which was used in earlier versions of Windows to enable the use of unsigned drivers. It isn't even listed in the bcdedit help menu. I have no idea how it got there.
I've been scratching my head on this one for a couple of days, but hadn't thought about "Change GUID". Thanks for that!
This one is solved!
> OK. Your HD should have 4 partitions associated with the OS...
>
> Recovery
> ESP
> MSR
> Win10
>
> I suggest imaging all partitions (single file) and restoring the image to a
> blank, empty SSD. Use "Change GUID". For safety I'd disconnect
> the HD prior to the restore or at least before the first boot from the SSD.
> You will probably need to do a BCD Edit. Wait and see.
My system is a bit more complicated. I have 3 HDD's as well as the mSATA SSD that I recently installed. I created an EFI partition for the SSD, imaged the existing EFI partition of HDD 0 and restored it to the SSD, booted into BootItUEFI and deleted the EFI partition on HDD 0 and rebooted into Windows. That worked. Next I created the 100GB partition (using BootIt) on the SSD, and another partition for data that took the rest of the drive. There is no MSR partition. My Recovery partition is still on HDD 0, boots from there (with Image For Windows added) and works fine.
I just did an Image For Windows copy of my existing installation to the 100GB partition on the mSATA SSD, and I'm booted into it now. I used "Change GUID" as you suggested, but it still wouldn't boot. Then I found an erroneous entry in the BCD store that was evidently pooching driver loading on the SSD. After I deleted that entry, it booted just fine. The entry was "loadoptions DDISABLE_INTEGRITY_CHECKS" which was used in earlier versions of Windows to enable the use of unsigned drivers. It isn't even listed in the bcdedit help menu. I have no idea how it got there.
I've been scratching my head on this one for a couple of days, but hadn't thought about "Change GUID". Thanks for that!
This one is solved!
Re: Moving Windows 10 from HDD to mSATA SSD
Great news. Thanks for the feedback.