Running out of space on your boot drive is one of those problems that starts as an annoyance — a warning popup here, a failed game install there — and ends with you uninstalling things you actually want to keep. Cloning your existing Windows installation onto a larger SSD solves it without a fresh install, and you keep every app, setting, and save file exactly where you left them. This guide walks you through the entire process: checking your drive layout, cloning with free software, expanding your partition to use the new space, and fixing the two most common boot problems afterward. Expect the whole job to take 45 to 90 minutes, most of it waiting on the copy.
Before we begin, a quick note on scope: these steps assume a standard UEFI system with Windows 10 or 11, a GPT disk layout, and a SATA or NVMe SSD as the destination. If your PC still boots in legacy MBR mode, the same tools work, but pay extra attention to the boot-mode notes in Step 4.
Before You Start
The single biggest cause of failed clones is skipping prep. Two minutes here saves an hour of troubleshooting.
| What you need | Why | Optional? |
|---|---|---|
| Destination SSD larger than your current drive | The clone copies everything, so the target must have equal or greater capacity. A 1 TB target comfortably holds a 500 GB source. | No |
| USB-to-SATA or USB-to-NVMe enclosure/adapter | Lets you connect the new drive while Windows runs, so you can clone without opening the case twice. Desktop users can instead plug the drive into a spare SATA or M.2 slot. | No |
| Cloning software (Macrium Reflect Free successor options, DiskGenius Free, or the SSD maker’s own tool) | Automates the copy, including the hidden EFI partition most manual methods miss. | No |
| External backup of important files | Cloning is reliable, but a mistake like selecting the wrong source disk destroys data. Copy Documents, saves, and anything irreplaceable to cloud storage or another drive first. | No |
| Second display or phone with these instructions | You will reboot during the process, and on-screen guides disappear. | Recommended |
| Philips screwdriver and an M.2 standoff screw | Needed if you are installing an internal M.2 drive; many motherboards ship with only one screw installed. | Yes, if using USB |
| Windows 11 users: BitLocker recovery key | If BitLocker is on, the cloned drive may ask for the key on first boot. Retrieve it at your Microsoft account page under Devices before you start. | Yes, only if BitLocker is enabled |
One more check: open Settings → System → Storage and confirm your source drive’s used space. Your new SSD must be at least that size. Also verify your boot mode by pressing Win+R, typing msinfo32, and looking for “BIOS Mode” — it should say UEFI for the steps below to apply cleanly.
Step-by-Step
Step 1: Connect the new SSD and confirm Windows sees it (5 minutes)
Install the new drive internally or connect it via USB adapter, then boot Windows. Right-click Start → Disk Management (or press Win+X and select Disk Management). The new disk should appear as “Not Initialized.” If prompted by the Initialize Disk dialog, choose GPT — never MBR on a UEFI system — and click OK. It will then show as “Unallocated.” Do not create any partitions; the cloning software handles that. If the drive does not appear, reseat the cable or try a different USB port before continuing.
Step 2: Shrink the source partition to speed up the copy (5 minutes, optional)
Cloning tools copy every allocated sector, so freeing dead space shortens the wait. Run Disk Cleanup (Win+R → type cleanmgr → select your C: drive → Clean up system files) and check “Previous Windows installations” and “Delivery Optimization Files” if present. You can also disable hibernation to remove a multi-gigabyte file: open Terminal as administrator (right-click Start → Terminal (Admin)) and run powercfg /h off. To undo this later, run powercfg /h on. Neither step is required, but removing 20–40 GB of junk can cut cloning time significantly.
Step 3: Run the clone (30–60 minutes)
Install and launch your cloning tool. In DiskGenius Free, for example: select Tools → System Migration, choose your current system disk as the source and the new SSD as the target, then click Start. Enable “Hot migration” if offered, which lets Windows keep running while the copy happens; the PC reboots into a preinstallation environment automatically to finish. Most tools include a checkbox like “Target disk is SSD” — leave it enabled so the tool aligns partitions correctly and skips defragmentation.
Make absolutely sure the source and target are not swapped. The target column should show the new, empty disk’s capacity. Confirm, start the migration, and let it run. Do not interrupt power during this phase; a laptop should be plugged in.
Step 4: Boot from the new SSD (5–15 minutes)
Shut down fully (hold Shift while clicking Shut down to bypass Fast Startup). If you cloned over USB, power off and swap the drives now: remove the old SSD or, ideally, keep it disconnected for the first boot so nothing can write to it. Power on and enter your firmware setup — usually Del, F2, or F12 during the vendor splash screen. Under Boot settings, set the new SSD as the first boot option. On UEFI systems, look for an entry named “Windows Boot Manager” associated with the new drive. If your system was legacy/MBR, check that CSM or Legacy Boot is enabled to match the cloned drive’s format. Save with F10 and reboot.
Windows should start normally. The drive will still show its old partition size — that is expected and fixed next.
Step 5: Extend the partition to use the full capacity (5 minutes)
Right-click Start → Disk Management. Right-click your C: partition on the new drive and choose Extend Volume. Click Next through the wizard, accept the maximum available space, and Finish. Your partition now fills the SSD. If Extend Volume is grayed out because recovery or OEM partitions sit between the unallocated space and C:, use a free third-party partition manager’s “Move/Resize” feature to slide the blocking partition to the end of the disk first, then extend.
Step 6: Clean up (10 minutes)
Re-enable hibernation with powercfg /h on if you disabled it. Check that TRIM is active: open Terminal and run fsutil behavior query DisableDeleteNotify — the result should be DisableDeleteNotify = 0. If it shows 1, run fsutil behavior set DisableDeleteNotify 0. Finally, verify storage sense is on under Settings → System → Storage so temporary files keep themselves under control on the roomier drive. Once you are confident everything works — give it a few days of normal use — reconnect the old drive, wipe it in Disk Management (right-click each partition → Delete Volume, then create a new simple volume), and enjoy a spare drive for games.
Verify It Worked
Run through this checklist after the first successful boot:
Correct drive: Press Win+R → msinfo32 → confirm “OS Name” is Windows and check Task Manager → Performance → Disk to confirm the model number matches your new SSD, not the old one.
Full capacity: In Disk Management, C: should show the new drive’s full usable size. A 2 TB drive typically reports around 1.8 TB usable — that is normal, not a problem.
UEFI boot path: In msinfo32, “BIOS Mode” should still read UEFI. If it changed to Legacy, the clone converted your partition table incorrectly — see the mistakes section.
Partition alignment: A quick sanity check: in an elevated Terminal, run wmic partition get Name,StartingOffset (or use PowerShell’s Get-Partition). Starting offsets should be multiples of 4096 bytes; most tools align to 1 MB (1048576 bytes), which is ideal. Poor alignment costs SSD lifespan and speed.
Apps and activation: Launch a couple of games and check Settings → System → Activation to confirm Windows remains activated. Hardware did not change, so it should be untouched.
Mistakes to Avoid
Booting the wrong disk. What causes it: both the old and new drives contain a Windows Boot Manager entry, and firmware picks the old one. How to check: in msinfo32 or Task Manager, see which disk model is active. What to do: enter firmware setup, disable or reorder the old drive’s boot entry, or simply disconnect the old drive. How to undo: re-enable the entry once you have confirmed the new drive boots independently.
BitLocker recovery prompt loop. What causes it: cloning changes disk signatures or boot measurements, so BitLocker demands its recovery key. How to check: a blue screen asking for a 48-digit recovery key at boot. What to do: enter the key from your Microsoft account, then suspend BitLocker (Control Panel → BitLocker Drive Encryption → Suspend protection) before any future firmware or boot changes. How to undo: resume protection after the system is stable; Windows re-seals the key to the new configuration automatically.
Cannot extend C: because unallocated space is “not adjacent.” What causes it: a recovery partition sits between C: and the free space at the end of the disk. How to check: the Extend Volume option is grayed out in Disk Management. What to do: use a free partition manager to move the recovery partition to the end of the drive, then extend. How to undo: not needed — moving it does not harm anything, and the recovery environment still works from its new location.
Copying the wrong direction and wiping the source. What causes it: selecting the disks in reverse in the cloning tool. How to check: the tool shows source and target capacities — the target should be the empty, larger drive. What to do: if you overwrote the wrong disk, stop writing to it immediately and run data recovery software from a different drive. How to undo: only partially possible, which is why the pre-clone backup in Before You Start matters.
Skipping TRIM verification. What causes it: some cloning environments boot with TRIM disabled and the flag persists. How to check: fsutil behavior query DisableDeleteNotify returns 1. What to do: set it back to 0 as shown in Step 6. How to undo: change the value back if a specific compatibility issue ever requires it — rare, and not recommended on modern systems.
FAQ
Do I need to reinstall Windows after swapping to a larger SSD?
No. A proper clone carries over the operating system, the EFI boot partition, installed programs, and license status. Windows remains activated because the motherboard — not the drive — is what activation is tied to. Only a drive interface change from MBR to GPT or vice versa can complicate things, and the cloning tools handle that automatically on UEFI systems.
Can I clone a larger drive to a smaller one, or only smaller to larger?
Both directions work as long as the used data fits on the destination. If your source has 700 GB used and the target is 500 GB, you must first shrink the source partition (or exclude large folders like game libraries) so the used space fits. Most cloning tools refuse to start rather than silently truncate, so you will know before any damage is done.
How long does migrating Windows to a new SSD take?
Plan on 45 to 90 minutes end to end. The clone itself is the variable: a SATA connection copies roughly 100–150 GB per hour of used data, while USB 3.2 or NVMe-connected targets finish in a fraction of that. Shrink dead space first (Step 2) to cut the wait, and keep the laptop plugged in throughout.
Do I have to keep the old drive, or can I format it right away?
Keep it untouched for at least a few days — ideally a week. If a boot entry, driver, or hidden partition turns out to be missing, the original drive is your instant fallback. Once you have confirmed boots, game launches, and Windows Update cycles all work normally, you can wipe it and reuse it as a second drive for your game library.
