Hyper-V Ms won't start after updates and reboot
Posted on 2014-11-13
I need some help.
I installed the November 2014 MS updates last night. I installed them on my lab Hyper-V box. The Hyper-V box is joined to a domain but is not a domain controller. It is Server 2012R2 with Hyper-V with all previous patches applied. I had two VMs configured on the box. The VMs were a 2012R2 server and a Windows 8.1 box. Both were running fine. In fact I shut them down before I did the Microsoft Updates on the server.
The issue I describe below was not present until I did the updates and rebooted. The server and the associated VMs had been running fine for months. These updates are the ones that my SUS server provided to this server.
After I rebooted the server I could not restart either VM. I kept getting the same error that is listed below. I tried DELETING the VM from Hyper-V manager and then building a new VM and using the old vhdx. Again NO LUCK. I even tried CREATING a new VM and I got the same problem.
(Additional Note: I appeared as though I was able to delete the VM from Hyper-V Manager. Hyper-V Manager displayed 'Destroying....' for some period of time and then the VM was removed from Hyper-V Manager. However, recreating the VM did not solve the problem.)
Each time I get the following error displayed on screen.
'Unnamed VM' could not intiialize.
An attempt to read or update virtual machine configuration failed
'Unnamed VM' could not initialize (Virtual Machine ID)
'Unnamed VM' could not read or update virtual machine configuration: Ran out of memory (0x8007000E) Virtual machine ID B9xxxxxxxxxxxx
I adjusted permissions on the C:\ProgramData\Microsoft\Windows\Hyper-V folder. Opened it up to "Authenticated Users" based on a couple of TechNet articles that I found. NO luck
In the Hyper-V Config log I get the following entry,
The configuration store at'' is not accessible Unspecified error(0x80004005)
I also had these errors in the Windows Application log.
ID=1000 Source=Application Error Type=1 Message=Faulting application name: vmwp.exe, version: 6.3.9600.17334, time stamp: 0x5407c751
Faulting module name: vsconfig.dll, version: 6.3.9600.16384, time stamp: 0x5215db66
Exception code: 0xc0000194
Fault offset: 0x000000000001966c
Faulting process id: 0xb84
Faulting application start time: 0x01cffe274d55ea6b
Faulting application path: C:\Windows\System32\vmwp.exe
Faulting module path: C:\Windows\System32\vsconfig.dll
Report Id: d4210450-6a1a-11e4-80d6-0019b9eed814
Faulting package full name:
Faulting package-relative application ID: