Microsoft video monitor catastrophic failure or Failed to restore with Error ‘Catastrophic failure’ (0x8000FFFF)   2 comments

Somehow the Hyper-v server Stopped Microsoft video monitor catastrophic failure or Failed to restore with Error ‘Catastrophic failure’ (0x8000FFFF)

A hyper-v server reboot did not solve the problem. the servers are hung on saved state. This hyper-v server is far from best practice and the cause of this is unknown shutdown during patching or installing some software updates. In my case I was upgrading the Windows server 2016 TP3 to windows server 2016 TP4 and I may rebooted the hyper-v server just to see if it is stable and to see what is happening. Well It broke my VM’s eh bring it in save state.

But can we fix this ? yes we can.

image

the servers are all in a saved state. When starting the servers we get this error : Microsoft video monitor catastrophic failure or Failed to restore with Error ‘Catastrophic failure’ (0x8000FFFF)

image

First an easy fix reboot the hyper- server. but this did not solve the issue.

An extra stop start of the vmms services

net stop vmms

net start vmms

no result.

there is a KB https://support.microsoft.com/en-us/kb/2960802

To work around this issue, follow these steps:

  1. Start Command Prompt with elevated permissions, and then run the following command:
    Net stop vmms

    If it prompts, input yes to stop the Remote Desktop Virtualization Host Agent service.

  2. Open the configuration XML of the VM. Generally, the file is under the Virtual Machines folder of the VM.
  3. Find the VDEVVersion tag which has a value of 512. Reduce this value to 256, and then save the XML file.
  4. Start Command Prompt with elevated permissions, and then run the following command:
    Net start vmhostagent
  5. Try to start the VM again.

 

So basically the fix is easy edit the config files and save it an start the vm.

image

  <VDEVVersion type="integer">512</VDEVVersion>

</_58f75a6d-d949-4320-99e1-a2a2576d581c_>

<_5ced1297-4598-4915-a5fc-ad21bb4d02a4_>

  <VDEVVersion type="integer">256</VDEVVersion>

</_5ced1297-4598-4915-a5fc-ad21bb4d02a4_>

<_655bc5c5-a784-46b7-81bc-e26328f7eb0e_>

  <VDEVVersion type="integer">512</VDEVVersion>

</_655bc5c5-a784-46b7-81bc-e26328f7eb0e_>

<_6c09bb55-d683-4da0-8931-c9bf705f6480_>

  <Enabled type="bool">False</Enabled>

this fixed the issue but if you can loose the saved state and just start the VM again if may also help your issue.

image

So if you upgrade your VM’s don’t do a live migration or a Hyper-v server shutdown let the upgrade finish first and logon to the servers and see if all is working.

 

Happy clustering

Robert Smit

@clusterMVP

https://robertsmit.wordpress.com

Technorati Tags: Windows,Server,Storage,Spaces,Direct,SOFS,setup

Posted November 30, 2015 by Robert Smit [MVP] in Hyper-V

Tagged with

2 responses to “Microsoft video monitor catastrophic failure or Failed to restore with Error ‘Catastrophic failure’ (0x8000FFFF)

Subscribe to comments with RSS.

  1. Hi,
    I have the same problem, so I tried to apply your fix.
    However, the command “Net start vmhostagent” does not work. I receive an error “invalid service name”.
    The command “Net start vmms” works, but the VM still send the error 8000FFFF at start.
    Do you have any idea?
    I have a windows 2008.

    • In this case it was on windows server 2016. but the quickest way Is recreate the VM. remount the disk. you are up in less then 5 min.

      for the fix make sure you edited this in the right spot. there are multiple locations for this.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

  • Twitter

  • %d bloggers like this: