Increase disk size when using checkpoints?

I ran out of virtual disk space and it seem there is not much I can do since I'm using checkpoints:



My checkpoints look like:
checkpoint 1
-> checkpoint 2
-> -> checkpoint 3
etc...
-> .. -> checkpoint 8

I only care about last check point.
Is there something I can do to make last checkpoint permanent by removing all other checkpoints, and will that allow me to edit virtual disk in the end?

Or is there even better way to increase disk and keep checkpoints somehow?

hsehestedt said:

You could revert to checkpoint 8, making it the current state, then delete all checkpoints.

I can delete all other checkpoints except last one, but the last one will still count as checkpoint right?
And since if it will count as checkpoint it still won't allow me to edit disk right?

So, assuming I delete all except last one, what exactly do I do with the last one if not delete it?
Do I just "apply it" and then delete it?

Thank you, I'll try this method as soon as needed.

What I did in the mean time and so far is installing programs to test and then revert to free up space.

Good point about dynamically expanding disk! I always do this for memory but not for disk heh.

I the end there is nothing to lose except old checkpoints which I didn't need so far anyway, so I won't cry
But I'll export VM just in case if I screw up something, thanks again!

hsehestedt said:

Had one more idea: You could also create a new VM with a larger virtual disk. Then image the original VM and restore it to the new VM. You won't have the checkpoints in the new VM and it's a little bit of work, but it's still another way to go. At least this way you keep the original VM with all the checkpoints until you know all is working to your satisfaction in the new VM.

I would also suggest creating the virtual drive as a dynamically expanding disk a good deal larger than you think you will need for now, just in case. Remember that a dynamically expanding disk only grows as space is needed, so creating it with plenty of space to start won't hurt anything and can save you this aggravation in the future.

I am afraid life is more complicated than that - every time you get updates, you can run disk cleanup to free space but unfortunately, the space feed up is not physically deleted from vhdx file (but will get reused when needed). The upshot is the vhdx files inexorably grow in physical size, particular with Dev Build upgrades.

This is a long standing issue with vhdx files. So making vhdx file much larger than you need bites you up the rear eventually.

The compact tool in vhd edit can be used to reclaim that space but it does not work well. You have to go through hoops and loops reducing size of vhdx to minimum, compacting before and after, then resizing vhdx file to reclaim space.

The easy way to reclaim space is to clone existing vhdx file to a vhdx file slight larger than contents of existing vhdx and then resizing new vhdx file afterwards.

@cereberus thank you for useful insight, I recall once having this issue, freeing disk in guest OS but not seeing an effect on vhdx. but I didn't bother nor ask questions probably I had plenty of space.