Complications with system image recovery onto a new SSD

So here is my deal. Pre-hard drive change – I had three drives: C/operating system (60gb SSD); d/data drive (1TB HDD); f/data drive (64gb SSD). I planned to change out the c drive with a larger ssd drive and merge the data from the f drive to the new c drive. I created an image and stored on an external drive as well as the internal d drive.

I then swapped out the c drive with the new ssd drive and loaded the image onto it. It worked well and the computer was functioning properly. Knowing that everything was working fine I needed to destroy the data on the original c ssd drive as well as the f drive so I deleted the data on the f drive using command prompt and started it on the original c drive but for some reason did not complete the process.

Now, I can no longer re-boot back into windows on the new ssd drive. I think where it got screwed up was because I had saved material from the c drive (and g partition) and the f drive onto the image, but now I no longer have the f drive installed.

When I go into my windows repair disk it doesn’t want to repair the drive to make it work, nor does it allow me to use the saved image (potentially because it is searching for the f drive which is not there). The error message “element not found. (0x80070490) system image” occurs when I attempt to install the system image. When I go to do the system image recovery it says that it will restore material on the c, g (reserved partition), and f drives. The thing is, none of the drives that I have connected have those drive labels any longer because they are re-assigned a new label because I have un-plugged and re-connected them. Could this be the problem? If so, can I change the drive labels in command prompt?

The other thing is that the computer is not even reading/finding the f drive the I had wiped clean. Is there a step that I have to do for it to locate/find it?

Any help would be much appreciated. I probably should not have been playing with this myself in the first place as I have little computer experience. I should have paid to have it done at a computer shop. Thanks.

I created the system image in windows 7 64 bit. I did have the bootmgr error message at one point in this process. I followed up with the following:
bootrec /FixMbr
bootrec /FixBoot
bootrec /RebuildBcd

So I copied the file to a dvd using my laptop and then dropped it in the desktop cd rom drive and tried running it via the bootable cd option. It brings me to a window that prompts me to select one of two "Windows 7 Home Premium (recovered)" options. When I go to recover it, it starts loading windows but stops at a blue page. In the bottom right hand corner it says that the version is not a genuine windows 7 version...but it actually is.

when I go into my " hard disk boot priority" the following drives and associations are there:
Ch0 M: Patriot Pyro SE (SSD I want the os on)
Ch0 S: WDC (1TB data drive - western digital)
Ch1 M: M4 (crucial ssd)

Got it figured out. I believe it needed both the c drive and f drive in place for the image to install. The drive I said was not being read needed to be formatted...so I did that through the command prompt thanks to a youtube video. How to Format a Drive using the Command Prompt - YouTube. Then re-tried the image recovery and everything took shape. Now, because I don't want that f drive, I will do another image back-up without that drive in the picture. And then re-install...hopefully I don't run into further problems.

Thanks for your time WHS for trying to solve my issue

Actually, I still have an issue...but with something slightly different. So I went to create another system image but this time without the f (data) drive included, but I now know why it was included in the first place. It turns out that for some reason it is being included as a default drive to accompany my c drive in the image. I don't know why because from what I know there are no windows files on the f drive. I currently have two software programs running from that drive though...could that be the issue? If I was to delete them would that eliminate them as a default drive in the image?