- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a Windows 10 VM which is almost maxed out on space. It was originally created as a 100GB drive. With the VM powered off, I extended the HDD to be 200GB. When I boot up the VM and go into windows Disk Management, I can see unallocated disk space of 100 GB but I cannot extend the C: partition since there is a "Healthy (Recovery Partition)" between the two. I can do nothing with the "Healthy (Recovery Partition)".
Why did VMWare create the partition at the end where I do nothing with it? Any help would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don’t think this has anything to do with Workstation, Windows decides where to create partitions within a disk, whether that disk is physical or virtual.
You need to find a safe method of deleting the recovery partition. If that’s possible.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can download the GParted ISO and boot up the VM from the ISO. You then move the "Healthy (Recovery Partition)" (and any other partitions for that matter that come in between) using GParted so that the unused/unallocated block is next to the volume that you want to extend. Once moved, reboot the VM back to Windows 10 and you can use diskmgmt.msc to extend volume.
If you want to be cautious, back up the VM first before moving the partition(s) with GParted so that you have something to go back to in case something goes wrong.