Cloned install boot issues

Ok long story short.

Used messy procedure to clone hdd to ssd via norton ghost.

The 100mbit partition is removed, and new partition is aligned on ssd.

New partition has mbr, marked as active, and is now the system partition, the system boot part WORKS. Its for sure as I removed old system files of original hdd boot.

Now here is where I am currently stuck.

On boot comes up a boot menu with 2 options, both windows 7. One is the hdd, other is supposed to be ssd but also boots the hdd.

In msconfig I see the following.

The non default one is to boot of c: drive.
the default one boots of \device\harddisk\volume3\windows

in easy bcd I renamed them so can tell both apart however in terms of boot source of files I can only change drive letter not volume.

so I am stuck.

What defines what is the c: drive right at the start of system boot? in bios the ssd is first boot device yet it seems the original hdd is assigned c:.

currently volume 3 is the old system reserved partition so it seems it points to same device hence both options booting of hdd, the ssd is volume 10. currently without a drive letter, before last reboot it did have a drive letter tho.

Also I just tried setting the device to BOOT in easybcd for the default option but its still booting of hdd.

hdd impossible to unplug sadly its hard to access cable without causing issues.

somehow i managed to access the sata cable on board for the hdd (10+ drives trust me its hard, and be a big tsk to get back in) and unplugged.

now it booted first time to ssd, it seems as if windows bootloader is a bit dumb and searches for operating system in order of drives or something.

now with that out of way it hung on preparing desktop for a couple of minutes and then was staring at a blank desktop for 10 mins, windows unactivated as well, I then ctrl-alt-del loaded task managaer, explorer which then finished the boot, all my gui config desktop etc. icons etc. missing and a bubble saying I am on a temp profile as my files cant be accessed.

I cant load a window to browse files/dirs cant load computer management"the spcified path does not exist" I suspect the drive is labeled as f: not c:.

I already did that easybcd process you linked to. remember the system is able to boot of the ssd bootmgr, the issue is whats happenening after the boot menu.

confirmed the drive is f: and is no c: drive at all now.

startup repair says nothing wrong, windows still boots as f:

so to summarise.

if hdd plugged in.

ssd loads bootmgr but windows is loaded of hdd on c: with both boot optoins

if hdd unplugged

ssd loads bootmgr, first boot option fails as hdd unplugged, 2md default loads os of ssd but it boots as f: which causes massive failures on boot as profile etc. cannot be accessed.

more fun and games

from bit of googling its became apparent one should never boot a cloned disk the first time with the original still plugged in as I did.

So I wiped the drive using clean in diskpart. (since i cant use disk manager without plugging this other hdd back in)

now symantec recovery disk does not show the drive as available to restore to it is listed in diskpart as online.

also I cant secure erase the ssd due to samsungs tool not working on boot, so I am hoping if I ever get this done a optimisation run will sort out all trim etc. on wiped blocks.

I also see partitions listed that arent on diskpart, so SRD seems funky. I guess I need to take a pic with my camera to show you guys what I mean.

ok that 99gig was a theortical partition on the ssd if it cloned the partition I figured it out in end.

so restored imagae again to ssd.
copied over bootmgr as before.
this time with oiginal hdd unplugged it boots fine. although is a pause on boot. is c: drive.

however of course I still want to use old hdd is expensive wd black 640gig. so plug it back in. luckily wasnt that hard to do in end.
however it now messed up boot again.

i think but not sure it booted off hdd windows partition again by noise and it has given me a black desktop as it seems the hdd boot doesnt work properly now.

what I wanted was to keep the windows files intact on this drive but it seems this isnt going to be possible if I want the ssd to boot and work normally.

update I think is still using ssd but is a signatur collision with old hdd. Can this be fixed without wiping old hdd?