Residual Hyper-V checkpoints remaining after differential disk merge
Residual virtual machine checkpoints remain visible in Hyper-V Manager after differential disk files (.avhdx) have been merged, and they cannot be removed using standard tools such as Hyper-V Manager or PowerShell.
Residual checkpoints after .avhdx consolidation are typically caused by metadata desynchronization between the disk files and Hyper-V configuration. This can happen, for example, when differential disks are manually merged using PowerShell while Hyper-V Manager is still open — in this case, the .avhdx files are correctly merged into the base .vhdx file, but the checkpoint metadata is not removed. Other scenarios can also lead to the same issue, but this is one of the most common.