How to Physically Install a SSD and Transfer the Operating System
Introduction
If you never owned an SSD, you have missed something. Yes, they are not cheap, but Dollar per Dollar there is no other piece of hardware that can give you as much additional performance than an SSD.
Because SSDs are expensive, their current use is for placing the operating system. That’s how you get the best mileage. Although XP and Vista can be installed on SSDs, it is recommended to use them for Windows7, which is the first system to support Trim.
For desktops, an SSD with a 60GB capacity is usually sufficient. The user data can be moved to the HDD – I will explain the procedure later. Should you have very large programs, e.g., games, you should move their program files during the installation of the game to the HDD too.
For laptops, the situation is more complicated because you usually have only one disk bay. I use 80GB and 90GB SSDs on my laptops. In addition, I use the HDD that I recovered from the laptop after I installed the SSD in an external USB enclosure. But, if you move around a lot with the laptop, that may not be so convenient and a bigger SSD (120GB or 250GB) may be in order (budget allowing).
Hardware Installation
For a desktop, you will need a bracket if it is a 2.5” SSD (like most today). But, there are also 3.5” SSDs that will fit without adaptor brackets into the disk bays. You also need a cable to attach the SSD to the motherboard. For electricity, there is usually an extra plug at the PSU which you can use for the SSD’s.
Once you have all those bits, you can install the SSD in an available disk bay – or if none available, some self-adhesive Velcro will also do. The SSDs are light and do not produce any vibration or heat.
For a laptop, you need an external enclosure that attaches to a USB port. That will allow you to make the initial SSD setups. The one I linked attaches via USB2 and eSata, which may be practical later to use as external drive with the HDD that you recovered from the laptop. Also for hot swapping bare bone HDDs. But there are cheaper enclosures for USB2 only and also some that allow attachment to USB3.
Transfer the Operating System
There are two ways to transfer the operating system from your current HDD to the SSD:
1. The Geeky way which comes for free and
2. The easy way that costs $19.95.
1.The Geeky way requires the following steps:
Prepare the SSD – You first have to initialize the SSD to create the MBR. You can do that with Disk Management or with this program (which you will need later anyhow).
Then you need to align the SSD and define an active partition on it. You use an elevated Command Prompt with the following commands:
Diskpart
List disk
Select disk n (where n is the number that was given for your SSD in List disk)
Clean
Create partition primary align=1024
Format fs=ntfs quick
Active (assuming you want to install an OS)
Exit
Note: If you are more comfortable working with Disk Management, you can also define a primary active partition with Disk Management. On a SSD, the partition will be automatically aligned by 1024.
If you want to verify that the alignment is correct, you use these commands:
Diskpart
List disk
Select disk n
List partition
You should see a result like this:
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 59 GB
1024 KB - but 64KB or any number divisible by 4 is also good. The offset has to be divisible by 4.
In Windows7, you may have the 100MB active boot partition. The easiest way to deal with that is to move the bootmgr to the C: partition using EasyBCD. That you do on your HDD before you transfer anything to the SSD. Then you do not have to worry about it and you need only transfer the C: partition to the SSD.
But if you care to keep the 100MB partition, then the partition you just created on the SSD is for that 100MB partition. The next step is to shrink the partition you just created to a 100MB size (make sure it is not any smaller). With Disk Management you will have trouble to do that. I recommend this program for the operation.
From the free space you gained, you create the C: partition for the OS. This partition must not be active and need not be a primary (because the 100MB partition contains the boot manager).
Alternatively and easier is if you first create the 100MB partition with these commands:
Diskpart
List disk
Select disk n (where n is the number that was given for your SSD in List disk)
Clean
Create partition primary size=100 align=1024
Format fs=ntfs quick
Active
Exit
Note: The unit in the size parameter is MB
After this action you can use Disk Management to create the C partition from the remaining unallocated space. That can be a logical partition.
If there is no 100MB partition, things are easy. The partition you created with Command Prompt will receive the C partition including boot manager and all.
There may be more partitions on your factory HDD – e.g., the Recovery partition and a Tools Partition. Those you should not transfer to the SSD because of space constraints. I would back them up – e.g., with an imaging program. The Recovery Partition you can also burn to DVDs.
The OS transfer
This is done with an image. There are a variety of free imaging programs (e.g., the free editions of Macrium, Paragon, Acronis, etc.) that are suitable for the task. You can also use the Windows7 imaging, which has the advantage that it deals with the 100MB active boot partition automatically. Disadvantage is that you never know exactly what it does.
You image your partitions to an external disk (you may have to assign a drive letter to the 100MB partition so that the imaging program can identify it) and then pull the images back in to the SSD (using the bootable recovery program of the imaging program).
The recovery is partition by partition. So you have to make separate runs for the 100MB partition (if any) and the C: partition.
Note: Many free imaging programs cannot shrink the originating partition to fit into the usually much smaller C: partition on the SSD - even if the amount of data in that partition would fit. In that case you will need to shrink the C: partition on the HDD prior to imaging it. The HDD C: partition must be smaller or equal in size to the designated partition on the SSD. For that operation I also recommend this program because Disk Management might not be able to shrink it enough. Note: Free Macrium can image to a smaller disk if the data fits.
It is, of course, understood, that the amount of data on your HDD C: partition must not exceed the capacity of the designated C: partition on the SSD. Should you have more data on your HDD C: partition than the size of the SSD C: partition can hold, I suggest you first create a data partition on the HDD system and move the user data there. Here is my video tutorial that explains how this is done. When you finally are on the SSD system, you then right click on the user folders in the data partition (Documents, Pictures, etc.) and Include them into the appropriate library. That approach does not require you to move the user folders later.
Next step is to change the boot sequence in the BIOS to set the SSD as second boot device (leave the CD/DVD reader as first boot device) and, hopefully, your system will boot.
2.The easy way for transferring the OS requires you to purchase this program. It does everything for you – alignment, deals with the 100MB partition, transfers C:, shrinks the originating partition, etc. All you will have to do is change the boot sequence.
Note: Before you activate the SSD, it is recommended to set the BIOS to AHCI. Best time to do that is just before you change the boot sequence. Once Windows7 is running, you make the corresponding settings in the OS. Here is a tutorial on how to do that.
Many people claim that there is a significant performance gain with AHCI. I, however, did not see that. But it may be different from system to system.
Settings after the OS transfer
Disk Defragmentation makes no sense on an SSD. For a laptop, go into Services, navigate to Disk Defragmenter, right click on it and go to Properties. Here you set the service to Disabled.
For a desktop, you may want to disable defrag in the Disk Defragmenter and only for the SSD so that the remaining HDDs can still be defragmented.
Note: As long as Defrag Service is turned off, you cannot shrink any partition. The partition shrink process requires the Defrag service. If you need to shrink a partition later, turn the Defragmentation Service temporarily on.
Hibernation File – most of us do not use Hibernation, but Sleep instead. But, the hiberfile takes precious space on your SSD – to the same tune as the size as your RAM. To get rid of it, run the following command in elevated Command Prompt: powercfg –h off. If you ever want it back, it is powercfg – h on.
Superfetch – many “experts” suggest to turn Superfetch off. I think that is not appropriate. Fetching a program or data from RAM is still a lot faster than fetching it from a disk – even from an SSD.
There are no other settings that are necessary. On the SSD forums you will find a lot of tweaks. I recommend you stay away from them.
Move the user folders to the HDD
To move the user folders to the HDD is very simple. Create a Data partition on the HDD. Define folders in that partition – e.g., Documents, Music, Pictures, etc. One for each folder you want to move off the SSD. The name of those folders can be anything. The system will rename them anyhow. It is just more obvious if you call them by the same name as the originating folders.
Then, open the Explorer and right click on, e.g., My Documents folder (not the Documents Library) in the left pane. Go to Properties and click on the Location tab. Here you click on Move and navigate to the corresponding folder in your Data Partition on the HDD. Then you Select that folder and Apply it.
Very Important: You must move the SSD folder to the corresponding Data Partition folder – NOT to the root of the partition itself. That would create a mess.
Last edited:
) so I did a wee test to see if it actually could be done. I have a 2TB HDD in my computer (F
that currently has only an empty folder in it. I added a small .jpg to the drive (ironically, one of a cat walking away from an explosion; it was the first nonsensitive file I saw). I then plugged a 120GB spinner I rescued from an old netbook several years ago into my 2.5" swap bay. I set up Macrium Reflect to clone from the considerably larger F: drive to the considerably smaller drive. I got this message before setting things in motion:
It simply refused to show up in this menu until I went back and reconfigured to IDE. Then it booted and all seems well.