Windows 10: Why Hyper-V 2019 splits checkpoints into additional VMs after upgrading configuration version?

I am in the midst of upgrading my Hyper-V environment from Windows 2012 R2 old to Windows 2019 new. Moving virtual machines VM from the old system to the new system works flawlessly. But since the version of VMs from the old version 5.0 is lower than then new 9.0, there is an option to Upgrade Configuration Version when I right-click on VMs within Hyper-V Manager in the new system. Please see the attached image. *If a VM does not have checkpoints, upgrading the configuration version isn't an issue. **However, when there is one checkpoint or more, after upgrading the configuration

:)

 

Hyper-V 2019 Checkpoint Operations fails after a day

We backup our Hyper-V 2019/16 servers containing couple of virtual machines, with Unitrend backup system, which requires checkpoints to be able to back the VM's. When we tested to create checkpoint, it would give the error "An error occured while attempting
to checkpoint the selected virtual machines. The operation cannot be performend while the object is in use". When we check the logs we get the following Event ID: 19100, 18012, 18014.
Normally when we reboot the Hyper-V servers , we are able to create checkpoints for a day or so after which the same issue recurs.

We have used ICACLS to grant the "NT Virtual Machine" user of each VM full access, and ensured that the VHD files and checkpoints are in the same folder. We also ovserved that the .avhdx files which are created would remain and are not able to automatically
get merged to the parend .vhdx file.

This is happening al all our Hyper-V 2019 servers which are part of a domain.

 

Virtual machines were lost after upgrading hyper-v configuration version

Hello,

Since your issue involves lost virtual machines after upgrade to the Hyper-V configuration version, we recommend posting on this
page to get advanced
suggestions from our IT Pro users in TechNet. You will find more people with expertise over the matter you are working on in order to get the appropriate steps required to address this type of concern.

Feel free to write again should you have additional questions.

Regards.

 

Creators Update and Hyper-V - Upgrade Configuration Version

Re-installing Hyper-V role did not help.

Using powershell command Get-VMHostSupportedVersion I can see new version available (which is 8.1).



And if I create new VM using command New-VM -Name test -Version 8.1, new VM is created with version 8.1:




But I still cannot upgrade my existing VMs to new configuration version.