| Event Id | 19000 |
| Source | Microsoft-Windows-Hyper-V-VMMS |
| Description | The WMI namespace '%1' is not registered in the CIM repository. |
| Event Information | According to Microsoft: Cause : This event is logged when the WMI namespace is not registered in the CIM repository. Resolution : Ensure VMMS is running and WMI registered Ensure that the VMMS service is in the running state. The Managed Object Format (MOF) compiler parses a file containing MOF statements and adds the classes and class instances defined in the file to the WMI repository. If this event still appears in the event log, run following commands on the Hyper-V server: mofcomp %systemroot%\system32\WindowsVirtualization.mof Mofcomp %systemroot%\system32\en-US\WindowsVirtualization.mfl and then restart the VMMS service. To restart the VMMS service: 1.Open a command prompt with local administrator privileges. 2.Type the following command to stop the vmms service. net stop vmmsnet stop If the service is not running, you will see the error "The Hyper-V Virtual Machine Management service is not started." 3.On the command prompt type the following command to start the vmms service. net start vmms If the service start starts you will see the message "The Hyper-V Virtual Management service was start successfully." If you still see this event firing, re-install Hyper-V. Verify : The nvspwmi service is displayed as running in the service control manager and the user is able to create and manage virtual switches. |
| Reference Links | Event ID 19000 from Source Microsoft-Windows-Hyper-V-VMMS |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.