How to Merge Microsoft Hyper-V Virtual Machine Checkpoints

preview_player
Показать описание
Hyper-V uses checkpoints to save the state of a VM and are similar to snapshots used with other virtualization platforms such as VMware and VirtualBox. Sometimes these checkpoints will give you issues such as not being able to start your virtual machine or perform hard disk related tasks. When this happens you can simply merge the checkpoint and see if that fixes the issue for you. Hyper-V on Windows 10 tends to make checkpoints automatically even before you get a chance to disable the feature.

If you get an error starting your VM that says something similar to "synthetic SCSI controller failed to power on with the error the system cannot find the file specified" then you can edit the VMs settings and point the disk file to the vhdx file rather than the avhdx file that it might be looking for

Check out our book (Microsoft Hyper-V Desktop Made Easy) that is designed to take your virtualization skills to the next level!

#hyperv
Рекомендации по теме
Комментарии
Автор

I rarely comment on videos but thank you! You saved me a long time of searching online.

justindobner
Автор

Thank you, this made it extremely simple. Was dreading the use of a command line option I saw elsewhere.

terminalfx
Автор

Thanks, buddy. You've saved my life and made my HDD free again :)

mirosawh.
Автор

Hi... the VM have to be off for this process?

gabrielmojica
Автор

Thanks for the concise video. My machine has checkpoints disabled as well, but it has created many, what seems to be orphaned AVHDX files despite the setting. Assuming I can't just delete these, do I start with the oldest or newest AVHDX and merge back into the VHDX?

chrisjohnson
Автор

The VM can't start now, look at your hard disk name and settings hard disk : the name is different

SebastienM-wong
Автор

Or you can just skip all of that and delete the checkpoints one by one from the Hyper-V manager and it will merge them automatically... best to turn of the VM to speed up the process... with what you did and didn't show you will have to delete the checkpoint tree in Hyper-V and remove the virtual drive and add it back to work again... take note that if you have a backup program making checkpoint outside of Hyper-V the neither will work and it's PowerShell time... 😎😎😀😀

DAHCKRAM