| Event Id | 14073 |
| Source | Microsoft-Windows-Hyper-V-VMMS |
| Description | Virtual machine '%1' (ID=%2) stopped responding repeatedly. |
| Event Information | According to Microsoft : Cause : This event is logged when Virtual machine stopped responding repeatedlyin Hyper-V. Resolution : Retry virtual machine start Check the environment in which the start virtual machine operation was being attempted, including: 1.access and permissions to the configuration file, memory file and all image files 2.prior error messages in the event log 3.available RAM on the system 4.configuration settings 5.disk space for the memory file and any expanding virtual hard disks Once the necessary issues have been rectified, try to start the virtual machine again. If the problem continues, restart the VMMS Service. To restart VMMS using the Service Manager: 1. In the Hyper-V Manager click the server on which you want to stop the service, then click Action, then click Stop Service. 2. Click Action, and then click Start Service. To restart the VMMS service using the command prompt: 1. On the computer that has the stopped service, open a command prompt as local administrator and type the following: net stop nvpswmi 2. If the service is not running, you will see the error "The Hyper-V Networking Management service is not started." 3. On the command prompt type the following command to start the nvpswmi service net start nvspwmi If the service start starts you will see the message "The Hyper-V Networking Management service was start successfully." To restart VMMS using PowerShell: 1. On the computer that has the stopped service, open a command prompt as local administrator and type the following: C:\PS>restart-service vmms Verify : The virtual machine is able to start successfully. |
| Reference Links | Event ID 14073 from 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.