checkpoint operation failed could not initiate a checkpoint operation

Then go to the place the checkpoint is being saved and copy it somewhere safe, Then delete the VM or just rename it. 01:51 PM. The errors that you get when you have an AVHDX with an invalid parent usually do not help you reach that conclusion. A change on the virtual disk (which is a changed block of data) is not written to the parent .VHDX file, but to a .AVHDX checkpoint file. Privacy Look in the event viewer for any clues as to why that didnt happen. Also, weve discussed how our Support Engineers change the required setting to resolve the error. Reliable Hyper-V Backup Solution from NAKIVO, Could not initiate a checkpoint operation, Incorrect permission settings for the folder containing snapshots, A Hyper-V VM moved from a different host improperly and without setting the required permissions. To view logs, open Computer Management and go to System Tools > Event viewer > Applications and services > Microsoft > Windows > Hyper-V VMMS. If merged in the original location and in the correct order, AVHDX merging poses no risks. Terms We initially, open Hyper-v manager and select the Virtual machine. by fsr Jan 08, 2020 8:12 pm If checkpointing in Hyper-V keeps failing, you could try another Microsoft application PowerShell. For your reference: Snapshot - General access denied error (0x80070005). 'S2022DC' could not initiate a checkpoint operation. To find and fix issues, use Hyper-V logs. You will have no further option except to recreate the virtual machines files. I recommend that you perform merges with PowerShell because you can do it more quickly. You may need to disable production checkpoints for the VM. I can unsubscribe at any time. In Method 3 this sentence seems incomplete: The risk of data loss is about the same as method 5. Perpetual licenses of VMware and/or Hyper-V, Subscription licenses of VMware, Hyper-V, Nutanix, AWS and Physical, I agree to the NAKIVO The vmrs file for this VM is 67Gb There are about 49Gb worth of vhdx files for this VM on S2D vol Leave those unconnected for now. We enable the checkpoint option. Check your backups and/or make an export. The Hyper-V backup error "could not initiate a checkpoint operation: Element not found. I Your email address will not be published. by mapate Dec 29, 2019 5:02 am Check on any supporting tools that identify VMs by ID instead of name (like backup). You can safely delete them all. Uninstalling and reinstalling it resolved my inability to backup the 2012 R2 VM. Apr 21 2021 If, for some reason, the checkpoint process did not merge the disks, do that manually first. Thank you anyway for your excelllent blog articles ! Any changes made on a virtual disk (that is, changed blocks) are recorded to an .AVHDX checkpoint file instead of being written to the parent .VHDX file. You could remove backup server from group policy for a while to test whether Hyper-V checkpoints could be created. You can easily take care of these leftover bits, but you must proceed with caution. The only odd thing about this VM is it has a load of .vmgs files (4097kb each) in its Snapshots folder, each with a correspondingly named empty folder. Try the following steps to fix the issue: 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 the VM is sharing certain devices like physical DVD drive, virtual disk, etc., with another VM this error might occur so you could check VM configuration to see whether there is a shared device. Sometimes the checkpoint does not present aDelete option in Hyper-V Manager. 1 person likes this post, Post Also, do not start off by deleting the virtual machine. this post, Post if your problem is related to parents and .avhdx file, you need to go to your vm settings and choose your hard drive and then try to edit your vhd file. VBR is successfully backing up several Windows VM in the cluster but am unable to successfully backup the Ubuntu VM. Didn't find what you were looking for? A special type of checkpoints, which is the recovery checkpoint, is used as a differencing virtual hard disk and can be the cause for issues in case the backup workflow isnt completed successfully. See the causes of the issue and get effective fixes for it in this post. Login or and other members-exclusive content, Join 50,000+ IT Pros Bouncing services around eventually would get it to work. If a snapshot was created by Hyper-V backup software, try to delete this lingering backup checkpoint in PowerShell: A checkpoint of recovery type is created. Open Hyper-V Manager > right-click the problematic VM > select, Production Checkpoint is added later in Windows 10, which uses Volume Shadow Copy Service or File System Freeze on a Linux virtual machine to create a data-consistent. The following information was included with the event: server-name There is already one checkpoint in place. The ID is used for serving ads that are most relevant to the user. You can search for manual fixes but in the case of an otherwise functional SQL Server I chose to go for a repair install of SQL Server. agree that In the Hyper-V Manager interface, right-click on the virtual machine (not a checkpoint), and clickCheckpoint: Now, at the root of all of the VMs checkpoints, right-click on the topmost and clickDelete checkpoint subtree: If this option does not appear, then our jiggle the handle fix wont work. Each differencing disk (the AVHDXs) contains the FULL path of their parent. How can I narrow down what is causing this? I had such a case where the Hyper-V Checkpoints were not removable. (0x80070490)" is an old but still existing Hyper-V bug seen on Windows Server 2012 R2 when backing up Hyper-V virtual machines with Windows Server 2003 guest operating systems. 10 Total Steps I went through the same issue and I was able to fix it on my own, so I just want to contribute and share another possible solution. (Virtual machine ID 409F8A99-AFE7-480C-AEA2-95D5E90E9C1A). Vinchin Backup & Recoveryis an excellent VM backup solution which has helped thousands of companies protect their business systems. Initially, we open the Hyper-V Manager and select the Virtual machine. To be precise VM does not have permissions to its own disks folder. our expert moderators your questions. Another common reason for the failure is because of the wrong checkpoint architecture. Any changes made on a virtual disk (that is, changed blocks) are recorded to an .AVHDX checkpoint file instead of being written to the parent, Another error related to creating Hyper-V checkpoints is, NAKIVO There are two types of Hyper-V checkpoints: Standard checkpoints are application-consistent and save the disk data and memory state, as well as hardware configuration of a running VM. Errors that appear when you try to create a Hyper-V checkpoint may look as follows: The incorrect permissions configured for folders and files are usual reasons for such errors. Re-enable checkpoints in Hyper-V Manager. Delete the virtual machine (Method 3 step 6 has a screenshot, mind the note about. But others cant, such as Microsoft Access and MySQL. The virtual machine ' ' cannot start a backup operation because it is currently executing a conflicting operation. For instance. For now, Ive renumbered them. [Expanded Information]Checkpoint operation for 'vm_name' failed. In the properties, select Integration Services. 1 person likes this post, Post Spice (1) flag Report I dont think that Ive ever seen a Hyper-V backup application that will allow you to only restore the virtual machine configuration files, but if one exists and you happen to have it, use that feature. 12:52 PM Download NAKIVO Backup & Replication free edition and try the solution in your environment. Bonus Flashback: March 3, 1969: Apollo 9 launched (Read more HERE.) Merging them and enabling Guest Services in Hyper-V Manager might be the cure. Remove the restored virtual disks from the VM (see step 4 of Method 3). Enter to win a. I have ran into this before. Save my name, email, and website in this browser for the next time I comment. If production checkpoint fails, it specifies the host to automatically take a standard checkpoint. The equivalent PowerShell isCheckpoint-VM -VMName demovmfollowed byRemove-VMCheckpoint -VMName demovm. At least you should know how to export entire Hyper-V VM. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. Backup solutions can perform the following actions to create a VM backup: The recovery checkpoint turns into a lingering checkpoint when automatic deletion doesnt happen due to a failed backup process. by AlexandreD Jul 29, 2019 6:54 am If you have more than a couple of disks to merge, you will find this process tedious. The A in AVHDX stands for automatic. This is a bit more involved jiggle the handle type of fix, but its also easy. How to fix the issue Hyper-V checkpoint operation failed? At least you should know. Open Hyper-V Manager > right-click the problematic VM > select Settings > in Management tab, select Checkpoints > uncheck Enable checkpoints > click Apply > re-enable checkpoints > click Apply. Interrupting a backup can cause all sorts of problems. One of the cool features of Hyper-V is checkpoints. Change Hyper-V integration services, Open Hyper-V Manager > right-click the problematic VM > select Settings > in Management tab, click Integration Services > uncheck Backup (volume shadow copy) > click Apply. Update 2018 #2: Yet another bug in Hyper-V on Windows Server 2016 has surfaced. When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. If it reports an error during the process, the error messages might include: Could not initiate a checkpoint operation, Production checkpoints cannot be created, Failed to switch using the new differencing disks, The operation failed because the file was not found, Cannot take checkpoint for *** because one or more shareable vhds are attached. Find out more about the Microsoft MVP Award Program. Method 1: Delete the Checkpoint If you can, right-click the checkpoint in Hyper-V Manager and use the Delete Checkpoint or Delete Checkpoint Subtree option: This usually does not work on lingering checkpoints, but it never hurts to try. The website cannot function properly without these cookies. by wishr Sep 24, 2019 8:57 am The general recommendation to address different Hyper-V errors is to check Event Viewer log files. Import the virtual machine configurationfrom step 5 into the location you recorded in step 3. How you got fixed I am having the same issue not able export and not able to delete the checkpoint. If you see an identifier instead of a user or group name in folder properties, the permissions may be incorrect. Another reason is because of the wrong checkpoint architecture. However, it sometimes fails to completely clean up afterward. When a virtual disk has checkpoints, you cannot perform virtual disk operations, like expanding a virtual disk. If you have confidence in your backup, or if you already followed step 4 and still have the export, then you can skip step 5 (export the VM). If your checkpoint persists after trying the above, then you now face some potentially difficult choices. Last but not least I can see this inside the VM usingvssadmin list writers: Writer name: 'SqlServerWriter'Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}Writer Instance Id: {fa8a6236-e52b-4970-8778-b8e024b46d70}State: [8] FailedLast error: Inconsistent shadow copy, Posted in Solution 2. Some users report that restarting VSS service (Volume Shadow Copy Service)could turn the writer to a normal state. Checkpoint operation failed. It does not need to be recent. In this guide, we explain why Hyper-V checkpoint operations might fail due to errors and guide you through ways to fix those errors. Don't worry, you can unsubscribe whenever you like! by wishr Jul 30, 2019 4:19 pm DV - Google ad personalisation. this post, Post It was due to the Message Queuing Service on the guest. After the VM shutdown, try to consolidate or remove existing checkpoints. How to Backup XenServer VM and Host Easily in 6 Ways. Run PowerShell as the Windows administrator. I do not know how pass-through disks or vSANs affect these processes. If you need instructions, look at the section after the final method. Try using the guidelines from the previous sections: check folder permissions, checkpoint and integration services settings. by wishr Jul 05, 2019 9:30 am Is there a way i can do that please help. Ill have to go back through all my drafts and see what happened with the numbering. Go to folder Properties>Security>Edit Add INTERACTIVE and SERVICE and give them needed permissions. I realized I messed up when I went to rejoin the domain Welcome to the Snap! gdpr[allowed_cookies] - Used to store user allowed cookies. Best practices and the latest news on Microsoft FastTrack, The employee experience platform to help people thrive at work, Expand your Azure partner-to-partner network, Bringing IT Pros together through In-Person & Virtual events. You can also read more about how to disable a Hyper-V VM stuck in the starting/stopping state. and create more checkpoints and under settings > hard drive> virtual hard disk, the path in there seem a little off, it was for sure not the one I had save it in. December 13, 2022. Some users report that they have fixed the issue by moving VM to another folder and then moving it back. A chain of checkpoints with several .AVHDX files linked to each other in the appropriate VM folder can be created if necessary. I have 3 instances of Windows 2012 standard Domain Controller VMs on Hyper-V 2016 or 2019 hosts where the checkpoint fails. Merge Hyper-V snapshots and enable Guest Services. The existing snapshots might affect checkpoint creation. Additionally, an active VM with files in use can make editing those VM settings impossible. Hyper-Vs checkpointing system typically does a perfect job of coordinating all its moving parts. Sometimes the error "could not create backup checkpoint for virtual machine" is due to permissions and one more strange Microsoft limitation: You can see an example of the Hyper-V Worker Admin log window in the screenshot below: Check the folder where your VM files are stored. Lets see how our Support Engineers resolve it for our customers. You need to hear this. Just for your information. is an old but still existing Hyper-V bug seen on Windows Server 2012 R2 when backing up Hyper-V virtual machines with Windows Server 2003 guest operating systems. (0x80070490). Change the type of checkpoint by selecting the appropriate option (change. A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. The other serves are working correctly. 'OOS-TIR-FS1' could not initiate a checkpoint operation. Hyper-V can't make a Production checkpoint manually. (0x80070490). Open Hyper-V Manager > right-click the problematic VM > select Settings > check the hardware resources, Solution 6. So, I just click on browse found the folder where I originally had saved my vm, click on This fixed the checkpoint problem. However, the checkpoint can only be deleted or cleaned up via Windows PowerShell if the backup operation fails. You could switch the checkpoint type in Hyper-V manager with the following steps: Open Hyper-V Manager > right-click the problematic VM > select Settings > in Management tab, select Checkpoints > select another checkpoint type. If you precisely followed one of the methods above that redirected you here, then you already satisfied these requirements. Open Hyper-V Manager > right-click the problematic VM > select Settings > in Management tab, select Checkpoints > uncheck Enable checkpoints > click Apply > re-enable checkpoints > click Apply Solution 7. by churchthedead Jul 30, 2019 4:05 pm (Virtual machine ID 409F8A99-AFE7-480C-AEA2-95D5E90E9C1A) How can I narrow down what is causing this? If you see the Hyper-V checkpoint operation failed error, try to change the checkpoint type to standard checkpoints. by mb1811 Jul 24, 2019 6:18 am If you have permission problem you need to use the below command to reset the permission of your .VHDx files: icacls C:\ClusterStorage\Volume4 /grant NT VIRTUAL MACHINE\Virtual Machines:F /T. You can see this error when attempting to edit the settings of a Hyper-V VMs virtual disk. Hyper-V on Windows 2019 S2D unable to create a checkpoint for a particular VM, Windows Server AMA: Developing Hybrid Cloud and Azure Skills for Windows Server Professionals. http://technet.microsoft.com/en-us/library/jj860400.aspx, //backupchain.com/hyper-v-backup/Troubleshooting.html, 18 Hyper-V Tips & Strategies You Need to Know, How to use BackupChain for Cloud and Remote, DriveMaker: Map FTP, SFTP, S3 Sites to a Drive Letter (Freeware), Alternatives to Acronis, Veeam, Backup Exec, and Microsoft DPM, How to Fix Disk Signature Error PartMgr 58, How to Configure a Hyper-V Granular Backup, Alternative to Amazon S3, Glacier, Azure, OpenStack, Google Cloud Drive, All Fixes for: The driver detected a controller error on \Device\Harddisk2\DR2, VSS Crash and Application Consistency for Hyper-V and VMware Backups, Backup Software for Windows Server 2022, VMware, & Hyper-V, Gmail SMTP Configuration for Backup Alerts, Video Step-by-Step Restore VM from Hyper-V Backup on Windows Server 2022 and Windows 11, Best Network Backup Solution for Windows Server 2022, How to Install Microsoft Hyper-V Server 2012 R2 / 2008 R2, Version Backup Software with File Versioning, Volume Shadow Copy Error Diagnostic Freeware VssDiag, Why You Need To Defragment Your Backup Drives. I honestly just felt like deleting my VM and re starting it if anything (my HV Vm is Request a live demo by one of our engineers, See the full list of features, editions and prices. If the backup process is retried, the error is likely to reoccur. 'vm_name' could not initiate a checkpoint operation: %%2147754992 (0x800423F0). In our case, the destination for those virtual disk files is D:\Hyper-V\Virtual hard disks, and we need to ensure that the correct permissions are set for Hyper-V to access the required data. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer. Some problem occured sending your feedback. It seems like the relationship between hot migration and cold migration. (Virtual machine ID 409F8A99-AFE7-480C-AEA2-95D5E90E9C1A), 'vm_name' could not initiate a checkpoint operation: %%2147754992 (0x800423F0). It can be temporary. _gat - Used by Google Analytics to throttle request rate _gid - Registers a unique ID that is used to generate statistical data on how you use the website. If you see that file in the folder (there could be one for each VHDX), simply delete it and run the backup once again. Type thecommandbelow to create checkpoint in PowerShell: Some users report that group policy could affect creating Hyper-V checkpoints. However, whenever you perform any operation related to checkpoints, including creating a new checkpoint, errors may occur. There appears to bea fix for the situation usingan intermediate step: You need to uncheck the backup option in the VMs Hyper-V integration settings: The difference between backing up with this option on or off is that it controls whether the VSS signal is passed into the VM. I wanted to know if i can remote access this machine and switch between os or while rebooting the system I can select the specific os. Our experts have had an average response time of 10.78 minutes in Jan 2023 to fix urgent issues. elevated command prompt, the commands wont work in powershell. I would personally shut the VM down beforehand so as to only capture the most recent data. In the previously mentioned scenario with lingering checkpoints, the most reliable method to delete the backup checkpoint is using PowerShell: Another error related to creating Hyper-V checkpoints is Could not initiate a checkpoint operation: Element not found. I decided to let MS install the 22H2 build. Starting with the AVHDX that the virtual machine used as its active disk, issue the following command: Once that finishes, move to the next file in your list. Everyone has had one of those toilets that wont stop running. You can remove all checkpoints on a host at once: If the script completes without error, you can verify in Hyper-V Manager that it successfully removed all checkpoints. If this error occurs, you cannot create a new Hyper-V checkpoint. The information does not usually directly identify you, but it can give you a more personalized web experience. Other software may react similarly, or worse. There is already one checkpoint in place. 1. click on settings on the vm having this issues, 3. under virtual hard disk click on browse, 5. once the folder is selected click on apply. Possible solutions to fix the Edit is not available because checkpoints exist for this VM error: Get-VMSnapshot -ComputerName "HyperVHostName" -VMName "VMWithLingeringBackupCheckpoint" | Remove-VMSnapshot. You can reconnect your devices afterward. When the VM was running the checkpoint would fail with the error above, however when shutting the VM down it worked without any issues. You can fix that by following these instructions. The problem is connected with a problem with performing a checkpoint of the VM. NAKIVO Backup & Replication is a comprehensive data protection solution with advanced features that provides agentless backup, instant recovery and disaster recovery. Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. Windows will need to activate again, and it will not re-use the previous licensing instance. All of my 2016 or 2019 VMs back up just fine. Snapshot is useful but it is not good enough for long-term disaster recovery plan, while backup is. by wishr Jul 24, 2019 9:56 am This process has a somewhat greater level of risk as method 4. Navigate to folder containing the Hyper-V VHD files. Try to delete the checkpoint that you just made, if possible. You will receive a welcome email shortly, as well as our weekly newsletter. Sometimes though, the GUI crashes. Search "Service"on Windows or type services.msc. Use tab completion! Before that, make sure you have enough storage for checkponits and run command vssadmin list writers. Well, I resolved my issue. (0x80070490)* There can be several reasons why it occurs: when file permissions are wrong or due to the internal VM issues related to the VSS writer. Veeam can't back it up. n error occurred while attempting to checkpoint the selected virtual machine, Snapshots, also called checkpoints in Hyper-V, are the insurance of VM data and status. If you want to do that, refer to this post How to merge Hyper-V snapshots in Hyper-V Manager. Then create a new VM with the same properties and use the check point .VHD file as the HDD. thank you for your suggestion , I just want to add I was having the same issue and I could fix it by restarting hyperv v manager service and give permission again to replica folder for account used for snapshot. There can be several reasons why it occurs: when file permissions are wrong or due to the internal VM issues related to the VSS writer. Sometimes, the traditional delete option is unavailable for a checkpoint in the Hyper-V Manager interface. Once the copy process is completed, the recovery. 1) you can try to discard all changes and reset the machine to the state before you created the checkpoint. The most common mistake is starting your repair attempt by manually merging the AVHDX file into its parent. I was creating checkpoint for Hyper-V VM but received checkpoint operation failed error. by wishr Jul 05, 2019 8:29 am Unfortunately, you might only have this problem because of a failed backup. Have just tested the freebsd . If there is enough disk space to complete the operation, check the checkpoint folder in the VM settings. Because it lists the child AVHDX in both locations, along with an empty string where the parent name should appear, it might seem that the child file has the problem. Use the following command: The solution creates a recovery type checkpoint that then holds the changes that are made in the VM throughout the backup procedure. Hi Team, Method 3 is something of a jiggle the handle fix. Get the recovery checkpoint exact name with the command, Verify that the recovery checkpoint has been successfully deleted with the command. Taking VM snapshots is necessary for data security but receiving error messages like Hyper-V checkpoint failed could be disappointing. I do not know how all pass-through disks or vSANs affect these processes.. After all, rebooting solves most computer problems. Follow steps 1, 2, and 3 from method 3 (turn VM off and record configuration information). Hyper V 2016 Events, Flashback: March 3, 1971: Magnavox Licenses Home Video Games (Read more HERE.) PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies], _clck, _clsk, CLID, ANONCHK, MR, MUID, SM, VSS error 0x800423f4 during a backup of Hyper-V: Easy Fix, SSO Embedding Looker Content in Web Application: Guide, FSR to Azure error An existing connection was forcibly closed, An Introduction to ActiveMQ Persistence PostgreSQL, How to add Virtualmin to Webmin via Web Interface, Ansible HAproxy Load Balancer | A Quick Intro. Minimum order size for Basic is 1 socket, maximum - 4 sockets. I migrated a SQL Server running Windows Server 2012 R2 and hit this bug. So the error was the VM was not able to create a new checkpoint, therefore I test another vm to see if my host was able to create checkpoints and while that seem to work then it meant the problem was isolated. Avoid Mistakes When Cleaning up a Hyper-V Checkpoint, How to Cleanup a Failed Hyper-V Checkpoint, Method 2: Create a New Checkpoint and Delete It, Method 3: Reload the Virtual Machines Configuration, Method 4: Restore the VM Configuration and Manually Merge the Disks, Method 5: Rebuild the VMs Configuration and Manually Merge the Disks, Using Wireshark to Analyze and Troubleshoot Hyper-V Networking, Real IT Pros Reveal Their Homelab Secrets, Revealed: How Many IT Pros Really Feel About Microsoft, NTFS vs. ReFS How to Decide Which to Use, Take note of the virtual machines configuration file location, its virtual disk file names and locations, and the virtual controller positions that connect them (IDE 1 position 0, SCSI 2 position 12, etc. Required fields are marked *. Read on to find out how to clean up after a failed checkpoint. Thank you, Alex Mayer, I will be saving this for future reference when creating a VM. Search "Service"on Windows or type services.msc. Hence, a consistent copy of data can be taken. Some backup solutions follow these steps to perform a backup job: If the backup process fails, the recovery checkpoint is not deleted automatically. The guest host is an domain server with Windows 2016 server. Alternatively, if you go through theEdit Disk wizard as shown in the manual merge instructions above, then at step 4, you cansometimeschoose to reconnect the disk. I do not know that anyone has ever determined the central cause of this problem. In my case, while I was receiving the same error I did research for possible solutions they all seem great but seem like those solutions were sending me in a wild chase. More info about Internet Explorer and Microsoft Edge. Checkpoint operation was cancelled. The standard checkpoint deletion option may be unavailable in the Hyper-V manager. In the next section, well explain the nature of the Hyper-V checkpoint operation failed error when it occurs after running Hyper-V VM backup jobs and methods to fix this error. Create checkpoint with PowerShell. An error Occurred while attempting to checkpoint the selected Virtual machine(s). this post, Post Just for your information. to get more specific error messages. How to Fix Hyper-V Checkpoint Operation Failed Issue in 12 Ways? IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. by churchthedead Aug 01, 2019 4:16 pm It becomes a lingering checkpoint. smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience. Try deleting the lingering backup checkpoints created by your Hyper-V backup software via PowerShell. Move the VM Some users report that they have fixed the issue by moving VM to another folder and then moving it back. Go to Hyper-V-Worker > Admin section and see events with the IDs 3280 and 18012. 1.After VM migration between hosts, when one host suddenly goes out, few problems can appear. 3.Sometimes there is a problem with performing a backup. Thank you for the very detailled article ! The cause of this error can be corrupted file permissions, as explained above in this article, or VSS writer issues inside a VM. The error in the job is: I just found this problem with a freebsd (pfSense) VM on a Windows Server 2016 HOST. If permissions are granted correctly, check the available storage space for Hyper-V checkpoints. With the use of Hyper-V Integration Services and Volume Shadow Copy Service (VSS) to freeze the state of the file system, you can avoid errors when writing data of the open files. - edited Let's discuss how our Support Engineers change the checkpoint architecture.