I don’t know about you but we’ve been using GPT by default everywhere we can for many years now to get rid of the 2TB limit. The good news is that GParted works with both MBR and GPT disks, which is great.

I kind of hoping you’re not by now, but hey, I understand if you encounter them still. At the time of writing that’s 0.25.0-1 Make sure you grab the 圆4 version unless you’re still running older x86 edition of an operating system. With modern guest operating systems, you’ll want to use the latest 圆4 build of Gparted you can find. Note that the use cases for Gparted go way beyond this particular use case.

Luckily there is Gparted the open source partition editor. While the Windows inbox tools have gotten way better over the years we’re often left with lacking capabilities. When doing P2V, V2V or even P2P the need to deal with legacy partition / volume layouts and other disk housekeeping tasks often arises. Today we’ll show you how to fix virtual disk resizing issues with Gparted. I mentioned using Gparted to fix this particular issue in a previous blog post You cannot shrink a VHDX file because you cannot shrink the volume on the virtual disk. This cannot be used to allow shrinking a virtual hard disk, the unused space has to be at the need of the disk. One problem you can encounter is unused space that’s not located at the end of a virtual disk. In that article I also showed ways to deal with those challenges. Shrinking virtual disks has a few more potential issues to deal with which I discussed before. For this they need to be attached to a vSCSI controller.Įxtending virtual hard disks is something that rarely causes issues unless we don’t have enough disk space. In Windows Server 212 R2 and the VHDX format even allows us to extend and shrink the virtual disks on line. I’ve discussed resizing virtual hard disks in Windows Hyper-V before.

Gparted live usb firmware bug