Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3778
  • Last Modified:

Hyper-V Virtual Servers will not start - 'Servername' Failed to start worker process: class not registered (0x0040154)

This morning, virtual servers on one of my Hyper-V host servers were all in the 'SAVED' status.  When I try to start them I get the following message (full details):

An error occurred while attempting to change the state of virtual machine 'ServerName'.
'ServerName' failed to restore virtual machine state.
'ServerName' failed to restore virtual machine state.  (Virtual Machine ID .....)
'ServerName' failed to start worker process: Class not registered (0x80040154).  (Virtual Machine ID .....)

I have attempted system reboots, backed out the 4 patches installed last night (all released 11/11/2008), checked permissions on the files, and tried to recreate the virtual servers using the existing .vhd file.  I also tried creating a new virtual machine from scratch and it gives the same error.
Has anyone seen this error before and know how to correct it?

Server is an HP DL360 G5, latest firmware and Bios running Windows Server 2008 Enterprise Full install with Hyper-V role only.  No A/V or other apps installed!

To make things worse, I rebooted one of my Server Core systems running Hyper-V (all it's VM's were running) and after the reboot it is having the same problems as the system above!  It also patched last night but all VM's were running this morning.


This error is also listed in the Hyper-v-VMMS log.
  • 2
1 Solution
SCWestServerAuthor Commented:
FYI - More info.  This server is running the full version of 2008.  I also have a Core Server running Hyper-V whose VM's were running.  I rebooted it and now the VM's on that server also will not start and have the same error message.
SCWestServerAuthor Commented:
All is well now, here is what I did:

I had to rebuild the OS partition of the Full Install Hyper-V host because Hyper-V did not uninstall properly and the system hung.  I was then able to recreate all the VM's using the existing VHD's.

On the server core system I uninstalled Hyper-V successfully and then reinstalled it.  I again had to recreate the VM's using the existing VHD's and they all started fine.

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now