大网数据广告活动
Hyper-V与虚拟化

Can't Restore VM From Checkpoint in Hyper-V on Windows Server 2016

· 52CE 我爱测

Discusses how to fix an issue in which you can't restore a virtual machine from a checkpoint in a Hyper-V environment that runs on Windows Server 2016.

Summary

This article discusses an issue in which you can't restore a virtual machine (VM) from a checkpoint in a Hyper-V environment that runs on Windows Server 2016. The issue typically occurs after an operating system (OS) upgrade, and it often involves checkpoint corruption or misalignment.

Symptoms

  • Error message: "An error occurred while attempting to export the data from checkpoint."
  • The VM can't be restored from the latest checkpoint.
  • Multiple checkpoints are present, but none can be used to successfully restore the VM.
  • Data loss is reported, requiring urgent recovery.
  • The issue begins immediately after an OS upgrade, such as from Windows 10 to Windows 11.
  • Hyper-V VM Management Service (VMMS) admin logs and checkpoint chain integrity are analyzed, revealing irregularities.
  • Attempts to merge checkpoints fail, causing concerns about possible data loss.

Cause

The issue occurs because of one or more of the following reasons:

  • The checkpoint wasn't merged correctly before you ran the OS upgrade, or the upgrade was run without using the latest checkpoint in the VM.
  • Changes were made directly to the original virtual hard disk (VHDX) file after creating a checkpoint, causing a misalignment in the checkpoint chain.
  • The VM became inconsistent with the checkpoint structure and caused corruption or breakage in the chain.
  • A corrupted or missing VM configuration file further contributed to the inability to restore the VM from the checkpoint.

Resolution

To resolve the issue, follow these steps:

  1. Back up VM files:

    • Before you try any recovery steps, back up all checkpoints and VHD files to a secure location. This step minimizes the risk of permanent data loss.
  2. Inspect the checkpoint chain:

    • Run the following PowerShell script to verify the chain of differencing disks:
    Get-VHDChain -Path <path to vhd file></path>
    
    • Analyze the output to identify any inconsistencies or corruption in the chain.
  3. Manually merge checkpoints:

    • Try to manually merge the checkpoints by using PowerShell commands. For example:

      Merge-VHD -Path <Path to AVHDX file> -DestinationPath <Path to merged VHDX file>
      
    • Notify the customer of potential risks, including data loss, before you proceed to merge.

  4. Re-create the VM:

    • If merging checkpoints fails, re-create the VM by using the backed-up files. Make sure that you configure the new VM to point to the merged VHDX file.
  5. Follow proper checkpoint management practices: - Always merge checkpoints before you perform OS upgrades. - Avoid direct changes to the original VHDX file if checkpoints exist. - Regularly maintain and verify checkpoints to make sure of integrity.

  6. Confirm resolution:

    • After the recovery steps are completed, verify with the customer that the VM is operational and data was restored.

By following these steps and recommendations, you can resolve the checkpoint restoration issue and prevent similar problems in the future.

Data collection

Before you contact Microsoft Support, you can gather the following information about your issue.

  • Hyper-V VMMS admin logs. These logs can be collected from the Event Viewer under Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS.
  • Results from running the Get-VHDChain PowerShell command to inspect the integrity of the VHD chain.
  • Any additional error messages or logs that provide insight into the checkpoint issue.

References

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: kaushika-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。