Windows 10: Hyper-V Checkpoint revert accidentally: Can I recover original files?

Today my VM popped up with "Do you want to revert to xx_xx_ date or continue?" I literally went to hit "Continue" but I've got an awkward setup and the mouse is a little twitchy and it hit "revert". Which is an absolute catastrophe - the revert point was when the machine was first made. Now supposedly it had another checkpoint for today, but now that it's reverted, that check point is not available! ****. I have turned off the machine so that I have some kind of chance of using a recovery program to pull the files back out. Has anyone got any experience with this? Someone mentioned Recuva in a

:)

 

Hyper V Checkpoint Error

Hi Sarjeant, as an Independent Advisor, I'd be happy to help.

This error generally suggests an issue related to permissions or availability of storage where the checkpoint (also known as snapshot) is being stored. Here are some steps to investigate and potentially solve this issue:

1. Check Permissions: Ensure that the account used by Veeam to back up the VMs has appropriate permissions on the Hyper-V host, and specifically to the directory where the VM's disks and configuration files are stored. This account typically needs full control or administrative access to these resources.

2. Check Storage Space: Ensure that there is sufficient storage space on the disk where the VM's files are stored. When a checkpoint is created, Hyper-V needs to create an .avhdx file which can grow as large as the disk it is shadowing. If there isn't enough space, the operation will fail.

3. Check NTFS Rights: Ensure that the system and the account used by Veeam to back up the VMs have full control over the VM's folder and all its files. You can check this by right-clicking on the folder, going to "Properties", selecting the "Security" tab, and then checking the permissions.

4. Check Antivirus or Security Software: Sometimes, antivirus or security software can interfere with Veeam's ability to back up VMs. You might need to adjust the settings of these programs to exclude the directories where your VM's files are stored.

5. Reconfigure VM Storage Path: If permissions seem correct, and there's enough space on the storage device, it could help to try moving the VM storage to a different location, creating a checkpoint manually, and then moving it back.

6. Reset the VM: As a last resort, if none of the above steps solve the issue, you could export the VM, completely remove it from Hyper-V, and then import it again. Be sure to take necessary steps to avoid data loss, and only try this if you're comfortable with managing Hyper-V at this level.

Remember, any time you are troubleshooting, it's wise to proceed carefully, documenting your steps, and ensuring you have recent backups before making any changes. If you're not comfortable with any of these steps, you should contact a local IT service provider or continue working with Veeam support.

 

Hyper-V doesn't delete checkpoint files

It certainly does delete them if you use PowerShell with administrator privileges. I've had issues with Hyper-V Manager myself, but didn't find out the reasons.

more discussion about checkpoints are here: Create and Use Hyper-V Checkpoints in Windows 10 Virtualization Tutorials

 

Hyper-V doesn't delete checkpoint files

Is it normal for Hyper-V to not delete the original checkpoint files when the reference/restore point is deleted in the Hyper-V manager?

I am just getting my feet wet in the Hyper-V realm and noticed that the AVHDX files take space on my PC even after deleting the checkpoint -- until I manually remove them. Seems rather counterintuitive. Also, can anyone tell me what exactly are VMRS and VMXC files used for? I see them in my Virtual Machines folder.

Thnx