I've just cloned my 60Gb SSD using Macrium Reflect, cloning it onto a 120Gb SSD. Everything seemed to go fine, I formatted the 120Gb SSD before starting and then ran Reflect and let it do its thing.
Everything is working as it should but if I go into diskmanagement it shows I have 351Mb 'Unallocated' on the C:/ drive which is the new 120Gb SSD that I cloned the 60Gb drive to. Why is that and can I do anything about it? Or is it not worth bothering about given its only 350Mb?
The F:/ drive you can see in the screenshot is another 60Gb SSD that I've just installed Windows 10 Home onto in order to dual boot and have a play with W10 before deciding to move up to it from Windows 8.1. I notice it also has a similar 'Unallocated' bit listed, albeit a bit smaller. The other drives are all data or archive drives.
Screenie:-
Everything is working as it should but if I go into diskmanagement it shows I have 351Mb 'Unallocated' on the C:/ drive which is the new 120Gb SSD that I cloned the 60Gb drive to. Why is that and can I do anything about it? Or is it not worth bothering about given its only 350Mb?
The F:/ drive you can see in the screenshot is another 60Gb SSD that I've just installed Windows 10 Home onto in order to dual boot and have a play with W10 before deciding to move up to it from Windows 8.1. I notice it also has a similar 'Unallocated' bit listed, albeit a bit smaller. The other drives are all data or archive drives.
Screenie:-
