Moving Windows to a New Drive

Reinstall unless you have a specific reason to clone. A clone reproduces the old system exactly, which includes every reason it felt slow — the same startup entries, the same leftovers, the same accumulated state, now on a faster disk.

Whichever route you take, back up to a third device first. Both of them work on the drive holding everything you own.

A note on this guide: this rests on how these migrations are structured rather than on machines migrated here. See how we test.

The problem, as it appears

The new drive is faster and bigger and it is sitting on the desk. The question is how to get Windows onto it without losing anything or spending a weekend on it.

Cloning sounds like the answer, because it promises to change one variable and nothing else.

Why cloning first disappoints

Because "nothing else changes" is exactly what it delivers.

A Windows installation accumulates. Startup entries from software removed two years ago, drivers for hardware that has gone, half-uninstalled things, scheduled tasks nobody set deliberately, and a registry that has been written to a few million times. None of that is dramatic on its own, and together it is a meaningful part of why the machine feels tired.

A clone carries all of it across. The result is genuinely faster — the drive is faster — and it is the same system, so the improvement is smaller than the hardware suggests and people conclude the drive was oversold.

A fresh install is often not much more work than a careful clone once you count the checking, the partition extension and the driver tidy-up afterwards. And it produces a machine that is actually new rather than a faithful copy of an old one.

That said, cloning has legitimate uses, and they are specific: software that is awkward to license again, a configuration you did not set up and cannot reproduce, or a machine that has to be working this evening.

What actually matters

Back up to a third device, first

Both routes operate on the drive holding everything you have.

A mistake at the partition level is not the kind you recover by trying again, and the moment it happens is the moment you find out what was only in one place. The backup wants to be somewhere that is neither the old drive nor the new one.

This page contains affiliate links. If you buy through them, Ugly Fixes may earn a commission at no extra cost to you. Products are selected independently.

What is worth copying beyond the obvious — saves, configurations, licence files — is set out in backing up more than game saves.

Find the encryption key before you start

The trap that turns a routine upgrade into a bad evening.

An operating-system-encrypted drive can demand a recovery key after hardware changes, and moving to a new disk or altering firmware settings both qualify. The key is often stored in an online account — which is fine until the machine that would open that account is the one showing the prompt.

Find it, write it down or put it on a phone, and then start. It takes two minutes and it is the difference between an inconvenience and a rebuild.

Connect the new drive without opening anything twice

Cloning needs both drives attached at once, and on a laptop or a small machine with one slot, that means an enclosure or an adapter.

The same hardware earns its keep afterwards, because the old drive becomes external storage the moment the migration is done.

Whether an enclosure or a dock suits you better is argued in external SSD vs drive dock.

Installation media, if you go the clean route

A fresh install needs a USB stick with the installer on it, which the manufacturer's own tool will prepare.

Make it before you take the old drive out, because making it needs a working computer — an obvious thing that catches people who work in the wrong order.

The unallocated space at the end

The most common post-clone surprise, and it is not a fault.

A clone copies partitions at their existing sizes, so moving from a smaller drive to a larger one leaves the difference sitting unallocated at the end of the disk. The new drive reports the old capacity and everything looks wrong.

Extending the main partition into that space is a normal operation in disk management. Occasionally a recovery partition sits between the main partition and the free space, which makes it slightly more involved — worth knowing before assuming the clone failed.

Change one thing at a time in the firmware

A machine may need its boot entry pointed at the new drive, and an older installation may predate settings a new one expects.

Do those one at a time. A machine that will not boot after three simultaneous changes has three candidate causes and no way to tell them apart, and this is exactly the situation where people start updating firmware as well — which is its own decision, covered in BIOS updates: when, and when not to.

Keep the old drive intact for a fortnight

The strongest safety net available and it costs nothing but patience.

Until the new drive has done a couple of weeks of ordinary use, the old one is the only complete copy of the working system. The things you find missing — a licence file, a saved configuration, a folder you forgot was outside your user directory — surface over days rather than on the first afternoon.

Afterwards it becomes a spare or external storage, which is the subject of turning an old drive into portable storage.

If the old drive is failing, the calculation changes

A drive that is already misbehaving is a poor source for a clone — the copy inherits whatever is wrong and the process itself stresses a component that has already shown it cannot be relied on.

In that case, get the data off first and reinstall clean, rather than trying to reproduce a system sitting on a disk that is on its way out. The signs are covered in a drive that has started clicking.

The order to work in

1. Back up to a device that is neither drive.
2. Find the encryption recovery key and store it off the machine.
3. Make the installation media while the machine still works.
4. Decide clone or clean on the reason, not the effort.
5. Attach both drives if cloning.
6. Extend the partition into the unallocated space afterwards.
7. Change firmware settings one at a time.
8. Leave the old drive alone for two weeks.

The mistake to avoid

Cloning to avoid reinstalling software, then wondering why it still feels slow. The drive is the one thing that definitely got faster, and everything else — the startup load, the accumulated state, the drivers for hardware that left years ago — arrived unchanged. The upgrade gets judged on a result it was never going to produce, and the honest comparison is not clone-versus-clean effort but clone-versus-clean outcome.

The second mistake is treating the old drive as the backup. It is a copy of the same data you are about to operate on, attached to the same machine, and a partitioning error can take both in one step. A third device is the only arrangement where a mistake costs you an afternoon rather than everything.