Capture the exact error
Record the Hyper-V Manager or PowerShell error before changing the VM. Check Hyper-V-VMMS and Hyper-V-Worker event logs.
Check VM configuration
Use Get-VM VMName | Format-List * and inspect attached disks, virtual NICs, checkpoints and firmware settings.
Validate storage
Confirm the VM configuration and VHDX files exist at the configured paths and that the host or cluster node has access.
Check permissions
For clustered VMs, validate the computer object and cluster identity have the required permissions on storage. Avoid broad permissions changes.
Check networking
A missing virtual switch can prevent startup or leave the VM without network connectivity. Compare the VM network adapter configuration with available switches.
Validate resources
Check free disk space, memory pressure and any cluster resource failures. Start the VM after correcting the specific fault and verify its integration services.
Explore more TechRunbook guides
Browse practical troubleshooting guides, PowerShell scripts, checklists and infrastructure resources for your environment.
Browse all articles →