Are you stuck with hyper-v catastrophic failure (0x8000ffff)? We can help you fix it.
There are multiple occasions for this error to occur. The common ones are when trying to delete a checkpoint or after upgrading Windows.
Here at Bobcares, we often receive requests regarding to fix Hyper V errors as a part of our Server Management Services.
Today, let’s see how our Support Engineers fix hyper-v catastrophic failure (0x8000ffff)
Causes for the Catastrophic failure (0x8000FFFF)
This error commonly occurs when we try to delete the checkpoint. Another possibility is when we try to upgrade windows in the host server.
Also, occurs when we try to increase the CPU core and can occur when starting the virtual machine.
The cause for this error is the configuration file references a VM checkpoint data set is lost or does not exist.
Thus, to resolve this we need to restore the checkpoint or the virtual machine. Else we need to edit the virtual machine configuration to resolve the error.
The sample error looks like:
Let us discuss how our Support Engineers resolve the error for our customers.
How we fix Hyper-v catastrophic failure (0x8000ffff)
Recently one of the customers contacted us saying that he is unable to delete the checkpoint. Thus, there was no backup of the whole Virtual machine.
In most of the cases, a clean VM restart will resolve the error. But still, the error persisted.
Thus, the available option is to edit the virtual machine configuration file to resolve the error. Let us discuss how our Support Engineers resolve this error by editing the configuration file.
First, we open the command prompt with administrator privileges.
Then we run the command
Net stop vmms
Now a message prompt to stop the Remote Desktop Virtualization Host Agent service appears. We enter yes to proceed further.
Then we navigate to the virtual machine’s folder. After that, we open the configuration XML file of the virtual machine.
In the file, we find the VDEVVersion tag. The default value is 512.
<VDEVVersion type="integer">512</VDEVVersion>
We reduce the value to 256, and we save the XML file.
In the command prompt, we run the following command
Net start vmhostagent
After that finally, we start the virtual machine.
[Need assistance to fix Hyper-V errors – We can help you fix it]
Conclusion
In short, we have discussed the causes of the error. Also, we have discussed how our Support Engineers fix hyper-v catastrophic failure (0x8000ffff) for our customers.
Unable to delete the Check point in Hyper -V that is created by Veeam Backup and replication. I have treid the above solutions along with few other recommendations suggested online such as exporing the most recent avhdx file to the new location and etc…
Unfortunately that process was not successful.
Also, I would like to give more explanation of my current scenario below.
1. The Veeam Backup and Replica is created 50 Check Points while performing the daily backup jobs (Schedule is set to run Every 4 Hours).
2. When I tried to delete the most recent check on the Hyper – V manager, I am unable to delete the check point and it is giving Catastrophic failure error on the screen.
Can someone please suggest how to over come this issue. Contact details as followed.
Hi,
Our experts can help you with the issue.we will be happy to talk to you through our live chat(click on the icon at right-bottom).