Cloning OS's: This needs to be addressed {GUIDE on Windows Cloning}

I'm making this small guide because quite frankly I'm sick of seeing replies with 'just reinstall' because someone is afraid to clone their shit. It seems even my boss ('Senior' Desktop Tech) doesn't know how this works. For the love software and computing, this is usually an easy process.

A lot of tools out will do it for you in a breeze. I'm going to attempt to make this guide for you guys to reference and provide information. Feel free to comment/give feedback for me to add and make this a better guide for everyone.

This is a general guide for windows installs. If someone wants to cover Linux, feel free and I will link it here.

The guide:

Compatibility


For starters:
If you're migrating to a different chipset, it is not recommended that you migrate your installation. You can do this, but likely you will mess things up, and there isn't really a guarantee your machine will work correctly. So usually and motherboard swap needs a fresh install.

Example:
I migrated my 2600k install to my 4790k install, which worked for a time but had stability issues, as well as issues saving data. I uninstalled chipsets with little luck at keeping the system working correctly.

Additionally this means you should not migrate laptop installs to a desktop (should be obvious).

How do I know if I have the same chipset?
If you're not changing the CPU or motherboard the chipset is the same. If you switch motherboards, you might be lucky to get the same chipset, or only have to uninstall drivers. It is generally recommended that if you change motherboards, its time for a fresh install.

What about a CPU swap?
You can generally get away with this. Always verify the device is recognized in Device manager and reinstall your chipset drivers. If you have any sort of stability issues, fresh install.

How about a larger drive to a smaller one?
Are you familiar with the Disk Management tool? Time to get familiar.

Lets say I wanted to copy this

To this:

First, I need to figure out how much free space is on Drive I:
Right click main partition>properties

and you get:

Now, since the drive I'm migrating to is only 238.48 (or 240GB SSD) I will need to uninstall/remove things to migrate this partition. Keep in mind you will also need to migrate the smaller 'system reserved portion, as it contains the information required to boot the OS.

Once I've made the 'Used space' less than the size of the drive, I can get ready to migrate. You can shrink partitions using the disk management tool. You can also use third party stuff, and I'm pretty sure you can do this in Clonezilla, although it is easier to get your devices/partitions confused if you're not familiar.
Right click partition>Shrink volume

You will get something like this:

The tool auto divides based on free space, so you don't typically need to edit it. If you're confused on the space, Google MB to GB calculator.

What about the 'System Reserved' or the 'Recovery Partition'?

System reserved is the MBR/Boot portion of the drive, you will need that to boot (so yeah, copy/clone it). Recovery is an OEM thing, and may contain tools/a system image(in some cases) for you to 'recover' the machine. It isn't required, but you can copy it. I personally don't bother with recovery partitions, but that is just me. Keep in mind whatever is in there, be the image, drivers, etc, are what your OEM provided at the time it was shipped, which could be updated with newer stuff by the time you go to use it.

What about a smaller drive to a bigger one?
After the clone/copy, just use the 'extend volume' tool in this list. Pretty much works the same as the shrink tool. Do this after you've migrated the install.

Tools


You can use any partition or drive cloning tool. Most seem to prefer Clonezilla, a free linux based bootable OS. You can make a CD or build a USB drive. If you don't know how to do that frankly this is probably a thread that is beyond you.
If you have the same size drives, you can get one of these great one button cloners like I got:

I love this thing.

Onward:

Guide to Cloning Windows OS


This is the easy part, usually. A lot of software exists for this kind of thing. Some use Acornis, some use Clonezilla, use whatever you like.

For starters, TEST YOUR DAMN DRIVES. You don't really need to do it for the source disk (the drive you're pulling the data from) but you really should for the target drive. This will save you a lot of headache later. Generally new drives are fine, but anything that is a used drive should be tested will a full sector. I'm sensitive about this and usually test the drive regardless, I've had plenty of 'new' drives with bad sectors likely from shipping.

For software like Acronis, this is as simple as selecting the volumes (disks/drives) you would like to backup, and a destination. You can recover from the Acronis Boot CD later.


One thing, Acronis is a bit more sensitive about damaged data/partitions unlike others, like clonezilla.

Clonezilla is an excellent mini linux based OS for cloning/saving partitions. You can read the guide to using clonezilla here and saving disk images here

@FizzyFantom mentioned the importance of the windows COA/Activation key, and I think I should mention some things:
If you change the motherboard/CPU, you're not supposed to use the OEM copy of windows that came with your machine, but a new retail copy. For many, this is an opportunity to change to a newer OS entirely.
Other changes, like the switch to a HDD to SSD should be fine.
It should go without saying that you should not be using the OEM key on a completely separate machine.

Retail copies of Windows can be used multiple times, but in my experience, after two reactivation, you will have to use the voice activation for this to work correctly.
Windows 10 encodes your COA to hardware, including your motherboard/CPU configuration. Keep this in mind, as you can likely skip the step to activate during the install, and it should automatically authenticate later.

Aftermath


For starters, depending on the migration, I generally recommend you run CHKDSK /r in command after a migration to a different sized drive. The blocks may differ, and I can almost guarantee this if you're switching from a HDD to SSD. I run it pretty much every time regardless. This will save you a lot of blue screen and possible data issues now and in the future, so just do it. NTFS file system isn't always a friendly migrating file system.

Now, one thing I should mention- cloning a damaged partition might give you the same results on a new drive. In some cases, this can be fixed with the CHKDSK /F Command on the new drive, but it really depends on the amount of damage/unreadable or uncopyable data there is. The longer you wait to clone a failing HD, the less likely you are to migrate the drive successful to a working one.

