Thanks for the clarification.
What you want to do is not impossible, but made more difficult by Microsoft. This is not a VMware issue but a Microsoft issue. It occurs when expanding a virtual machine on any virtual platform or if you cloned a physical disk to a larger disk.
When you first installed Windows with a 75GB (or so) virtual disk, Microsoft put the recovery partition at the end of the 75 GB-ish disk at that time. When you expand a virtual disk in Fusion, you now have unallocated space (not another partition) after the recovery partition and continuing to the end of the newly expanded disk. Note that even though the disk size increased, none of the existing partitions (including the recovery partition) are touched.
The recovery partition now sits between the C drive and the free space. Windows Disk Management will not be able to expand the C drive in this case because it wants the free space to be right next to the partition (the C drive) that you want to expand.
You should be able to see this in Windows Disk Management, Disk Management should look something like this (in this order) after you've expanded the disk through Fusion :
- the C: drive partition
- the recovery partition (about 600MB)
- a large unused space of a bit less than 1.5 TB.
To allow Windows to expand the C drive, you need to:
- Disable the recovery partition using the command line
- Delete the recovery partition using the command line
- Expand the C drive in Disk Management, but leave 1GB or so empty space at the end of the disk
- Create a new recovery partition in Disk Management
- Set appropriate attributes on the hew recovery partitionusing the command line
- Enable the recovery partition using the command line.
There are two good videos on how to do this, depending on whether you are have configured your VM for BIOS or EFI firmware. See
https://www.youtube.com/watch?v=uGn7YGwmS1Y (EFI)
or
https://www.youtube.com/watch?v=hlNtLcFqfOo (legacy BIOS)