Link to home
Start Free TrialLog in
Avatar of GCITech

asked on

Hyper-V host services stop after a few minutes

I am working at a small school district, and their domain controller (Server2012R2) also hosts 2 Hyper V machines. I dont know if this is relevant, but recently there was an unplanned shut down.

The issue is when attempting to start any of the virtual machines, an error pops up stating: Windows could not start the Hyper-VRemote Desktop Virtualization Service service on Local computer
Error 126: The specified module could not be found.

The interesting part is, you can remove the Hyper-V feature from the server, then reinstall it, and the virtual machines will boot, and run fine, until they are rebooted or shut down, as long as you start them quickly after reinstallation of Hyper-V.  If you wait as long as 5 minutes or so, it is already broken again.
The Hyper-V services are all off, when it is not working, and you cannot turn them back on.
Any suggestions will be appreciated.
Avatar of Philip Elder
Philip Elder
Flag of Canada image

A domain controller should _not_ have the Hyper-V Role enabled. Period.
Avatar of Member_2_231077

There may be some useful stuff in the event logs but as Phillip says the host should just be the host and not run any other roles. You're probably breaking the license agreement as standard covers two VMs or the real server but you have both.
Avatar of GCITech


Thanks guys.
Hyper-VRemote Desktop Virtualization Service

This leads me to want to investigate the remote desktop services role as Remote Destkop Virtualization Service is a RDS function. 
Is there two partitions on the host?

If this was a standalone Hyper-V host without the other Roles you would be able to re-install, configure Hyper-V, and import the VMs and be up and running in about 30-45 minutes.

The DC Role with the Hyper-V Role breaks things. Plus, it kills the ability to recover simply from a problem at the host level.
Avatar of GCITech


Mr. Phillip,
I am able to remove & reinstall now, and fix only works for 5 minutes or so. I am not understanding the separate partition fix. Please elaborate.
Avatar of Member_2_231077

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
@andyalder gives the best route to take. Set up a temporary Hyper-V in say a desktop, install Windows Server, set up and DCPromo, then DCPromo the current Hyper-V host DC out, workgroup it, and finally re-install the host OS, configure the Hyper-V Role, and import the existing VMs.

You can then set up another VM, DCPromo it, transfer the FSMO Roles, and DCPromo the temp DC out.
Avatar of GCITech


Thanks for the help