I'm not sure but I think this started after the installation from KB5051979.
Running Windows Server 2022 Datacenter.
Workaround for me at the moment is a live migration from all VMs to another host or shutdown (not reboot) from the VMs.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have been having an issue on a brand new Dell PowerEdge R650 that I loaded Server 2025 Standard on. I have also been having this same issue on servers loaded with Server 2022 as well. Whenever I attempt to create a checkpoint, I get the error:
When I check Event Viewer under Hyper-V VMMS, I am seeing the below Event IDs.
This problem goes away when I reboot the server, yet since these are Hyper-V hosts, that is not a viable option going forward. I need help to figure out what is going on.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 3/10/2025 4:06:36 AM
Event ID: 18014
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: RI-HOST02.collinsengr.com
Description:
Checkpoint operation for 'RI-DC02' was cancelled. (Virtual machine ID 642795EC-07AB-49DF-BACF-4C2C8A33AF37)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066f867-7ca1-4418-85fd-36e3f9c0600c}" />
<EventID>18014</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-03-10T08:06:36.8378724Z" />
<EventRecordID>50954</EventRecordID>
<Correlation />
<Execution ProcessID="2748" ThreadID="1160" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>RI-HOST02.collinsengr.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>RI-DC02</VmName>
<VmId>642795EC-07AB-49DF-BACF-4C2C8A33AF37</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 3/10/2025 4:06:36 AM
Event ID: 18012
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: RI-HOST02.collinsengr.com
Description:
Checkpoint operation for 'RI-DC02' failed. (Virtual machine ID 642795EC-07AB-49DF-BACF-4C2C8A33AF37)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066f867-7ca1-4418-85fd-36e3f9c0600c}" />
<EventID>18012</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-03-10T08:06:36.8379272Z" />
<EventRecordID>50955</EventRecordID>
<Correlation />
<Execution ProcessID="2748" ThreadID="1160" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>RI-HOST02.collinsengr.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>RI-DC02</VmName>
<VmId>642795EC-07AB-49DF-BACF-4C2C8A33AF37</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 3/10/2025 4:06:36 AM
Event ID: 19100
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: RI-HOST02.collinsengr.com
Description:
'RI-DC02' background disk merge failed to complete: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 642795EC-07AB-49DF-BACF-4C2C8A33AF37)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066f867-7ca1-4418-85fd-36e3f9c0600c}" />
<EventID>19100</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-03-10T08:06:36.8593764Z" />
<EventRecordID>50957</EventRecordID>
<Correlation />
<Execution ProcessID="2748" ThreadID="1160" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>RI-HOST02.collinsengr.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>RI-DC02</VmName>
<VmId>642795EC-07AB-49DF-BACF-4C2C8A33AF37</VmId>
<ErrorMessage>%%2147942432</ErrorMessage>
<ErrorCode>0x80070020</ErrorCode>
</VmlEventLog>
</UserData>
</Event>
I'm not sure but I think this started after the installation from KB5051979.
Running Windows Server 2022 Datacenter.
Workaround for me at the moment is a live migration from all VMs to another host or shutdown (not reboot) from the VMs.