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.