My Hyper-V guest VM is stuck in an Unmapped state

Question

My Hyper-V guest VM is stuck in an Unmapped state

Michael Johnson 40

I'm having real problems with a guest VM on our Hyper-V cluster. It has entered an Unmapped state because the .VMCX configuration file remains locked by an orphaned vmwp.exe process from a previous cluster node. And I can't work out how to release the file lock. For a number of months, if I live migrated the VM or failed it over, it would clear up, and it would take me back to a normal running state.

But now, I seem stuck with this locked file and an unmapped VM. I work for myself, and so don't have an IT department to consult. Any help on how to safely release the lock without a host reboot would be hugely appreciated!

0 comments

1 answer

Your answer

Answer 1

For a Hyper-V VM stuck in an unmapped or transitional state because a vmwp.exe process is still holding the configuration file, use this recovery path:

Identify the stuck VM worker process on the affected host.

   Get-Process | Where-Object {$_.Name -like "*vmwp*"}

End the specific stuck VM process.
```
   taskkill /PID <PID> /F
```
This forcibly stops the VM worker process that is holding the lock.
Restart the Hyper-V Virtual Machine Management Service.
If the VM is still stuck after the service restart, restart the host computer.
If the VM remains inaccessible in the cluster, validate cluster health because cluster configuration issues can cause live migration failures, unexpected restarts, and failover problems.
```
   Test-Cluster
```
Review the VM folder on the storage hosting the VM and confirm the expected files exist: .vmcx, .vmrs, .vhdx, and any .avhdx files.
- If the .vmcx file is missing or corrupted, rebuild the VM by using the existing .vhdx, or restore the VM from backup.
- If disk or network assignments are wrong after migration, correct the VM settings so the proper disk and network adapter are assigned.

Important: forcibly ending the VM process can cause loss of unsaved or transient data. A host restart is the documented fallback if the lock is not cleared after terminating the worker process and restarting the management service.