If a Windows partition leaves unallocated space that you cannot merge
The other day I faced this strange problem. Having replaced my 120GB Kingston SSD with Samsung 860 Evo 500GB SSD, I used Macrium Reflect and a Disk Image I had taken with it to clone my old disk and use all my programs in the new one without having to install or configure anything at all. Cloning lasted 24 minutes (double the time needed for taking the image).
I closed Macrium, entered BIOS and changed the boot order giving priority to the new Samsung SSD. Everything worked fine, Windows opened, all my programs where there alive and kicking — however, instead of 500GB the new disk was reported as having 111GB, which was the available space in my old Kingston SSD!
Of course I understood that cloning “transferred” even the drive’s capacity, but I guessed this could be changed easily from Windows Disk Management, by extending the C partition to the unallocated space. No joy! Disk Management let me only use the unallocated space to create a new volume — no merging possible! I opened Macrium Reflect in case some help was offered on such issues. No joy! Then I thought about using a Partition Manager, and resorted to AOMEI Partition Assistant Standard.
AOMEI’s program is easy to use and reliable, it offers a commercial version but the free (Standard) one is more than enough for such jobs. The program immediately showed the condition of the C with the unallocated space and offered to merge this space with the rest of the volume. I chose this option, everything was configured instantly and I only had to restart my PC. When I was in Windows again, all space was available in my new Samsung SSD. — You may also like to check this post if you don’t know how to migrate Windows to SSD easily and safely, without reinstalling anything.