Windows Server 2019 — Hyper-V VMMS crash takes virtual machines offline — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

The Hyper-V Virtual Machine Management Service on Windows Server 2019 crashes, leaving running VMs detached from the management plane and blocking start, stop, and live-migration operations. Tools fail to query state and clusters cannot place VMs.

Environment & Reproduction

Reproduce on hosts with stalled WMI providers, corrupt VM configuration files, or recent integration service updates. Inspect Hyper-V-VMMS events.

Get-Service -Name hyperv
Get-WinEvent -LogName System -MaxEvents 40
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Root Cause Analysis

Causes include a corrupted VM .xml/.vmcx file, WMI provider crash inside vmms.exe, conflicting third-party filter driver, or storage outage during start.

Quick Triage

Capture VMMS service state, the failing VM identifier if any, and the most recent VMMS crash event before remediation.

sc.exe query hyperv
Get-Service -Name hyperv | Select-Object Status,StartType
Get-EventLog -LogName System -Newest 30 | Where-Object {$_.Source -match 'hyperv'}

Step-by-Step Diagnosis

Read Hyper-V-VMMS events, list VM state, and check storage and WMI health.

Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.ProviderName -match 'hyperv'} | Select TimeCreated,Id,LevelDisplayName,Message
sc.exe qfailure hyperv
sfc /verifyonly

Solution — Primary Fix

Stop the offending VM if identifiable, restart VMMS, and validate that VM configuration files parse cleanly.

Restart-Service -Name hyperv -Force
Get-Service -Name hyperv | Select-Object Status,StartType
Get-WinEvent -LogName System -MaxEvents 20 | Where-Object {$_.ProviderName -match 'hyperv'}

Solution — Alternative Approaches

If a config file is corrupt, restore the most recent VM configuration backup and reimport the affected VM.

sc.exe config hyperv start= auto
sc.exe failure hyperv reset= 86400 actions= restart/60000/restart/60000/run/1000
Restart-Service -Name hyperv -Force

Verification & Acceptance Criteria

VMMS runs, all VMs are visible and controllable, and Hyper-V management tools return expected state.

Get-Service -Name hyperv
Get-WinEvent -LogName System -MaxEvents 25 | Where-Object {$_.ProviderName -match 'hyperv' -and $_.LevelDisplayName -eq 'Error'}
Test-NetConnection -ComputerName localhost -Port 

Rollback Plan

Restore the previous VM configuration backups and the previous integration services package if needed.

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
wbadmin get versions
# Restore previous configuration export if available

Prevention & Hardening

Back up VM configurations, isolate third-party storage filter drivers, and patch Hyper-V on a tracked cadence.

Get-Service -Name hyperv | Export-Clixml C:/Temp/hyperv-baseline.xml
Get-WinEvent -LogName System -MaxEvents 50 > C:/Temp/hyperv-events.txt
Get-ScheduledTask | Where-Object {$_.TaskName -match 'hyperv'}

Related Errors & Cross-Refs

Related to events 14050, 16010, and SCM 7031 for VMMS.

Related tutorial: View the step-by-step tutorial for Windows Server 2019.

View all Windows Server 2019 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn references for Hyper-V VMMS troubleshooting on Windows Server 2019.