The Blog

Hyper-V Paused-Critical and Saved-Critical

Here are two states you don't want to find your Hyper-V virtual machine in and what to do about it if you do.

When a Hyper-V virtual machine is in the state 'Paused-Critical' it commonly means that a host volume where a differencing or dynamic disk is located is running out of space or may already be full. To avoid crashing the the virtual machine it will automatically put it in a paused state called Paused-Critical.

To resolve this free space on the drive and attempt to resume/start the virtual machine.

'Saved-Critical' generally occurs when the virtual machine configuration files can not be found. They likely are deleted, moved or corrupt.

To resolve this issue find/fix the configuration file. If it can not be found or fixed create a new virtual machine using the new virtual machine wizard and attach the existing VHD's. Note that recreating the virtual machine will not bring back your snapshots or saved state information if you happened to be using them on the virtual machine which lost its configuration files.

Neil Bryan
IT Consultant & Technical Trainer
Neil Bryan is an IT consultant and technical trainer specializing in VMware, Citrix and Microsoft virtualization and infrastructure.


  1. Pepper

    Thanks for this article. I was in panic mode after doing a bios upgrade on my SuperMicro X9DAi box running Server 2008R2 DataCenter. I had a bunch of VM’s showing in “Saved-Critical” state.

    As it turned out, a couple of my RAID arrays were marked “offline” in Disk Management; stopping Hyper-V, bringing the drives online and then restarting Hyper-V cleared everything up.

    1. Neil Bryan

      Thanks PEPPER I’m glad you find it useful.

Leave a Reply

Skip to toolbar