I have a Windows 2012 R2 Hyper-V Host server that has been performing perfectly up until one week ago. This is a lab environment, but it is an important lab for testing deployments of Exchange, SCCM, ADFS, as well as desktop deployment scenarios using ADK 8.1. The point is its an important lab environment for my consulting firm.
The problem: About a week ago I fired up the host server and thevirutal machine manager service will not start. The error is as stated in the post above.
The host is nowhere near out of disk space and the disk is not corrupted. All file checks and disk checks pass with no errors. The files have all been verified for accuracy. The available disk space on the system disk is 40GB. All of the VM Guests and the default machine configuration files as well as Vhdx files are stored on a separate disk that check out good as well with over 400GB free space.
The event log shows the error posted above and the only other error in the event log is Event ID: 46
\Device\HarddiskVolume7
Volmgr - Crash dump initialization failed.
Disk 7 has nothing to do with the Windows Server installation or Hyper-V files.
The only other thing I did on this machine is create 2 separate partitions on a separate disk and install Windows 8.1 and Windows 7 as a dual-boot option. The problem did seem to occur after doing this but not immediately. I also, cannot make the connection as to why this would have caused the service to fail. The Windows 8.1 and Windows 7 files are on a completely different disk with the BCD boot options being the only configuration change that was made to the system disk or C:\Root drive.
Please help! It's important to get this fixed as soon as possible.
David Cook
dshcook@itsaboutsolutions.com
David Cook