Hyper-V Reference Point / Production Checkpoint failures on Windows Server 2025

Koller Zoltán 0 Reputation points
2026-06-30T08:10:26.8433333+00:00

Dear Microsoft Support,

We are experiencing intermittent Hyper-V Reference Point / Production Checkpoint related failures on a newly deployed Windows Server 2025 Hyper-V host.

Environment

  • Host OS: Microsoft Windows Server 2025 Standard
  • OS Build: 10.0.26100 (Build 26100)
  • Latest cumulative updates installed
  • Server: Dell PowerEdge R760xs
  • RAID Controller: Dell PERC H755
  • BIOS and firmware updated to the latest available versions
  • Hyper-V Configuration Version: 12.0

Virtual Machines

The issue has been observed on multiple virtual machines, including:

  • Linux Generation 1 virtual machines
  • Windows Generation 2 virtual machines

Therefore, the issue does not appear to be guest OS or VM generation specific.

Symptoms

Hyper-V intermittently fails during operations that require Production Checkpoints / Reference Points.

Previously, when Hyper-V Replica was configured, replication occasionally failed with Reference Point related errors.

The same behavior occurred before any third-party backup software was installed, therefore the issue is not related to backup software.

Hyper-V Replica has since been completely removed, however we are still concerned that the underlying issue may still exist.

Diagnostics performed

We have verified the following:

  • No active Hyper-V Replica configuration
  • No orphaned AVHDX files
  • No remaining checkpoints
  • No checkpoint chain corruption
  • VHDX files are healthy
  • Fragmentation = 0%
  • No NTFS errors
  • No storage errors
  • No RAID controller errors
  • BIOS and firmware are current
  • Hyper-V reports all VMs as healthy and running normally

PowerShell confirms:

  • ReplicationMode = None
  • ReplicationState = Disabled
  • ReplicationHealth = NotApplicable

Questions

  1. Are there any known issues in Windows Server 2025 related to Hyper-V Reference Points or Production Checkpoints?
  2. Are there any known issues affecting both Linux Gen1 and Windows Gen2 virtual machines?
  3. Could this be related to Resilient Change Tracking (RCT) metadata or Reference Point metadata corruption?
  4. Are there any recommended hotfixes or cumulative updates addressing this issue?
  5. Is there any Microsoft diagnostic logging or tracing that you recommend enabling to further investigate these intermittent failures?

Although all virtual machines are currently operating normally, we are concerned that the underlying issue may affect future Hyper-V Replica operations or Production Checkpoint creation.

We would appreciate any guidance or recommendations.

Kind regards,Dear Microsoft Support,

We are experiencing intermittent Hyper-V Reference Point / Production Checkpoint related failures on a newly deployed Windows Server 2025 Hyper-V host.

Environment

  • Host OS: Microsoft Windows Server 2025 Standard
  • OS Build: 10.0.26100 (Build 26100)
  • Latest cumulative updates installed
  • Server: Dell PowerEdge R760xs
  • RAID Controller: Dell PERC H755
  • BIOS and firmware updated to the latest available versions
  • Hyper-V Configuration Version: 12.0

Virtual Machines

The issue has been observed on multiple virtual machines, including:

  • Linux Generation 1 virtual machines
  • Windows Generation 2 virtual machines

Therefore, the issue does not appear to be guest OS or VM generation specific.

Symptoms

Hyper-V intermittently fails during operations that require Production Checkpoints / Reference Points.

Previously, when Hyper-V Replica was configured, replication occasionally failed with Reference Point related errors.

The same behavior occurred before any third-party backup software was installed, therefore the issue is not related to backup software.

Hyper-V Replica has since been completely removed, however we are still concerned that the underlying issue may still exist.

Diagnostics performed

We have verified the following:

  • No active Hyper-V Replica configuration
  • No orphaned AVHDX files
  • No remaining checkpoints
  • No checkpoint chain corruption
  • VHDX files are healthy
  • Fragmentation = 0%
  • No NTFS errors
  • No storage errors
  • No RAID controller errors
  • BIOS and firmware are current
  • Hyper-V reports all VMs as healthy and running normally

PowerShell confirms:

  • ReplicationMode = None
  • ReplicationState = Disabled
  • ReplicationHealth = NotApplicable

Questions

  1. Are there any known issues in Windows Server 2025 related to Hyper-V Reference Points or Production Checkpoints?
  2. Are there any known issues affecting both Linux Gen1 and Windows Gen2 virtual machines?
  3. Could this be related to Resilient Change Tracking (RCT) metadata or Reference Point metadata corruption?
  4. Are there any recommended hotfixes or cumulative updates addressing this issue?
  5. Is there any Microsoft diagnostic logging or tracing that you recommend enabling to further investigate these intermittent failures?

Although all virtual machines are currently operating normally, we are concerned that the underlying issue may affect future Hyper-V Replica operations or Production Checkpoint creation.

We would appreciate any guidance or recommendations.

Kind regards,

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xuan Nhu 970 Reputation points Independent Advisor
    2026-06-30T10:10:33.8466667+00:00

    Hi Koller,

    Thanks for reaching out!

    Based on the information provided, we are not aware of any currently documented Windows Server 2025 known issue specifically related to Hyper-V Reference Points or Production Checkpoints. The issue also affects both Linux Gen1 and Windows Gen2 VMs, which suggests the problem is occurring at the Hyper-V host layer rather than within the guest operating systems. Please visit Guidance for troubleshooting Hyper-V snapshots, checkpoints, and differencing disks (AVHDX) for further details.

    My primary suspicion would be RCT (Resilient Change Tracking) or Reference Point metadata. Since similar failures were previously observed during Hyper-V Replica operations, it is possible that stale or corrupted RCT/Reference Point metadata remains, even though replication has since been removed.

    At this stage, I would recommend focusing on collecting the exact error message, Event IDs, and corresponding Hyper-V-VMMS trace at the time of failure. These logs are typically required to determine whether the issue is related to checkpoint creation, RCT metadata, storage interaction, or a potential Hyper-V defect.

    For further investigation, please refer to the following Microsoft guidance:

    Once the exact error details and event logs are available, we can better determine the underlying cause and the appropriate remediation steps.

    Please let me know if you need further clarification. Thank you.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.