aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
I bought a new Samsung 980 1TB SSD and I've installed it. I tried cloning windows from my old KINGSTON 110GB SSD (using Macrium Reflect) to my new one. However, when I did so I realized that neither the old nor new SSD would boot up windows without the ERROR 0XC0000F message. And the only way I could boot up windows was from my HDD which I didn't even realize still had windows installed on it (which got me wondering If I was always booting up windows from the HDD).

Even though my old SSD is the windows drive on my PC, I can't even boot it up from that one anymore without the error message.

Any ideas what I can do to get windows on my new SSD ?
 
Last edited:

USAFRet

Titan
Moderator
Mar 16, 2013
153,638
10,987
175,990
24,031
1. Return the system back to original config, without the new SSD.
Does it boot up?

2. Give us a screencap of the original working Disk Management window

3. Is the original drive MBR or GPT? Both drives MUST be the same (pref GPT)
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
1. Return the system back to original config, without the new SSD.
Does it boot up?

2. Give us a screencap of the original working Disk Management window

3. Is the original drive MBR or GPT? Both drives MUST be the same (pref GPT)
Screengrab of disk management is here now. I think both are GPT but I don't really know what it means (EDIT: yes they are both GPT after checking)
 

USAFRet

Titan
Moderator
Mar 16, 2013
153,638
10,987
175,990
24,031
So it now boots up properly?

If so, redo the clone operation.
Since you have a Samsung drive, try the Samsung Data Migration tool.

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

(ignore this if using the SDM)
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specifiy the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
So it now boots up properly?

If so, redo the clone operation.
Since you have a Samsung drive, try the Samsung Data Migration tool.

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

(ignore this if using the SDM)
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specifiy the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------
Thank you I will follow these instructions. But first you ask if it is now booting up properly, I just want to make it clear that it's the HDD that I'm bootin from currently. Shall I still proceed?
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
Bootloader probably is on HDD.
Show screenshot from Disk Management.
(upload to imgur.com and post link)

Probably have to create bootloader on SSD.
Show the screenshot first.
I disconnected my HDD and I ran into the error , meaning i will have to manually create a boot partition drive to the old SSD. Do you know how to do this, and could you walk me through it?
 
here is my disk management
Here's how to fix your 120GB drive and make it bootable.
There is already bootloader partition on it. It's rather small though - only 100MB. Recommended size is 350MB-500MB.
We'll delete 450MB recovery partition, 100MB EFI system partition and create a new EFI system partition.
If there are any errors, then stop immediately.
Execute from elevated command prompt. Regular command prompt will give error on last steps.

diskpart
list disk
select disk 2
(select 120GB disk)​
list partition
select partition 2
(select 100MB EFI System partition)​
delete partition override
select partition 1
(select first 450MB recovery partition)​
delete partition override
create partition efi size=450
format fs=fat32 quick
assign letter=H
exit
bcdboot C:\windows /s H: /f UEFI
bootsect /nt60 H: /force
Show screenshot of command output.
If everything is good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.

 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
Here's how to fix your 120GB drive and make it bootable.
There is already bootloader partition on it. It's rather small though - only 100MB. Recommended size is 350MB-500MB.
We'll delete 450MB recovery partition, 100MB EFI system partition and create a new EFI system partition.
If there are any errors, then stop immediately.
Execute from elevated command prompt. Regular command prompt will give error on last steps.

diskpart
list disk
select disk 2
(select 120GB disk)​
list partition
select partition 2
(select 100MB EFI System partition)​
delete partition override
select partition 1
(select first 450MB recovery partition)​
delete partition override
create partition efi size=450
format fs=fat32 quick
assign letter=H
exit
bcdboot C:\windows /s H: /f UEFI
bootsect /nt60 H: /force
Show screenshot of command output.
If everything is good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.

Great, thank you ! Would it be necessary to even disconnect my m.2 SSD and not just the HDD ??
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
Here's how to fix your 120GB drive and make it bootable.
There is already bootloader partition on it. It's rather small though - only 100MB. Recommended size is 350MB-500MB.
We'll delete 450MB recovery partition, 100MB EFI system partition and create a new EFI system partition.
If there are any errors, then stop immediately.
Execute from elevated command prompt. Regular command prompt will give error on last steps.

