Using an existing w7x64 SSD in a new build with a new key

disasterman5

Prominent
Apr 28, 2018
19
0
510
UPDATE - I had an existing Dell Studio XPS 7100 with Win7 Pro x64 Sp1 and have built a new PC. I had a relatively new 500GB Samsung SSD in the Dell, but needed a much bigger drive in the new build. I tried using a 1TB Crucial SSD and purchased a NEW OEM disc and key for the new computer, since everyone said I can't transfer the old Win7 OEM key.

I had made TONS of modifications to the Windows system and really didn't want to have to go through copying over all the things necessary to completely redo all that. But nevertheless, all the experts on several forums stated that no way would it work to do what I wanted to do, which was to simply take the old Samsung SSD out of the Dell unit, plug it into the new build, then change the product key. SO I set about doing it the painful way. Starting with the Blank NEW 1TB SSD and the new Windows boot disk, I loaded Windows on the new machine, loaded all the drivers, and started doing all my tweaks, and got to my email program which is also a pain in the @$$ to move. No luck whatsoever getting Vivaldi to save my info, even copying the full profile over.

SO, out of frustration. I shut it down, yanked the 1TB drive out, and got my old Samsung SSD out of the Dell and plugged it in in place of it. It booted just fine. Immediately I got the warning that my copies of windows did not appear to be genuine, and a pop-up box with options to reload a new product key to re-validate. I typed in the NEW key code from the NEW windows OEM disk, and whadaya know, everything worked beautifully.

I then cleaned the Crucial drive, and removed everything from it, and ran it plugged into the old machine's power, but not the SATA connector, for the recommended 8 hours to allow the "Garbage Collector" built into the disk to reset everything to blank, like new condition.

I then loaded the cleaned drive in the #2 bay slot in my new machine, and downloaded the free cloning software for the Crucial drive from Acronis. I ran the clone operation, and it took about 30 minutes. I then had a new 1TB drive fully loaded with all my existing stuff, didn't have to reinstall anything, and everything works great.

I'm now taking the 500GB Samsung drive with all the info still on it, reinstalling it in the Dell machine, and re-validating the Windows with the original OEM Dell product key.

So, the way to do all this was to load the NEW windows OEM disk onto the new machine using the new 1TB Drive to activate it, and key it to the new mobo, then remove that drive, swap it with the 500GB existing SSD from my Dell, enter the NEW product key when prompted to re-validate, then cleaning the 1TB drive completely, reloading it as the number two drive in the new machine, then using the free Acronis software that came with the new Crucial drive, to clone the old drive over to the bigger new one.

Responses below were from the original question if not dated after today 6-18-18
 

USAFRet

Titan
Moderator
My question is, can I load the new Win7 pro x 64 and key onto the new build, using the new empty SSD, do the drivers, then clone my existing SSD over to the new SSD and have everything work without having to reload everything?

No, for several reasons.

1. The current Win 7 install on the drive is unlikely to work in a whole different system. It will probably fail to boot up

2. You can't install and OS and all its drivers, then 'clone' a different over top of it.
The clone completely blows away and replaces what OS you put on it before.

3. "Zinstall"? I'd have to see an independent review and test of that. Transferring applications between installed OS's is a non-trivial task.

4. A whole week? To actually have it working? Rather than flailing about with different levels of untried and untested solutions and no-name applications?
I'll take the week to do it manually.

I'm a big proponent of a clone operation, when used properly. Going from an OEM Win 7 in a Dell to a custom PC is not one of those situations.
 

disasterman5

Prominent
Apr 28, 2018
19
0
510
My speculative questions were based on the seemingly limited problem of the OEM key being slaved to the mobo, and that otherwise there wouldn't be a *problem*. I would think that whatever settings in the old copy of Win7Prox64 that I apply over the new, would be what I am going to have to do anyway, so don't understand why that couldn't be done if the key is the only problem. I will be using the same apps and tweaks to the new. Drivers for the new hardware I would think could be maintained simply not moving the old driver files over, but many will be duplicated anyway. I will be reusing the same printer, wifi adapter, and other peripherals that I am now.

Below is a link to Zinstall, the product that claims to do this.

Part of my lack of understanding is not knowing where or how drivers are installed, or why they would be necessarily any different, since they are simply the instructions for the operation of peripherals and apps. I had to install all these same drivers when I put these devices on my existing computer. Many had CD's, many others, the drivers were installed automatically by Windows.

But the hundreds of tweaks, and copying of links and shortcuts, and rebuilding the desktop and quick launch bar all seem to be ridiculously redundant, when they are the already on my SDD, when I am using the identical operating system, and all system files and drivers for my equipment are going to be the same, save a few drivers specific to the new motherboards chipsets and controllers, which I would think would remain or could be write protected.
 

USAFRet

Titan
Moderator
Taking a drive with OS from one system and putting it in a different system often fails completely.
Win 10 has gotten a lot better with this, but Win 7? Unlikely to work.
A clone is exactly the same as moving the physical drive.

It's not the "drivers" that you install...this happens on a much deeper level.

Basically, three outcomes when trying that:
1. It boots up just fine.
2. It fails completely
3. It boots up, but you have underlying issues later.

I've seen all 3, with varying OS's.


The license key is NOT the problem.
If you were to install an OS (OS #1), then apply a clone of an OS from a different system (OS #2) on top of that...OS #1 is wiped out completely. It is not just "settings"
It is everything. The OS #1 ceases to exist on that drive.


As for Zinstall? The 'testimonials' on their website are worth exactly squat. I mean independent reviews and tests.
Try it. It might work. You get to be our test case.

People have been looking for such a tool for a long time.
Haven't seen one yet that actually 'works'.
 

disasterman5

Prominent
Apr 28, 2018
19
0
510
Well, harrumph. LOL.

But I don't wanna be the test subject.....

I figured there was some secret coded file in the BIOS that the OS was attached to, and once that new code was in the BIOS, I could swap out the drive with the new unadulterated pristine OS with my totally convoluted and compromised custom one and no problem if I re-certified it. As they say in the UK, "Bollocks!" We can land a man on the moon, but we can't give him a box with more computing power than all of Mission Control, and let him move it to another box! :\