![]() Production checkpoints are used by default in Hyper-V. If deselecting the Backup (volume checkpoint) option helped you create a checkpoint without errors, it is recommended that you re-select this option after you are done creating the checkpoint. If there is an issue with the VSS writer, disabling this option can be of help. The deselected option is used for crash-consistent checkpoints, and the selected option is used for application-consistent checkpoints (the VSS signal is passed to a guest OS). Select/Deselect the Backup (volume checkpoint) option. ![]() Click Integration Services in the Management section.Make sure that Hyper-V Integration Services are installed in the guest operating system (OS). ![]() Try the following steps to fix the issue: To view logs, open Computer Management and go to System Tools > Event viewer > Applications and services > Microsoft > Windows > Hyper-V VMMS.Ĭheck the settings of Integration Services In Event Viewer, you can find more detailed information about errors than in Hyper-V Manager. The general recommendation to address different Hyper-V errors is to check Event Viewer log files. If permissions are correct, check that you have enough free storage space to perform operations with Hyper-V checkpoints. If you see an identifier instead of a user or group name in folder properties, the permissions may be incorrect. The system account that Hyper-V is running must have read and write permissions for the folder containing virtual disks and snapshot files. You need to make sure that there are enough permissions to access the needed data by Hyper-V. In this example, the virtual disk files are stored in the D:\Hyper-V\Virtual hard disks folder. AVHDX virtual disk files created when you take checkpoints. You can see a running Hyper-V VM with checkpoints in the screenshot below. To understand the cause of the error and fix it, you can do the following:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |