How to Fix “Hyper-V Cannot Delete Checkpoint: Catastrophic Failure (0x8000FFFF)”

Hyper-V is Microsoft’s built-in virtualization platform that allows you to create and manage virtual machines (VMs) on Windows and Windows Server. One of its most useful features is checkpoints (formerly called snapshots), which capture the state of a virtual machine so you can revert to it if needed. However, you may sometimes encounter the error “Cannot delete checkpoint: Catastrophic failure (0x8000FFFF)” when attempting to remove a checkpoint. As a result, the checkpoint remains stuck, merge operations fail, or the virtual machine becomes difficult to manage.

This error is typically caused by corrupted checkpoint files, damaged virtual hard disks (AVHDX files), insufficient permissions, Hyper-V service issues, storage problems, antivirus interference, or unexpected VM shutdowns during a merge operation. In some cases, disk errors, low storage space, or inconsistencies in the virtual machine configuration can also trigger the 0x8000FFFF error.

Fortunately, you can usually resolve the problem by restarting Hyper-V services, manually merging checkpoint disks, repairing the virtual machine, and checking the storage volume for errors. In this guide, we’ll walk you through the most effective methods to fix the “Cannot delete checkpoint: Catastrophic failure (0x8000FFFF)” error in Hyper-V.

How to Fix “Hyper-V Cannot Delete Checkpoint: Catastrophic Failure (0x8000FFFF)”

Before you begin, back up the virtual machine and its virtual hard disks if possible. If the VM contains important data, avoid manually deleting .AVHDX checkpoint files unless you’re certain they are no longer needed, as doing so can permanently damage the virtual machine.

1. Restart the Hyper-V Virtual Machine

A temporary VM state may be preventing the checkpoint from being removed.

1. Shut down the virtual machine completely.
2. Wait a few moments.
3. Start the VM again.
4. Try deleting the checkpoint.

Restarting the VM can clear temporary locks on checkpoint files.

2. Restart the Hyper-V Management Services

Hyper-V services may have become unresponsive.

1. Press Windows + R, type services.msc, and press Enter.
2. Restart the following services if available:
   • Hyper-V Virtual Machine Management
   • Hyper-V Host Compute Service
3. Open Hyper-V Manager again.
4. Retry deleting the checkpoint.

Restarting these services refreshes Hyper-V management components.

3. Shut Down the Virtual Machine Completely

Deleting checkpoints while the VM is running may fail in some situations.

1. Turn off the virtual machine.
2. Wait until its status changes to Off.
3. Delete the checkpoint.
4. Start the VM again.

A fully powered-off VM allows Hyper-V to merge checkpoint disks more reliably.

4. Check Available Disk Space

Checkpoint merging requires sufficient free storage.

1. Open File Explorer.
2. Verify that the drive storing the virtual machine has enough free space.
3. Free up storage if necessary.
4. Retry deleting the checkpoint.

Insufficient storage can interrupt checkpoint merge operations.

5. Check the Virtual Hard Disk Chain

A damaged AVHDX chain can prevent checkpoint deletion.

1. Open Hyper-V Manager.
2. Verify the virtual hard disk hierarchy.
3. Ensure all AVHDX files are present.
4. Check that no files are missing or moved.

Broken checkpoint chains often result in catastrophic failure errors.

6. Manually Merge the AVHDX Files

If automatic merging fails, you can manually merge the checkpoint disks.

1. Open Hyper-V Manager.
2. Select Edit Disk.
3. Browse to the newest .AVHDX file.
4. Choose Merge.
5. Merge it into the appropriate parent disk.
6. Repeat the process if multiple AVHDX files exist.

Be careful to merge the disks in the correct order to avoid data loss.

7. Run Check Disk on the Storage Volume

File system corruption can prevent Hyper-V from modifying checkpoint files.

1. Open Command Prompt as Administrator.
2. Run:

chkdsk C: /f

3. Press Y if prompted.
4. Restart your computer.
5. Allow the scan to complete.

Replace C: with the drive containing your virtual machine files if necessary.

8. Repair Corrupted System Files

Damaged Windows components can affect Hyper-V functionality.

1. Open Command Prompt as Administrator.
2. Run:

sfc /scannow

3. After the scan completes, run:

DISM /Online /Cleanup-Image /RestoreHealth

4. Restart your computer.

These tools repair Windows files required by Hyper-V.

9. Temporarily Disable Antivirus Software

Security software may lock virtual disk files during merge operations.

1. Temporarily disable your antivirus.
2. Delete the checkpoint again.
3. Re-enable your antivirus afterward.

Only perform this step if the virtual machine files are stored in a trusted location.

10. Update Hyper-V and Windows

Hyper-V reliability improvements are frequently included in Windows updates.

1. Open Settings.
2. Go to Windows Update.
3. Click Check for updates.
4. Install all available updates.
5. Restart your computer.

Keeping Windows updated helps prevent virtualization issues.

11. Export and Re-import the Virtual Machine

If checkpoint metadata is corrupted, exporting the VM may rebuild its configuration.

1. Shut down the VM.
2. Right-click it in Hyper-V Manager.
3. Select Export.
4. After the export finishes, import the virtual machine.
5. Verify whether the checkpoint issue has been resolved.

Exporting and importing can repair certain VM configuration problems without affecting guest data.

12. Create a New Virtual Machine and Attach the Existing VHDX

If the virtual machine configuration is severely corrupted, creating a new VM may be the best solution.

1. Create a new virtual machine in Hyper-V.
2. Choose Use an existing virtual hard disk.
3. Select the merged VHDX file.
4. Complete the wizard.
5. Start the new virtual machine.

This approach preserves the operating system and data stored inside the virtual hard disk while replacing the damaged VM configuration.

Conclusion

The “Cannot delete checkpoint: Catastrophic failure (0x8000FFFF)” error in Hyper-V is usually caused by corrupted checkpoint files, damaged AVHDX chains, insufficient storage, file system errors, or Hyper-V service issues. In most cases, restarting the Hyper-V services, shutting down the virtual machine, manually merging AVHDX files, and repairing Windows system files will resolve the problem.

If the error persists, check the storage volume for disk errors, export and re-import the virtual machine, or create a new VM using the existing virtual hard disk. Regularly deleting unnecessary checkpoints, maintaining adequate storage space, and keeping Hyper-V updated will help prevent similar checkpoint errors in the future.