Shattered.io’s “12 Steps, 60 Min” guide provides a useful starting point, but the stopwatch deserves less attention than the safeguards. Its own walkthrough acknowledges that copying a large hard drive can take hours. More importantly, BitLocker suspension is not decryption, and Clonezilla’s proportional-resizing option is not a universal shortcut for moving onto a smaller SSD. Those distinctions can determine whether an upgrade succeeds.
What this guide covers—and what Windows version matters
This procedure targets a healthy Windows 11 installation moving to a replacement drive in the same PC. Moving to a different motherboard, rescuing failing hardware, or preserving a complicated dual-boot configuration requires additional planning. Acronis distinguishes straightforward operating-system migration from scenarios involving different hardware and recovery requirements.
The Windows-version context has also moved forward. Microsoft lists Windows 11 version 26H2 as the 2026 Update, with general availability beginning September 29, 2026. Its release-health notice dated October 28, 2026 says the update is available to all eligible devices. Eligibility still matters: a storage upgrade does not make an otherwise ineligible computer eligible for Windows 11.
Windows 11 24H2 Home and Pro reached their servicing end date on October 13, 2026. That date does not apply to every edition; Enterprise and Education have a different lifecycle. Check both your version and edition rather than treating “24H2” alone as a support verdict.
Cloning and upgrading Windows should nevertheless be separate decisions. My recommendation is to complete any already-pending restart, establish that Windows works, and avoid combining an operating-system upgrade, firmware conversion and disk replacement into one troubleshooting puzzle.
Before starting: assemble the essentials
Have these ready:
- An SSD compatible with the PC’s slot, interface and physical dimensions.
- A suitable internal connection or external adapter/enclosure.
- A separate backup of irreplaceable files.
- Administrator access and dependable power.
- Your BitLocker recovery key, accessible from another device.
- Cloning software that supports your disk layout and encryption state.
- Recovery media and the tools needed to install the replacement drive.
Crucial’s installation guidance separates the connection, cloning and physical replacement stages; Microsoft separately emphasizes backing up the BitLocker recovery key. Treat those as prerequisites, not jobs to improvise after the old disk is disconnected.
Clone the drive safely in 12 steps
1. Back up before diagnosing or changing anything
Make an independent copy of documents, photographs, projects and other irreplaceable files. Open several files from that backup to confirm it is usable.
A clone and a backup image serve different purposes: a clone writes to another disk, while an image provides a stored recovery copy. Macrium specifically suggests an image when disaster recovery is the objective. Keeping the old disk is useful, but it should not be your only protection against selecting the wrong destination.
For an employer-managed PC, involve IT before changing storage or encryption settings. Recovery keys may be held in Microsoft Entra ID or another organization-controlled location rather than your personal Microsoft account.
2. Establish whether the source is healthy enough
Distinguish an upgrade from a rescue operation. If the source is producing read errors, repeatedly disconnecting or otherwise showing signs of failure, stop treating it as an ordinary migration.
GNU’s ddrescue manual recommends copying a failing drive and working on the copy rather than repairing the original filesystem first. Its mapfile supports resuming recovery without starting the entire operation again. For unique, valuable data, consider professional recovery before further experimentation.
This changes the order of operations: preserve readable data first, investigate corruption afterward. A clean installation can replace Windows, but it cannot recreate an unreadable family photograph.
3. Record the working boot configuration
Open Disk Management and inspect the existing system disk and its partitions. Microsoft documents checking a disk’s partition style through its properties and the Volumes tab. Record the current layout before changing it.
Do not convert MBR to GPT simply because an SSD is being installed. Microsoft’s MBR2GPT utility validates specific layout requirements, and a successful conversion requires switching the firmware to UEFI boot afterward. That is a separate operation with its own recovery considerations.
My practical recommendation is to preserve a working configuration during the migration. If conversion is necessary, plan and verify it separately instead of adding it as routine housekeeping.
4. Locate the recovery key and check encryption requirements
Before changing hardware, ensure that you can retrieve the 48-digit BitLocker recovery key. Microsoft identifies personal Microsoft accounts, work or school accounts, printouts and saved copies as possible locations. Match the recovery-key ID if multiple keys exist.
Then check how your cloning utility handles encrypted sources and destinations. Suspending BitLocker does not decrypt the volume. Microsoft explains that suspension leaves data encrypted but makes the unlocking key available without normal startup-integrity validation. Consequently, suspension alone does not satisfy a tool that requires an unencrypted source.
Do not assume that “protection off” means “data decrypted,” or that a clone will necessarily retain the source’s encryption state.
5. Suspend protection only when the workflow requires it
Where the selected migration procedure calls for suspension, Microsoft documents this elevated PowerShell command:
Suspend-BitLocker -MountPoint "C:" -RebootCount 2
The setting resumes protection after two restarts; it does not guarantee that those restarts correspond exactly to your migration stages. A value of zero leaves protection suspended until manually resumed. Keep the suspension window short and the computer physically secure.
Afterward, use Resume-BitLocker -MountPoint "C:" where protection was suspended and confirm the resulting state. If the destination was created unencrypted, resuming protection is not a substitute for enabling encryption on that destination.
6. Connect the SSD and identify both drives
Follow the computer’s service instructions when installing an internal drive. A supported USB adapter can provide the temporary second connection needed for migration; the replacement then moves into its intended internal position. Crucial’s installation process explicitly separates these stages.
Identify the source and destination by model and capacity, adding the serial number where available. Recheck those identities in the cloning application.
Avoid a preparatory diskpart clean command. A cloning application may already provide destination-partition controls, as Reflect X does. There is no benefit in adding an independent destructive operation merely to make a disk look “ready.”
7. Choose the tool and configure the complete migration
The main choices serve different needs:
| Tool | Appropriate use |
|---|---|
| Samsung Magician Data Migration | Migration to a supported Samsung SSD |
| Acronis True Image for Crucial | A supported Crucial-drive migration |
| Macrium Reflect X | A graphical workflow with partition-layout controls |
| Clonezilla Live | Offline cloning with explicit disk-size and layout constraints |
Samsung describes migration of the operating system, applications and user data to a new Samsung SSD. Acronis publishes a separate Crucial-edition guide; its compatibility conditions should not be confused with those of other editions.
For Reflect X, open Create Backups → Local Disks, select the source’s cloning action, and choose Select a disk to clone to. Use Copy Partitions or drag the required partitions into the destination layout. Preserve the system partitions, not just C:. Review the resizing choice and the complete destination diagram before proceeding.
8. Resolve smaller-disk limits before starting
A smaller SSD may work, but available file space is only part of the calculation. The software must also support the required partition resizing.
Clonezilla’s official advanced restore documentation describes -k1 proportional partitioning and -r filesystem resizing for a larger destination. Its smaller-destination override, -icds, carries an explicit warning: bypassing the size check does not prove the layout is safe. Do not select it merely because Windows reports enough free space.
Once the proposed layout fits, review the overwrite warning and start the operation. Keep power connected and allow the utility to complete its workflow, including any requested restart. Acronis notes that cloning active system operations can require a reboot.
9. Install the SSD and test it without the original
After successful completion, shut down and follow the manufacturer’s installation procedure. Put the replacement in its intended internal connection and disconnect the original for the first boot. Crucial’s installation guidance covers the transition from cloning to replacing the drive.
This is also a useful acceptance test: the SSD should demonstrate that it can start the PC without help from the original disk.
Keep the old drive unchanged. Shattered recommends retaining it for a week; treat that as a sensible observation period rather than a technical guarantee that every problem will appear within seven days.
10. Recover unused capacity when necessary
If C: remains smaller than expected, open Disk Management, right-click the volume and select Extend Volume when available.
Microsoft requires suitable unallocated space immediately after the volume on the same disk. If a recovery partition sits between C: and that space, the extension cannot proceed through the normal Windows operation.
Do not delete the recovery partition reflexively. Options include revising the clone’s layout, using a suitable partition-moving tool, or creating a separate data volume. Microsoft documents these alternatives when another partition blocks an extension.
11. Verify Windows, files and SSD-related settings
Use an elevated terminal to check Windows’ delete-notification setting:
fsutil behavior query DisableDeleteNotify
For NTFS, DisableDeleteNotify = 0 means delete notifications are enabled. This checks Windows’ setting; it is not a comprehensive test of SSD health or every component in the storage path. Microsoft documents the setting as controlling TRIM/delete notifications.
Shattered’s verification checklist also recommends checking recovery availability, opening important applications and launching games. That is more useful than celebrating a single successful sign-in. Include files from different folders and any libraries stored outside the Windows partition.
Finally, verify the destination’s encryption status and recovery-key accessibility rather than assuming both survived unchanged. Microsoft’s recovery guidance makes clear that access to the correct key matters when automatic unlocking fails.
12. Keep a rollback path and resume normal backups
Use the PC normally before repurposing the original. My suggested acceptance checklist is:
- Several successful starts with the original disconnected.
- Important files opening correctly.
- Essential applications and libraries working.
- Expected usable capacity.
- Encryption protection confirmed.
- A fresh independent backup completed.
These checks are recommendations, not a certification script. A green progress bar proves that software finished an operation; it does not establish that every workflow you depend on still works.
If the SSD will not boot
Start with the simplest questions: is the SSD detected, is it installed in the intended connection, and is the correct boot entry selected? Avoid immediately changing partition styles or storage-controller settings.
Microsoft’s BCDBoot can recreate boot-environment files from an existing Windows installation, but it is not a universal one-line repair. The Windows directory and system partition must be identified correctly; drive letters in a recovery environment must not be assumed from normal Windows.
There is another easily missed detail: Microsoft says specifying BCDBoot’s /s option prevents creation of the normal UEFI NVRAM entry and instead relies on default firmware behavior. That makes a copied command using an arbitrary D:\Windows and S: potentially incomplete for the actual problem.
If BitLocker requests recovery, use the saved key rather than assuming the clone is corrupt. Microsoft cannot recreate a lost recovery key; if neither the key nor a way to undo the triggering change is available, recovery options may involve losing the encrypted data.
The important takeaway
The best SSD migration is deliberately uneventful: preserve a healthy installation, minimize unrelated changes, verify the destination, and retain a fallback.
A twelve-step checklist is useful. A sixty-minute deadline is not. Spend the extra time identifying disks, protecting recovery keys and testing the finished installation. Those precautions matter far more than how quickly the progress bar reaches the right-hand edge.