windows 10 won't boot

[FluffySheep]

Hi all. First the setup

I have windows 10 running on a MSI Z68-DG65 motherboard. Ive run out of space on my 120GB SSD (12 year old and his use of roblox/games/rubbish), so I've got a new 500GB SSD. I've used macruim reflect to clone the drive, then I've extended the partition to the 'full' 466GB of the new drive. I can boot onto the original 120Gb drive fine, from there I can open windows explorer and interact with the new SSD and the files on it, but when I disconnect the old SSD I cannot boot. It says there's no drive to boot from, but the BIOS can see it, and it's set to be the primary boot drive in the BIOS (I've pulled all other HDDs to remove any aggro about opening another boot for some reason).

Treat me like a moron, what have I missed?
Tried looking for BIOS update, I have the latest.
Scandisk shows new drive as no problems and healthy.
Both drives are NTFS.
Both drives are MBR (read something about converting to GPT disk - red herring???)

Thanks in advance
FluffySheep

 

[Tetras]

Both drives are MBR (read something about converting to GPT disk - red herring???)

If you have secure boot and/or CSM enabled, then you can have difficulty using a MBR drive as a boot drive, but otherwise it should work fine. I'd assume this is not the problem anyway, because you can still boot from the 120GB drive.

I've used macruim reflect to clone the drive, then I've extended the partition to the 'full' 466GB of the new drive.

I don't use this software, but is there a possibility that by extending the partition you actually deleted/scrubbed some of the junk Windows creates by default and this is now preventing it from booting?

 

[FluffySheep]

If you have secure boot and/or CSM enabled, then you can have difficulty using a MBR drive as a boot drive, but otherwise it should work fine. I'd assume this is not the problem anyway, because you can still boot from the 120GB drive.


I don't use this software, but is there a possibility that by extending the partition you actually deleted/scrubbed some of the junk Windows creates by default and this is now preventing it from booting?

Thats my current idea. I've found the Boot Configuration Data (BCD) on the new drive is borked. I've reset it and now the error is pushing me to repair windows, so progression is being slowly made (at 1am!)

FlussfSheep