After a couple of reboots, I was able to delete the snapshots
Hyper-V Cannot Delete Checkpoint -Catastrophic failure (0x8000FFFF)Virtual machine failed to generate VHD tree
I have a VM with 3 checkpoints and I need to delete checkpoints in order to have only 1 vhdx. When right-click on the oldest snapshot, delete, I get
Remove-VMSnapshot : 'Kubernetes' failed to remove checkpoint. Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Virtual machine failed to generate VHD tree. 'Kubernetes' failed to remove checkpoint. (Virtual machine ID 20712F4D-1372-406D-9A0B-DD26C5002894) Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID 2BB59E44-2964-4CDF-9110-A Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF')
I need to delete all checkpoints in order to have only 1 disk to export the machine as a backup
I tried with powershell as admin it did not help. I googled and found sone posts talking about restarting hyper-v service or start the VM and tried to delete and others but it did not help.
Thanks for your help
Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
2 answers
Sort by: Most helpful
-
Chance Maurice Niyonzima 825 Reputation points Independent Advisor2026-11-06T19:05:44.85+00:00 Hello Salam,
Thank you for posting your question on the Microsoft Windows Forum!
Thank you for providing the screenshot and error details. The screenshot helps confirm that Hyper-V is failing before it can build the VHD checkpoint chain, which is why the checkpoint merge cannot begin.
The most important finding is the error:
Cannot delete checkpoint: Catastrophic failure (0x8000FFFF) Virtual machine failed to generate VHD treeThis is significant because Hyper-V normally generates the VHD tree by traversing the parent-child relationship between the .avhdx checkpoint disks and the base .vhdx file. If Hyper-V cannot build that chain, it often indicates a problem with the checkpoint disk hierarchy, missing references, damaged metadata, or inaccessible virtual disk files.
Highest-value next step
Before attempting any manual merge operations, I would verify the integrity of the checkpoint chain.
For the affected VM, could you check the VM storage folder and identify:
The base .vhdx file All associated .avhdx files Whether any checkpoint files appear missingI'd also recommend inspecting the parent relationships of the AVHDX files.
You can do this from PowerShell:
Get-VHD -Path "C:\Path\To\Checkpoint.avhdx" | Select-Object Path, ParentPathor:
Get-VHD -Path "C:\Path\To\BaseDisk.vhdx"The goal is to determine whether Hyper-V can still resolve a complete parent chain for every checkpoint disk.
Additional check
Since the VM appears to have multiple checkpoints, I'd also be interested to know whether:
The VM starts successfully The VM can be exported Hyper-V reports any errors in Event ViewerIn particular, please review:
Event Viewer → Applications and Services Logs → Microsoft → Windows → Hyper-V-VMMSand:
Hyper-V-Workeraround the time the checkpoint deletion fails.
One clarification
Have any of the following occurred recently?
Storage migration Manual movement of VHDX/AVHDX files Backup software interaction with Hyper-V checkpoints Host crash or unexpected shutdownOne reason I ask is that "failed to generate VHD tree" is frequently associated with checkpoint chain inconsistencies created after storage operations or interrupted checkpoint merges.
Before making changes
Because you mentioned that your goal is to reduce everything back to a single VHDX for backup purposes, I would recommend not manually deleting any AVHDX files until the parent-child relationships have been verified. Manual deletion can make recovery significantly more difficult if the checkpoint chain is already inconsistent.
If you can share:
The output of Get-VHD for the AVHDX files The VM configuration version Any Hyper-V VMMS or Worker eventsI can help determine whether this is a broken checkpoint chain or a storage-related inconsistency and advise on the safest next step.