Move Windows to a new SSD or hard drive

Move the Windows you are running to a larger or smaller SSD or hard drive with S.A.K. Utility, from a snapshot, and start from the new drive.

To move Windows to a new SSD or hard drive, use the migration wizard in S.A.K. Utility: open the Partition Manager tab, select the disk Windows runs from, and click Migrate OS to SSD/HDD Wizard. Windows keeps running while S.A.K. copies each volume from a snapshot, builds a new partition table on the new drive, fits the Windows partition to that drive, and rebuilds its boot files. The new drive can be larger or smaller than the old one, as long as what you have on it fits. Everything on the new drive is overwritten.

When to use this

You are moving to a new drive and want to keep your Windows install, programs, and files as they are. It works from the Windows you are running, on that PC.

To copy a data disk, or to keep an exact copy of a disk, use Copy Disk instead.

What you need

  • The new drive connected to the PC, with nothing on it you want to keep. It cannot be read-only, dynamic, or part of Storage Spaces.
  • A backup of your files on a third drive.
  • Administrator approval when you press Apply.
  • BitLocker turned off on the old disk. See the limits below.

How large the new drive must be depends on its size against the old Windows partition:

  • At least as large as the old Windows partition, plus the partitions around it: any such drive works, however full the old one is.
  • Smaller than that: it must hold what is in use on the Windows volume, plus some room to work in, plus a temporary image of Windows that is removed when the move is done. The Review page gives the number if a drive is too small.

Steps

  1. Connect the new drive.

  2. Press Scan Disks.

  3. Click the disk row that holds Windows, not one of its partitions. Its partitions show System or Boot under Flag.

  4. Click Migrate OS to SSD/HDD Wizard. The Source page names the disk you selected. Press Next >.

  5. On the Target Disk page, choose the new drive under Target disk: and press Next >. Check the model and size carefully. The list starts on the first disk Windows fits on, or on none if no disk is big enough.

    The Target Disk page of the migration wizard, with a list of disks showing number, model, and size
    Pick the new drive carefully, because it will be overwritten
  6. On the Options page, set Verify: to Sample verification or Full verification. Leave the check box about copying without a snapshot clear unless Windows has already told you it cannot take one. Press Next >.

    The Options page of the migration wizard, with a note about snapshots, a Verify list, and a check box for copying without a snapshot
    The Options page
  7. On the Review page, read the source, target, and sizes. If it says Blocked:, stop and read why, because this drive will not work.

  8. Check I understand the selected target disk will be overwritten. and press Finish.

    The Review page of the migration wizard, with source and target bars, a summary, and the overwrite confirmation box
    Review the copy before it joins the queue
  9. The migration is now in the queue. Press Apply, read the Apply Partition Operations window, press Apply in it, and approve the Windows prompt.

  10. When it finishes, restart and choose the new drive in your PC's BIOS or UEFI boot order. Your old disk still starts the PC until you do: S.A.K. does not change this PC's boot order.

How it works

S.A.K. checks everything it can before it writes anything: that both disks are the ones you chose, that the old disk's partitions have not changed, that nothing is encrypted with BitLocker, and that both disks use the same sector size.

Then it asks Windows for a snapshot of each volume on the old disk that can have one. A snapshot is a frozen view of the volume at one moment, so nothing that changes after it reaches the new drive, and programs that take part in snapshots get a chance to save their work first. The EFI, reserved, and recovery partitions are copied directly.

Next it takes the new drive offline and writes a new partition table, with the same order of partitions and the same partition style as the old disk, and a new identity for the disk and each partition. It then fills the partitions one of two ways:

  • When the Windows partition fits at its old size or larger: S.A.K. copies the blocks in use from its snapshot, then extends the volume to fill the room. Any other volume on the disk keeps its size.
  • When the new drive is smaller: blocks cannot be moved into a smaller partition. S.A.K. formats a new volume, makes a temporary partition after it, has Windows' own DISM capture an image from the snapshot into the temporary partition, applies that image to the new volume, removes the temporary partition, and extends the volume over its space. This takes much longer, and DISM can read for a long while first with no progress shown. The image leaves out the page file and hibernation file, which Windows makes again, and System Restore points, which do not come across. A Windows in the Compact state stays that way on the new drive.

Sample verification reads blocks from across each partition back from the new drive and checks them against what was copied. Full verification checks every block and takes longer. On a smaller drive, verification is DISM's own check of the image, and Sample verification skips it.

Last, it brings the drive online, rebuilds the boot files for the new drive's own Windows with Microsoft's bcdboot, and sets the new drive's list of drive letters so that Windows finds itself on C: again. Temporary drive letters are taken away, and every snapshot is released.

Good to know

Back up first. Copy anything you care about to another drive before you press Apply. On the v0.9.3 code, Partition Manager operations, including boot repair, MBR-to-GPT conversion and OS migration, ran through the app on disposable virtual machines and virtual disks. Some operations were also tested on one SAMSUNG MZVL2512HCJQ-00BH1 512 GB NVMe SSD and one Seagate Expansion Desk 8 TB USB disk. Internal SATA drives were not tested, and results on other devices may differ. See what was tested. Everything on the new drive is replaced, and this cannot be undone.

  • BitLocker stops it, with the reason. A copy of an encrypted volume would either stay unreadable or put your data on the new drive unencrypted without saying so. Turn BitLocker off for that volume, move Windows, and turn BitLocker on again on the new drive.
  • If Windows cannot take a snapshot, the move stops before writing anything and says why. Run the wizard again and tick the check box on the Options page only if you accept the risk: the running disk is then copied as it is, files that change during the copy can be inconsistent, and the new drive may not start. A smaller drive cannot be filled this way, so it still stops.
  • Your old disk is not changed. Keep it until you have started from the new drive and checked your files. Both disks can stay attached at once, because the new one has its own identity.
  • Work done after the snapshot stays behind. The new drive holds the PC as it was when the copy started, so save your work first and leave your programs alone until it finishes.
  • Long jobs run as long as they need. The copy takes as long as the drive and the data take. Cancel ends it. A copy you stop partway leaves the new drive unusable until you run the move again. The snapshot goes away by itself soon after, within about ten minutes, and the new drive may stay offline until you bring it back online in Windows Disk Management.
  • Windows logs an unexpected shutdown the first time it starts from the new drive. It was copied while running, so to Windows it looks like a restart after a power cut. Nothing is wrong.
  • Windows Recovery starts switched off on the new drive. The recovery partition is copied, but Windows does not use it until you run reagentc /enable once from the new drive, in a Command Prompt run as administrator.
  • Some disks cannot be moved. A dynamic disk, a Storage Spaces disk, a disk with extended or logical partitions, a Windows that starts from a boot partition on another disk, and a pair of disks with different sector sizes are all refused, each with its reason.
  • Very large drives on MBR. The partition style stays the old disk's, and an MBR disk can use only its first 2 TB. To use more, convert to GPT afterward.
  • It is not a wipe. Old data on the new drive can remain in its free space, though no file system points at it. To clear a drive first, see Wipe a drive.
  • If it does not boot, attach the new drive to a working Windows PC and use boot repair on that disk.