diskpart
list disk
select disk 2
(select 120GB disk)​
list partition
select partition 2
(select 100MB EFI System partition)​
delete partition override
select partition 1
(select first 450MB recovery partition)​
delete partition override
create partition efi size=450
format fs=fat32 quick
assign letter=H
exit
bcdboot C:\windows /s H: /f UEFI
bootsect /nt60 H: /force
Show screenshot of command output.
If everything is good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.

I got to the trying to creating the partition efi size=450 then it led to this.
View: https://imgur.com/a/JCNEsqK

Any ideas - sorry I'm really clueless to all this.
 
You didn't delete recovery partition 450MB. Without deleting recovery partition there's not enough space to create 450MB EFI system partition.
You skipped these commands:
select partition 1
(select first 450MB recovery partition)​
delete partition override
Continue this way (execute from elevated command prompt):
diskpart
list disk
select disk 2
(select 120GB disk)​
list partition
select partition 1
(select first 450MB recovery partition)​
delete partition override
create partition efi size=450
format fs=fat32 quick
assign letter=H
exit
bcdboot C:\windows /s H: /f UEFI
bootsect /nt60 H: /force
 
Last edited:

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
You didn't delete recovery partition 450MB. Without deleting recovery partition there's not enough space to create 450MB EFI system partition.
You skipped these commands:


Continue this way (execute from elevated command prompt):
diskpart
list disk
select disk 2
(select 120GB disk)​
list partition
select partition 1
(select first 450MB recovery partition)​
delete partition override
create partition efi size=450
format fs=fat32 quick
assign letter=H
exit
bcdboot C:\windows /s H: /f UEFI
bootsect /nt60 H: /force
Okay thank you. that seemed to of worked I guess. Here is a screengrab of the cmd View: https://imgur.com/a/ok7Cf0J


Shall I now proceed to set the SSD as boot option 1 in bios? (and disconnect the HDD)
 
It looks like you executed commands with wrong syntax several times.
Most of command output is not visible in the screenshot.

So - can't really tell, if everything was done properly. Could be fine, could be not.

Anyway - if everything seems good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.
 
Reactions: aidfarrell70

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
It looks like you executed commands with wrong syntax several times.
Most of command output is not visible in the screenshot.

So - can't really tell, if everything was done properly. Could be fine, could be not.

Anyway - if everything seems good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.
It looks like you executed commands with wrong syntax several times.
Most of command output is not visible in the screenshot.

So - can't really tell, if everything was done properly. Could be fine, could be not.

Anyway - if everything seems good, then disconnect all drives, leave only 120GB drive connected.
Boot into BIOS and set boot priority - Windows Boot Manager on 120GB drive - as first in boot order.
Should be able to boot into windows with only 120GB drive connected.
I did as you said and it worked. I was able to boot up straight from the 120gb SSD :). I'll begin the clone process with the Samsung data migration now. I will update if anything doesn't go to plan. Thanks
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
Make sure you remember to disconnect all the other drives after cloning.
First boot from new drive has to be with old drives disconnected.
This step can not be skipped. If you fail to do this, you'll have to redo cloning.
Okay so I did that and it worked. I was able to boot up windows with the new SSD. However, now that I have connected the other devices and booted up, disk management says the new SSD is offline as it has a signature collision with an online device (I'm guessing the old SSD with windows still on it). What's my best course of action. Do i format the old SSD ?
View: https://imgur.com/a/KPiFHoZ
 

aidfarrell70

Reputable
Mar 17, 2018
61
1
4,535
0
Set boot priority in BIOS properly.
Make Windows Boot Manager on Samsung 980 - first in boot order.

After that boot into windows and delete EFI System partitions from other drives. Leave it only on Samsung 980.
It's weird because I did this and it seems to reset itself. Still says 120gb SSD is the windows drive. I'll try deleting the EFI system partitions from the other drives to see if that fixes it.

EDIT: it also seems like no matter the boot order it will still boot from the HDD. I don't know how to delete the EFI partition from the HDD in disk part as I don't know which one it is - View: https://imgur.com/a/d5Rprwb
 
Last edited:

ASK THE COMMUNITY