Fresh install when transferring from an old computer to a new one. The hardware is likely to be different, so you can’t rely on the old DLLs, registry settings and other configurations to still work! Fresh install sorts all that out. Cloning doesn’t. The problem with a fresh install is the user has to sort out data migration and upgrading the applications.
Clone when replacing a hard drive in the same computer with a new SSD. In this simple case, cloning transfers the entire system including user installed applications and user data as a unit, job done. But only clone if nothing else has changed, otherwise the O/S boots, tries to talk the old way to new hardware, and is liable to fall over in a mumbling heap! If anything more than a disc drive has to be upgraded, perhaps a new network card, proceed in two steps. Clone to the SSD first and confirm the system still works; then fit new network card and drivers and reboot. This the OS should handle as normal business, fingers crossed!
Richard mentions many new SSDs come with cloning software: if so use it! Otherwise:
- I didn’t find anything nasty in clonezilla last year and it worked painlessly. It’s open source so you can check it for nasties.
- I also use ‘dd’ which is a bog standard UNIX utility, hence secure. Simple enough when both discs are the same size, but essential to Read The Flipping Manual. It’s a command line tool with super powers, so don’t get the magic incantations wrong! GUI cloners are far more straightforward – my preferred method.
- clone apps are like any other software in the Windows firmament! Downloading from a dodgy website risks malware galore. Find someone reputable and put the download through a virus checker before running it!
If it all goes horribly wrong, fresh install. You did take a full backup, didn’t you…
Dave
PS found my backup system is broken a month ago and haven’t had time to fix it. I like to walk on the wild side!