The image restore route forks at one question: is the old disk trustworthy? Restore onto the same disk when the hardware is sound and only Windows was damaged. Restore onto a new disk when the disk itself is a suspect - or when you are upgrading to an SSD at the same time. This page makes the call, and covers the practical details of both versions.
Both versions use the same image and the same Macrium Reflect restore. What differs is the destination, and choosing it is really a judgement about the old disk's health. Get it right and the restore is the end of the story. Get it wrong - a fresh image laid onto a failing disk - and the SrtTrail loop returns within weeks, wearing a new disguise. Decide with the evidence below, then follow the notes for your version.
Choose this when the evidence clears the disk: the SrtTrail log named a corrupt file or a bad update, the disk is not old, there were no weeks of slowdowns or disappearing files, and disk checks report no hardware errors. The video's laptop is the template - software damage on sound hardware, fixed by writing the healthy image back over it. Practical notes: the restore replaces every partition in the image, so if the disk holds a separate data partition that is not in the image, confirm in Macrium's destination view exactly which partitions will be overwritten before you confirm - the default restores the partitions contained in the image and leaves you to check the rest. After the first boot, verify your files, then pick up the prevention routine from this guide so the next incident is equally short.
Choose this when the disk is a suspect: the log or chkdsk reported disk errors, the drive is old or has been slowing down for months, or the PC was heading for an SSD upgrade anyway and the crash simply chose the date. The job adds only the physical swap: fit the new disk, boot the same rescue USB, and select the new disk as the restore destination. Two practical points matter here. Size: the new disk must hold the image's partitions - restoring onto a smaller disk works only if the data inside the partitions fits, and Macrium lets you shrink or expand partitions during the restore by dragging their boundaries in the destination layout. Afterwards: keep the old disk untouched on a shelf for a week or two as a data source of last resort before wiping or discarding it - failed restores are rare, but regret is forever.
Do not guess - use the evidence gathered before the restore. The SrtTrail log verdict: a named corrupt driver or an update-timed loop clears the disk provisionally; a disk error or a no-root-cause verdict after many attempts indicts it. Chkdsk's report: file-system errors that fix cleanly are normal wear; bad sectors reported (the scan mentions bad clusters) are a replacement sentence. The disk's own health record: tools that read the drive's SMART data - including Macrium's own disk view and free health utilities - reporting reallocated sectors or a Caution or Bad status settle the argument instantly. And the story test: months of unexplained slowness before the crash means the crash was the disk's announcement, not a coincidence. When the evidence is genuinely mixed, choose the new disk - it costs a drive; choosing wrong the other way costs a second outage.
Then close the loop properly: the restored machine is healthy now, which makes today the perfect day to take its fresh image - the habit the closing case pages of this guide build into a routine.
Watch the video for the same-disk route performed live - and how fast a prepared image turns a disk decision into a short job.
Watch Full VideoUsually yes, provided the actual data inside the image's partitions fits on the smaller disk - empty space does not need to travel. Macrium Reflect shows the partition layout during the restore and lets you shrink partitions to fit. What cannot shrink below its contents is a nearly-full partition; if the source Windows partition itself holds more data than the new SSD's capacity, free space on the source or choose a bigger target.
A disk change alone does not normally disturb Windows activation, because activation is tied mainly to the motherboard. Replacing the disk and restoring the same machine's image generally reactivates automatically once online. Changing the motherboard is a different story - that can require reactivation, and it is one more reason the identical-laptop image pattern in the video restores onto the same machine or its twin.
No preparation is needed. The restore process writes the image's partitions onto the destination and overwrites whatever layout was there, after your confirmation. Just make sure you select the correct destination disk - match it by model and size in the restore screen, because the overwrite is total and applies to the disk you pick.