Residual virtual machine checkpoints remain visible in Hyper-V Manager after differential disk files (.avhdx) have been merged, and they cannot be removed using standard tools such as Hyper-V Manager or PowerShell.
Residual checkpoints after .avhdx consolidation are typically caused by metadata desynchronization between the disk files and Hyper-V configuration. This can happen, for example, when differential disks are manually merged using PowerShell while Hyper-V Manager is still open — in this case, the .avhdx files are correctly merged into the base .vhdx file, but the checkpoint metadata is not removed. Other scenarios can also lead to the same issue, but this is one of the most common.
Before attempting manual checkpoint removal, ensure that incremental (.avhdx) disks have been successfully merged into the main virtual disk. In the VM’s settings, confirm that the virtual hard disk path points to a .vhdx file, not an .avhdx.
First, for the integrity of the operation, power off the virtual machine (before making any changes).
Open PowerShell as administrator and use the following command (replace [VirtualMachineName] with the actual name of the virtual machine as displayed in Hyper-V Manager):
The command will return the names and IDs of all snapshots associated with the VM.
For more detailed information, you can execute the following command:
In the VM settings (Hyper-V Manager > Settings > Checkpoints > Checkpoint file location), identify the path where snapshots are stored and navigate to this directory in File Explorer. You will find folders and files named according to the snapshot identifiers returned earlier. Do not delete them yet, as they are still locked by the Hyper-V service.
Open the services console (services.msc) and stop the service named Hyper-V Virtual Machine Management Service (VMMS). Alternatively, you can use a PowerShell command:
Once the service is stopped, delete all folders and files corresponding to the problematic snapshot identifiers.
Restart the previously stopped service using the following command:
Reopen Hyper-V Manager and confirm that the previously persistent checkpoints no longer appear in the list of snapshots.
VMware backup is missing files and/or folders.
If your VMware backup ends with warnings, the task details may indicate that one or more files failed to back up. Permissions for the Datastore Browser are managed by the vCenter server — in some cases, access to the Datastore Browser may be disabled for security reasons or to prevent users from accessing core virtual machine files and folders stored on the datastores.
Enable the Datastore Browser feature:
Stop the VirtualCenter Server service.
Back up the configuration file:
For Windows vCenter Server: C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg
For vCenter Server Appliance: /etc/vmware-vpx/vpxd.cfg
Open the vpxd.cfg file in a text editor.
Locate the <vpxd> tags and add the following entry within them:
Save the changes.
Start the VirtualCenter Server service.
You should now be able to back up the previously problematic files.
Optionally, create a snapshot of the vSphere server VM to enable restoration in case of a failure.
<enableHttpDatastoreAccess>true</enableHttpDatastoreAccess>Get-VMSnapshot -VMName [VirtualMachineName] | Select-Object Name, IdGet-VMSnapshot -VMName [VirtualMachineName] | Format-ListStop-Service vmmsStart-Service vmmsHyper-V related issues.
You cannot see your Hyper-V environment in Xopero ONE Management Service (XMS) even after installing the agent on the host.
Remember to use the appropriate installer to natively secure the Hyper-V host for external backup. This dedicated installer can be downloaded from the XMS in Virtual Machines > Hyper-V tab using the (+) Add new button.
If the Hyper-V host was added as a regular agent (with endpoint or server license), go to the Devices tab, select the device, and choose Delete from the top menu (without deleting data). With the correct installer and a Hyper-V per socket license, the license will be assigned automatically.
You are unable to backup your Hyper-V cluster.
To secure a Hyper-V cluster, install a dedicated backup agent on each Hyper-V host. After installation, open XMS, go to Virtual Machines > Hyper-V to add the entire cluster to your backup plan using the dedicated checkboxes.
You have the license but cannot assign it to your Hyper-V host.
To assign the correct installer license for Hyper-V hosts, you must use a dedicated Hyper-V per socket license. This license type is based on the number of processor sockets in the physical machine.
Backup (or replication) process finishes with "DW9700 - Creation of Application consistent snapshot failed" error message.
The error “DW9700 - Creation of Application consistent snapshot failed” usually means that during backup (or replication) process the Xopero system tried to create a VSS snapshot with application consistency, but the process didn’t complete successfully.
Check whether integration services are enabled in your virtual machine settings (Services > Backup (volume shadow copy) must be checked).
Check whether the operating system is supported by Hyper-V:
Check if integration services are running on the guest system:
