Newly imaged system not recognizing any unallocated space? (smaller image clone to larger drive)

1

I built a Windows 10 system image in VMWare Workstation that I gave a size of 64GB, so the image could be cloned onto multiple devices of any larger size. I was told that after cloning onto the target machine, I could simply open diskmgmt and refresh and it would pick up the true size of the hard drive. I have cloned this image onto my first target machine but it is not working. Disk Management is not seeing any unallocated space. It shows one EFI partition of 200MB and a C drive of 63.68GB and nothing else. This laptop has a 250GB drive, it should be showing me 186 GB of unallocated space?

EDIT: A workaround "solved" this. I actually shrunk the disk first, by 1024MB, and after that action it suddenly picked up that there was ~170 GB of unallocated space, at which point the C drive could be expanded. But why was this strange workaround necessary?

Vermont1981

Posted 2019-07-26T15:44:52.733

Reputation: 31

Have you cloned the disk via boot from Windows 10 install media, as described here?

– harrymc – 2019-07-26T15:52:37.703

@harrymc - No, this was using clonezilla for deployment to multiple machines in a volume licensed environment. – Vermont1981 – 2019-07-26T16:55:56.473

Clonezilla is a Linux-based utility that sometimes has problems with Windows, so is not the ideal tool. Apparently it cloned your disk, just did it too exactly. By shrinking the disk you caused Windows to interrogate it for its architecture, so discovering the missing space. Clonezilla should have done it for you, but as I said it's not that good with Windows. – harrymc – 2019-07-26T17:18:19.620

Answers

2

A workaround that fixes this is to first Shrink the disk by any amount (for instance 1024MB). The skrinking action forces diskmgmt to see the full size of the hard drive, at which point you can expand into the full unallocated space.

Vermont1981

Posted 2019-07-26T15:44:52.733

Reputation: 31

Trying to expand the system disk with Windows10 I had the same exact issue:

  • bought new larger ssd (480gb vs 128gb)
  • cloned 128gb system disk over the 480gb using CloneZilla
  • put the 480 disk in place of the 128, removed the 128 one and rebooted.
  • everything worked perfectly, but both diskpart and diskmanagment tool did not see the extra 350 gb
  • tried the SHRINK trick inside disk part (I reclaimed just one MB) and magically the space appeared inside the disk managment tool.
    • < – ALoopingIcon – 2019-08-02T05:12:05.893

Asked: 2019-07-26T15:44:52.733

Viewed: 36 times

Active: 2019-07-26T21:34:01.023