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

Posted on 2008-11-19
Last Modified: 2012-05-05
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.
Question by:SCWestServer

    Author Comment

    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.

    Accepted Solution

    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

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    #Citrix #XenApp #Citrix Scout #Citrix Insight Services #Microsoft VMMAP #Microsoft ADEXPLORE #Microsoft RAMMAP #Microsoft TCPVIEW #Microsoft AUTORUNS #Microsoft PROCESS EXPLORER #Microsoft PROCESS MONITOR
    Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
    This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
    This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now