System Builder OS to new storage drive?

[telly1220]

Hi guys. So for my build (been done for about two months, runs amazingly, love it) i used a windows 8.1 system builder oem for my OS. I installed that on a WD caviar green (not the fastest hdd by WD i have now heard.) Now though everything is fine and works wonderfully, i thought that i might as well put an ssd in the rig. After all, part of the fun of our hobby is upgrading sometimes for no particular reason right? XD Well anyway, my question is this: can i move my system builder OS to a new ssd or will it be rendered useless? I know that it binds to the mobo but im not sure about the hdd or other components. My other question, if the first one has a positive answer, is how do i clone all of my stuff to a new 250gb sata ssd? Thanks in advance guys
PS how tf do i put a signature on this site? I want to put my pc's specs in it so i dont have to list them every time i ask a question.

 

[glamdringfh]

Hi telly1220,

1) Yes, you can transfer your Windows OEM install to a different hard drive without any issue.

2) You'll need to make sure your current drive has no more than 200GB of data on it (so backup everything else to an external drive) and then follow this guide:

http://www.tomshardware.com/faq/id-2839729/clone-drive.html

*What cloning software you use will depend on what SSD you choose. The different options are at the bottom of the tutorial above.

 

[JackNaylorPE]

The "Binding to the MoBo" thing is somewhat exaggerated.

Cloning may not be the best option.... Here's an alternative to consider and the way I do these is:

1. Disconnect HD data cable.
2. Connect SSD data cable to lowest numbered SATA port
3. Boot to Windows storage media and install windows to SSD.
4. Run Windows update
5. Install drivers from manufacturers web site (not windows update)
6. Run Windows Update the 26 times or whatever it needs to say it's done.
7. Shut down machine and connect data cable to HD (2nd lowest SATA port
8. Check boot order in BIOS (set to SSD > HD > Optical if not listed that way)
9. Install programs over themselves D:\ProgramFiles\Whatever to set up registry

This keep the windows install on your HD intact so you can boot into system if SSD goes south or OS gets fudged for any reason.

Getting back to the tied to the MoBo thing, it doesn't apply a) cause you are using same MoBo and b) it doesn't apply anyway in cases of replacing a dead / defective Mobo. This is for XP but things haven't changed much and I haven't found anyone writing about how since

http://www.helpwithwindows.com/WindowsXP/activation.html

https://technet.microsoft.com/en-us/library/bb457054.aspx

Microsoft defines "substantially different" hardware differently for PCs that are configured to be dockable. Additionally, the network adapter is given a superior "weighting." If the PC is not dockable and a network adapter exists and is not changed, 6 or more of the other above values would have to change before reactivation was required. If a network adapter existed but is changed or never existed at all, 4 or more changes (including the changed network adapter if it previously existed) will result in a requirement to reactivate.

Scenario A:

PC One has the full assortment of hardware components listed in Table 1 above. User swaps the motherboard and CPU chip for an upgraded one, swaps the video adapter, adds a second hard drive for additional storage, doubles the amount of RAM, and swaps the CD ROM drive for a faster one.

Result: Reactivation is NOT required.

 

[glamdringfh]

Jack makes a good point.

It is good to remember that cloning isn't always guaranteed to work (has roughly a 90% success rate), while a fresh install will certainly work. Either way will probably be fine, but if you don't want to chance it go with Jack's steps above.

 

[telly1220]

The "Binding to the MoBo" thing is somewhat exaggerated.

Cloning may not be the best option.... Here's an alternative to consider and the way I do these is:

1. Disconnect HD data cable.
2. Connect SSD data cable to lowest numbered SATA port
3. Boot to Windows storage media and install windows to SSD.
4. Run Windows update
5. Install drivers from manufacturers web site (not windows update)
6. Run Windows Update the 26 times or whatever it needs to say it's done.
7. Shut down machine and connect data cable to HD (2nd lowest SATA port
8. Check boot order in BIOS (set to SSD > HD > Optical if not listed that way)
9. Install programs over themselves D:\ProgramFiles\Whatever to set up registry

This keep the windows install on your HD intact so you can boot into system if SSD goes south or OS gets fudged for any reason.

Getting back to the tied to the MoBo thing, it doesn't apply a) cause you are using same MoBo and b) it doesn't apply anyway in cases of replacing a dead / defective Mobo. This is for XP but things haven't changed much and I haven't found anyone writing about how since

http://www.helpwithwindows.com/WindowsXP/activation.html

https://technet.microsoft.com/en-us/library/bb457054.aspx

Microsoft defines "substantially different" hardware differently for PCs that are configured to be dockable. Additionally, the network adapter is given a superior "weighting." If the PC is not dockable and a network adapter exists and is not changed, 6 or more of the other above values would have to change before reactivation was required. If a network adapter existed but is changed or never existed at all, 4 or more changes (including the changed network adapter if it previously existed) will result in a requirement to reactivate.

Scenario A:

PC One has the full assortment of hardware components listed in Table 1 above. User swaps the motherboard and CPU chip for an upgraded one, swaps the video adapter, adds a second hard drive for additional storage, doubles the amount of RAM, and swaps the CD ROM drive for a faster one.

Result: Reactivation is NOT required.

Hi Jack. So you're saying two things. The first one is that i have to switch out a lot of components and essentially have a new computer for the system builder to not work. Is that correct? And then you're also saying i can just get the ssd and install windows right on to it from the OEM i used to install the OS to my hardrive in the first place? Im just wondering if im understanding correctly.

 

[JackNaylorPE]

A. Windows Activation:

1. I am saying that, with what we know about Windows Activation, you have to change a certain number of things to trigger a problem.

2. I can tell you from experience that I have changed dead 1156 MoBos and CPUs to 1155 MoBos and CPUs w/o issue.

3. I would tell you that is you are retiring an old system and building a new one, that would be stealing even if you could get away with it.... I doubt you would.

4. If you have a failed Asus MoBo, I would not recommend replacing it with one from say Gigabyte; another Asus MoBo would be less likely to trigger an activation issue. But.... if say it was an old socket and you couldn't find an Asus replacement, so you got a Gigabyte one as it was the only one available, calling MS will likely get you an OK (any written support of your dead MoBo i.e. a email from Asus TS would be good.

5. All this is out the windows if it is a mass market PC from Dell, HP etc.

B. Windows install - yes you can install Windows 10 times on the same PC if you want, even have multiple working installations on the same PC at the same time w/ the same product key. When it activates it's going to see the exact same list id components as before so has no reason to refuse activation.