CHECK YOUR DEVICE MANAGER. Ensure your devices are recognized/installed correctly. For most drives, Windows is plug and play and will recognize the new device. But you SHOULD CHECK regardless.

For multiple machines/repeated system image

You can techinically copy an activated version of windows multiple times for the same/similiar hardware configs. If you're running a business like me, this will save you untold amounts of time if you have to build multiple systems (say, laptops) of the exact same spec/motherboard + processor.
To reactivate/change the COA after the fact, just run/type Slui 3 in the start menu and press enter. This will run the windows reactivation tool.

Please feel free to give me some feedback, things to add, etc.
I wrote this a while back and now I'm finishing it in haste, I'm sure I've missed some things.

9 Likes

Nice guide thanks for that.

1 Like

Especially convenient if you buy a new laptop and want to upgrade the drive right off the bat.

1 Like

Clonezilla seems to do the trick quite well(And it's free weeeeee), not 100% sure if M$ has win10 boobytrapped, they kind of have a history of putting obstacles everywhere possible with these kinds of things, so i wont hold my name to it, but atleast for win 7-8-8.1 it did the trick quite well as long as you get a newer release which supports GPT partitioning.

Win10 encodes the COA to the motherboard/hardware config- so short of.

I believe it does the same with windows 8, or atleast 8.1 but again i've just not tested Clonezilla with win10 so hands down im not sure.

Again, sort of. Only in UEFI configs. So, if its OEM, yes. If you installed win8/8.1 without UEFI, no.

yea it's sort of a gray zone, i think win8 sort of aimed at allowing you to own older hardware, where win 10 sort of forces you to shell out, but with your cash monay, privacy, and which experience you're allowed to have from your paid for product from M$.
Either way Clonezilla should be capable of handling the task, since it basically just does a bit for bit copy of the harddrive, to another, and the BIOS wont, or atleast shouldn't the know difference unless you change something in the boot order, since the harddrive is essentially the same, except is has some new hardware codes on a low low low level.
Again atleast win 8.1 didn't detect any changes in the setup, but Windows 10 is notorious for creating these redicules hangups like you're "installing on a new machine" cause you changed your RAM sticks, so who knows, M$ really want's your money now.

Nice overview.

It's probably worth mentioning licences when talking about Windows cloning.

Each version is a bit different, but here is the short version:

You can't migrate an OEM licence. It's against Microsoft's terms of service and they have been known to block it on different hardware.

Retail licences can be migrated, but only activated on a specific number of machines at once. May require a phone activation.

Windows 10 licences automatically against the hardware (read motherboard), never seen any issues with re-installation.

It always pays to be careful of licencing as Microsoft's licencing system is as impenetrable as it gets.

1 Like

I'm pretty sure you can, as long as the processor/motherboard remain the same. You're not supposed to if these things change.

Yep. In my experience, more than two and you will have to call.

Yep. So it reads the motherboard/hardware config and activates accordingly.

I'm going to add a portion for writing system images, as you can technically migrate the same activated copy multiple times and change the COA afterward, just run the windows activator exe

Samsung also comes with a tool that can clone your OS from said a HDD to one of their SSD´s.

1 Like

Aw yeah this is good to note. Isn't it free/on their CD?

Yeah its free i guess.
Samsung megician or whatever its called. :-)

Sorry, I didn't make it clear enough when I said you can't transfer it.

Microsoft effectively consider the motherboard the computer. You can change any other component and keep the same licence (and often the same installation).

OEM licences are activated against the motherboard and often check in with Microsoft's servers on activation to make sure they are for that "computer".

1 Like

I used Clonezilla last week, at my job, to migrate Windows 10 to an SSD. It didn't want to boot but using a Windows recovery disk and the BOOTREC commands fixed it. Other than that it seemed to work fine.

1 Like

Details?

Might need to add a BOOTREC portion to this guide

Or you could use dd
kek

3 Likes

I did not really want to get to into this but...

Clonezilla will create images byte-per-byte style so it is not a good idea to use those images on any other hard drive, let alone any other computer. There are workarounds, but they are workarounds which signifies something fundamentally wrong with the workflow.

For anything end-user facing, I would recommend Macrium Reflect instead, since it at least has a GUI. I have not used Acronis, but I assume it is roughly the same thing.

For the overt transferring of images to different hardware or different systems enterprise style (such as when imaging multiple computers at once), I would recommenced Microsoft's Windows 10 ADK, or this older one, with the MDT extension.

  • Free
  • File-by-file based
  • Industry Standard
  • Scalable (SCCM is based on it)
    • The ADK Tools are mostly command line (e.g. scriptable)
    • The MDT extension the ADK Tools using GUIs.
  • Well supported
  • Perfect for small deployments

I'll add that if you are cloning from HDD to SSD that you should check that Windows 10 has correctly identified the new disk as an SSD. This will ensure it changes the preset optimisation from defrag to trim.

In Windows 10 you can just check from the disk tools when you right click properties. The SSD's should be correctly identified in the second column:

If they are not, just running the winsat disk command should be enough for Windows to now correctly identify the new disk as an SSD.

1 Like

Which is why we have the CHKDSK command, which will move the bytes to readable positions accordingly. I don't think there is much wrong here, unless you have specific end users. Otherwise this a generic setup.
If you want a GUI, you can also try Parted Magic, a free linux based tool as well.

I agree that enterprise deployment is different entirely and I will link your guide here. However, for what I'm doing (retail) you cannot use enterprise deployment for the MS Refurbished licenses.
So I'll make a note. But many doing same deployments still aren't using enterprise COAs, unless you mean something different.