Cloned Windows 10 from SSD to M.2 storage has revealed a large recovery partition.
Cloned Windows 10 from SSD to M.2 storage has revealed a large recovery partition.
I was going from a 120GB Samsung 2.5'' SSD to a 256GB m.2 SSD. Used Acronis True Image 2015 HD. Process went normally. After removing the Original drive - I went to increase the size of the Destination drive as usual. However instead of available unpartitioned space - there's a big Recovery Partition (matches the size of the original drive, i think). Attaching the image of the new drive - from the Disk Management screen. There have to be people that had a similar experience! Seems like a pretty standard update for those going to m.2 on their boot drive. Checked the Disk Cleanup section in case there's something like a "windows.old" cleaning, but no luck. So how did you manage to free up that space?
Ensure a fresh setup after transferring files to a new drive.
It's not my initial encounter with cloning. It usually proceeds effortlessly. This is my first time moving from a m.2 to an SSD. I've mostly assisted friends in transferring their 500GB HDD to a 120 SSD without any problems.
I understand what you're referring to, but these issues usually involve hardware identifiers and sometimes require re-syncing in apps like Evernote since they treat earlier versions as different devices. I didn't receive any follow-ups, probably because they don’t rely heavily on software and aren’t aware of these kinds of problems.
Updated instructions removed the partition via diskpart. Restarted to see if Windows 10 reported issues—rebooted without problems. The unallocated area didn’t allow the Extend Volume feature for the boot partition. (Attempted to create a Simple Volume, functioned fine for testing, but didn’t meet my requirements.) Any suggestions? Including the diskpart output might help clarify the situation.
I might consider using gparted or a more advanced partitioning utility that can manage this. It should be capable of resolving issues more effectively than the standard Windows tool, which often struggles with shrinking or relocating partitions.
It's really restricted. I usually steer clear of those advanced tools since their outcomes often come with... complex and risky results. But with the original drive available, I might try something tomorrow to find out what happens. (If no clear answer is given by someone experienced)