Group: Forum Members
I decided to move my C: drive containing Windows 10 to a new 512GB SSD because I was running out of space on my old 256GB SSD boot disk. Same PC, same motherboard. So, I created an image of my 256GB SSD, stored it, then copied it to the new SSD. Although no errors were reported, I seem to have the following problems, and I haven't found a solution in either the knowledgebase or the forum:
1. Now my 512GB SSD with the previously-created image only shows 256GB of space on it when I do a "disk properties." Reflect sure enough shows the extra 256GB of space in gray, but Windows believes there's only 256GB of total space on the thing.
2. After copying the image to the new 512GB SSD, I see that Windows Explorer is reporting a folder size of exactly 248,363,452 KB for every folder, and the original 256GB SSD does not have this property - no folder sizes are reported which is the way Windows normally does it.
3. Thinking this was a problem ReDeploy was designed to solve, I copied the image over to the 512GB SSD, then ran ReDeploy from the Macrium Windows 10 Rescue Disk I created. This seemed to have no effect - I still get the weird folder sizes, I am still missing 256GB of space on the new SSD, and I can't boot from the new 512GB SSD even if I was willing to put up with the disappearance of the extra space.
I suspect I'm supposed to be adjusting the partition sizes of the re-imaged disk (the 512GB one), but I'm not sure what I should be doing there. Also, the weird folder size issue makes me think the image copy over to the new hardware did not go as expected. Any guidance would be greatly appreciated.